Post-#2026 visual UAT regressions — restore dragon, simplify Writer's Craft return, profile status layout, and Skin V1 surface consistency

[BryanHarrisScripts]

Human UAT source

Follow-up Human testing immediately after #2026 merged. The Dashboard navigation reset is directionally correct, but this pass found several visual/flow regressions that should be repaired as one bounded cleanup issue.

Findings

1. Dashboard dragon was unintentionally lost

   • Restore the approved dragon artwork to the Dashboard.
   • Keep the new Dashboard main menu + navigation reset — canonical layout, labels, descriptions and status-square alignment #2026 menu order/grouping/status-column layout.
   • Do not restore the retired Score panel or obsolete dashboard chrome just to get the dragon back.

2. Writer's Craft layout can use available width better

   • Rows such as 01 Anatomy of a Screenplay have enough horizontal room for their Path/Craft context (for example Foundations / Craft Module / lesson context) without awkward wrapping.
   • Use the available width and preserve Skin V1 readability rather than letting the context wrap unnecessarily.

3. Writer's Craft Back flow is wrong for the new main navigation

   • Current Back to Journey returns to an older Journey submenu.
   • From the Writer's Craft curriculum surface, Human expectation is to return to the main Dashboard.
   • Retire the obsolete intermediary Journey-return path from this flow; update the visible action copy so destination and label agree.

4. Human Profile status strip is too horizontal/dense

   • The left-side status group (BUZZ Identity, Community BBS, Local Model, ComfyUI, Cloud Compute) is struggling to stay formatted in one horizontal strip.
   • Present these status items vertically (or as a clearly stacked single-column group) so labels and indicators remain legible at the current surface width.
   • Preserve the rest of the Profile layout.

5. Issue Log has regressed to an older visual treatment

   • It currently shows an older green/black/green treatment and typography mismatch.
   • Bring Issue Log back to the current approved Skin V1 visual language used by the Dashboard/submenus: canonical typography, spacing, monochrome surface treatment with the current green accent rules.

6. Licensing has the same visual regression

   • Restore current Skin V1 color/typography consistency without changing Licensing behavior/content.

7. Agents surface has regressed to black/white

   • Restore the most recent approved Agents Skin V1 treatment from before the regression.
   • Do not redesign the Agents product model in this issue; this is a visual continuity repair only.

Guardrails

• Dashboard main menu + navigation reset — canonical layout, labels, descriptions and status-square alignment #2026 Dashboard navigation/order/copy remains authoritative.
• Dragon restoration must not reintroduce the old Score panel or obsolete dashboard hero/chrome.
• Reuse prior approved Skin V1 surface treatments rather than inventing a new style.
• Preserve existing IDs, routes, keyboard shortcuts and wiring unless the explicit Writer's Craft Back-flow change requires a route target update.
• Do not fake status colors; use real connected/review/unwired state.
• Keep changes scoped to the observed Human UAT findings.

Verification

• Focused regression coverage for each repaired surface/flow.
• Exact-head seven-layer Architecture Verification.
• Inspect only failed gates, repair until green.
• Merge when green and stop.