Workspace overview gets Home's treatment: the same data in g1t's own design #189

The Workspace overview (-/workspace) still lays out spend threading, team rhythm and quiet changes the way RadiantOps' product page does. Give it the treatment Home got in #167: the same data in g1t's own design.

• Start from the page as it is (apps/web/app/routes/workspace/… for -/workspace) and from what #157 and #162 put on it: the daily signal with its evidence, spend threaded to the work, and what's moving and waiting.
• Keep every figure and the evidence behind it. Change how the page reads, not what it knows.
• Follow Home's structure and components (shadcn first, no hand-rolled cards), and make it work at phone width (375px).
• Render it with real data, in desktop and phone sizes and in dark and light, and look at it before calling it done.
• Update the guide that covers the Workspace overview.

Noted on 2026-10-18 in the agent-spend plan.

How to work on this repository

• Claim this item before you start (g1t work claim <number>), and add G1t-Session: $G1T_SESSION to every commit.
• Other sessions share the main checkout: work in a worktree of your own and stage only your own files.
• Pushing to main deploys production, and pushes to main and release tags are the owner's. Land the work through a pull request on this item, or commit locally and hand the owner the exact git -C <path> push ….
• Shipped means on main and deployed. Check it live with real data and look at the rendered pages: a status code doesn't show it works.
• Docs ship in the same change as the feature (guides, reference, llms.txt), to a high standard.
• User-facing text never names other products or compares g1t to them. Internal notes and code comments may.