Unify Quasar UI core and application shell #40

Merged
lost-rob0t merged 37 commits from ui-core-shell-overhaul into main 2026-08-19 04:40:57 +00:00
lost-rob0t commented 2026-08-19 03:57:23 +00:00 (Migrated from github.com)

Implements #39.

This is the approved full UI shell overhaul:

  • introduces one shared Quasar UI core with standalone, Common Lisp control-plane, and Auto-Dig adapters
  • replaces route-specific shell behavior with one persistent black/gold application shell
  • promotes Datasets to /datasets and redirects the legacy query-param route
  • guarantees explicit single-item navigation selection across desktop/mobile
  • keeps graph chrome, toolbar, inspector, dock, and full-viewport behavior inside the global shell
  • removes the DOM-mirroring OperatorUiEnhancer from the production entry point
  • consolidates runtime/service health into one status center
  • adds regression coverage for route shell geometry, graph containment, and navigation parity
  • documents the adapter and styling boundary

The existing Common Lisp/Tek9 authority boundary is unchanged; this PR is presentation/adapter architecture, not a second runtime.

Implements #39. This is the approved full UI shell overhaul: - introduces one shared Quasar UI core with standalone, Common Lisp control-plane, and Auto-Dig adapters - replaces route-specific shell behavior with one persistent black/gold application shell - promotes Datasets to `/datasets` and redirects the legacy query-param route - guarantees explicit single-item navigation selection across desktop/mobile - keeps graph chrome, toolbar, inspector, dock, and full-viewport behavior inside the global shell - removes the DOM-mirroring `OperatorUiEnhancer` from the production entry point - consolidates runtime/service health into one status center - adds regression coverage for route shell geometry, graph containment, and navigation parity - documents the adapter and styling boundary The existing Common Lisp/Tek9 authority boundary is unchanged; this PR is presentation/adapter architecture, not a second runtime.
Sign in to join this conversation.
No description provided.