Skin V1 Settings: dashboard-matched typography and full keyboard directory

[BryanHarrisScripts]

Goal

Make Settings feel like the same PlotPickle surface as the Dashboard rather than a visually disconnected legacy/options screen.

User-facing requirement

When the user enters Settings/Options, the first Settings directory must expose all top-level entries as keyboard-operable choices and use the same Skin V1 visual language/font as the Dashboard.

At minimum the directory must include:

• General
• Appearance & Accessibility
• Project Defaults
• Cloud Story Mode
• Data
• Deploy
• Repos
• Auth
• Agents
• Open Source

Do not show only generic Workspace / Systems headings as the useful interaction. Those groups may remain as visual grouping labels, but the named destinations are the keyboard entries.

Required behavior

1. Every visible top-level Settings destination receives a stable single-key shortcut displayed in the row, matching the Dashboard command-line pattern.
2. Up/Down moves the selected Settings row.
3. Enter opens a connected Settings surface.
4. Pressing a displayed shortcut activates that row.
5. Escape returns toward Dashboard/current parent surface.
6. Disabled/not-yet-connected destinations may remain visible, but they must still be selectable/inspectable and truthfully marked as not connected rather than omitted.
7. Settings typography must use the canonical Skin V1 Dashboard font tokens; do not fall back to a different browser/legacy font.
8. Reuse Skin V1 spacing, status boxes, borders and command-line row treatment so Settings visually belongs to the Dashboard.
9. Preserve future-skin separation: do not hard-code a second theme inside Settings.

Acceptance criteria

• All named Settings destinations appear as rows rather than only Workspace/Systems abstractions.
• Each row displays a keyboard shortcut.
• Up/Down, Enter, shortcut keys and Escape work consistently.
• Connected destinations open; unconnected destinations remain visible and truthfully inactive.
• Settings uses the same Skin V1 font/design tokens as Dashboard.
• Focused tests cover the menu names, shortcuts and keyboard handlers.
• Production build and required GitHub CI are green.

Do not change

Unrelated Dashboard navigation, Story/PPF behavior, BUZZ runtime behavior, or legacy Settings internals that are not being connected by this slice.