Problem
The README screenshot shows the v2.5 dashboard. After PR #17 (v2.6.0 "Dashboard Elevated" — boot sequence, ⌘K palette, tmux status bar, mission track, task burn), the headline image undersells the product's best work.
Plan (agreed with Daniel)
When Daniel picks this up, Claude will:
- Build a showcase
dashboard-data.js — not the test fixture, but a deliberately beautiful, realistic project: interesting mission, 4–5 phases with rich specs/designs/tasks, a meaty architecture diagram, mixed phase states so the mission track shows complete + active-pulsing + roadmap nodes, partial DoD for the LED bar, and stack rows exercising all four source badges
- Recommend the exact shot(s) to capture — which view, which state, window size — optimizing for the most beautiful screenshot (current candidates: Overview with mission track + task burn + tmux bar all visible; the boot sequence mid-type as a secondary/GIF shot; a phase design tab with the architecture map)
- Daniel takes the screenshot and swaps it into the README
Acceptance
Origin: v2.6.0 release-process audit (PR #17).
Problem
The README screenshot shows the v2.5 dashboard. After PR #17 (v2.6.0 "Dashboard Elevated" — boot sequence, ⌘K palette, tmux status bar, mission track, task burn), the headline image undersells the product's best work.
Plan (agreed with Daniel)
When Daniel picks this up, Claude will:
dashboard-data.js— not the test fixture, but a deliberately beautiful, realistic project: interesting mission, 4–5 phases with rich specs/designs/tasks, a meaty architecture diagram, mixed phase states so the mission track shows complete + active-pulsing + roadmap nodes, partial DoD for the LED bar, and stack rows exercising all four source badgesAcceptance
Origin: v2.6.0 release-process audit (PR #17).