26.6.6

Highlights

Migrated backend database access flow from direct psycopg cursor usage to SQLModel/SQLAlchemy session-backed execution while preserving existing API contracts.
Added compose watch configuration for docs, frontend, and backend services to improve local development rebuild behavior.
Standardized version-file usage across services and build pipelines from VERSIONS to VERSION.
Applied branding and product-homepage improvements to both frontend and VitePress docs site.
Added backlog tracking for expired-token session-state handling so signed-in UI state cannot drift after token expiry.

Added SQLModel/SQLAlchemy engine + session helpers with postgresql+psycopg dialect normalization.
Replaced direct psycopg cursor calls with session-based SQL execution helpers.
Added centralized IntegrityError mapping to API HTTP responses for unique, foreign-key, and check constraint violations.
Updated backend runtime version reading to use the VERSION file.

Added semantic message tone handling for status cards (danger, warning, success, info).
Added semantic button variants for success, warning, and info actions.
Applied Nexus brand typography and color tokens in app shell and component styling.
Replaced compatibility-sensitive color-mix(...) usage with static color/rgba equivalents in key UI styles.
Updated frontend build version injection to use the VERSION file.

Repositioned docs landing page as a Nexus product homepage with marketing-first messaging and CTAs.
Added branded VitePress custom theme overrides (typography, token palette, hero/nav/content styling).
Updated docs site shell branding and navigation labels for product-first information architecture.
Added backlog item for token expiry auth-state handling in the main backlog page.

Added develop.watch rebuild triggers in Compose for docs, frontend, and backend code/config inputs.
Updated docs, frontend, and backend Dockerfiles to copy VERSION instead of VERSIONS.
Removed legacy VERSIONS file in favor of single VERSION source.