Unify Quasar workbench UI around the graph shell #19

Merged
lost-rob0t merged 1 commit from design/unify-workbench-shell into stack/pr21-ui-base 2026-08-09 03:02:50 +00:00
lost-rob0t commented 2026-08-09 00:46:46 +00:00 (Migrated from github.com)

Summary

Makes the graph workspace the visual authority for the rest of Quasar instead of switching to a different blue/dashboard design outside /graph.

  • applies one compact operator shell across routes with the graph's 246px sidebar, 62px top bar, active-nav marker, and denser chrome;
  • builds on the Black & Gold / Kinpaku theme work while preventing route-specific layout drift;
  • removes the dashboard's landing-page treatment: oversized heading, glowing hero card, nested metric cards, and heavy gradient surfaces are flattened into an operational overview;
  • keeps review/unreviewed separation while using rules and data marks instead of a second visual theme;
  • fixes the graph sidebar New graph control so its label no longer wraps inside a 28px-wide button on desktop;
  • replaces the remaining Unicode brand glyph with the existing Lucide Sparkles icon;
  • tightens notices, focus treatment, selection, numeric presentation, and responsive dashboard behavior;
  • adds DESIGN.md so future routes inherit the same workbench language instead of drifting again.

Design guide

This pass follows pbakaus/impeccable in Operate mode: consistency and task scanability over route-specific expression, restrained accent usage, compact fixed product typography, no card soup/nested cards, and the existing graph surface treated as incumbent visual authority.

Stacking

PR #21 contains the isolated Kinpaku/navigation/diagnostics UI slice this work extends. stack/pr21-ui-base is a zero-change snapshot of PR #21 head de6c09478c8057108e3e12eec51a1fc89f7a4bb3, used only so this review shows the five design files instead of the whole UI precursor. After #21 lands, retarget this PR to the branch #21 lands on (ultimately main after #3).

Validation

GitHub Actions is the validation gate for formatting, lint/type/boundary/static checks, unit/integration tests, production build, Common Lisp tests, real-stack browser coverage, and packaged production smoke. No auto-merge is configured.

## Summary Makes the graph workspace the visual authority for the rest of Quasar instead of switching to a different blue/dashboard design outside `/graph`. - applies one compact operator shell across routes with the graph's 246px sidebar, 62px top bar, active-nav marker, and denser chrome; - builds on the Black & Gold / Kinpaku theme work while preventing route-specific layout drift; - removes the dashboard's landing-page treatment: oversized heading, glowing hero card, nested metric cards, and heavy gradient surfaces are flattened into an operational overview; - keeps review/unreviewed separation while using rules and data marks instead of a second visual theme; - fixes the graph sidebar `New graph` control so its label no longer wraps inside a 28px-wide button on desktop; - replaces the remaining Unicode brand glyph with the existing Lucide `Sparkles` icon; - tightens notices, focus treatment, selection, numeric presentation, and responsive dashboard behavior; - adds `DESIGN.md` so future routes inherit the same workbench language instead of drifting again. ## Design guide This pass follows `pbakaus/impeccable` in **Operate** mode: consistency and task scanability over route-specific expression, restrained accent usage, compact fixed product typography, no card soup/nested cards, and the existing graph surface treated as incumbent visual authority. ## Stacking PR #21 contains the isolated Kinpaku/navigation/diagnostics UI slice this work extends. `stack/pr21-ui-base` is a zero-change snapshot of PR #21 head `de6c09478c8057108e3e12eec51a1fc89f7a4bb3`, used only so this review shows the five design files instead of the whole UI precursor. After #21 lands, retarget this PR to the branch #21 lands on (ultimately `main` after #3). ## Validation GitHub Actions is the validation gate for formatting, lint/type/boundary/static checks, unit/integration tests, production build, Common Lisp tests, real-stack browser coverage, and packaged production smoke. No auto-merge is configured.
Sign in to join this conversation.
No description provided.