c7. Web Rail

Mark's words, 2026-11-11, late evening, in the c133 design session; unchanged. First tossed into c6's sprint, then split off: "can we create a small cycle to do so and run in a cloud session". The pointers below are the session's.

we need left nav space between sections.

in fact, let's replicate our nav from the web app. no icon, headers, etc *left nav

can we create a small cycle to do so and run in a cloud session

Pointers

• The web app's rail is the layer's vertical nav: /Users/mark/web/qpoint/q-nuxt-layer/components/nav/ (NavVertical and its submenu), drawn in qdash (/Users/mark/web/qpoint/qcontrol/crates/qdash/ui) with the groups MONITOR, GOVERN + SECURE, ADMIN as small uppercase labels, plain text entries, no icons, the active entry marked, a gap between groups.
• The lab's imitation of that rail: /Users/mark/web/qpoint/design/app/components/governance/mock/Sidebar.vue; the native skin's rail: /Users/mark/web/qpoint/design/app/components/native/Window.vue. Match the web app, not the skin.
• The native rail today: crates/app/src/shell.rs (menu, the groups) and the routes and groups in crates/app/src/router.rs (MACHINE and the rest).
• The token bridge: /Users/mark/web/qpoint/design/scripts/tokens-to-kit.mjs and brand/design_tokens.md; the kit theme it generates is the source of type sizes, weights and colours here.
• c6 (Panel Toggles, on a branch from c3/phases) colours the Dev group cyan when developer mode is on and leaves the rail's structure to this cycle; c5 (Activity) edits router.rs and shell.rs on main at the same time, uncommitted. This cycle commits only the rail.