c6. Panel Toggles

Mark's words, 2026-11-11, late evening, in the c133 design session; unchanged. The pointers below are the session's.

Also, I like the idea of opening the info panel, and adding two toggles that are set when it is open. Help Mode (on / off) Dev Mode (on/off)

let's do a quick sprint locally for that, no deep plan needed

actually, let's write a quick cycle file and then we can run in a fresh agent

Pointers

• The info panel is c2's Info View (the Tour stretch): crates/app/src/guide/info.rs, the tour in crates/app/src/tour/, the rail's Help entry and the tray menu in crates/app/src/shell.rs.
• Developer mode's switch is c3's: crates/devmode/src/lib.rs (allowed(), the "Developer mode" toggle the tray menu carries), the saved values in crates/host/src/lib.rs (Store) and crates/app/src/settings.rs (settings.json).
• The idea is recorded in design's c138 plan under Rulings as "The toggles' seat" (design 728dab6b27).
• One reading to check with Mark: "set when it is open" taken as shown and settable in the open panel, not switched on by opening it.

2026-11-11, later the same evening

Mark's words, relayed into the sprint by the c133 design session; unchanged.

we need left nav space between sections. Let's make the dev mode on section cyan like the tour elements

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

Then, relayed as Mark's correction: the left nav's replication of the web app (section headers, no icons, the space between sections) is its own cycle, qnative c7, run in the cloud on main, merging after this one. This sprint keeps what is developer mode's: the Dev group in the tour's cyan when developer mode is on, as colour only, the rail's structure untouched.