M22 Tracking — UI consolidation #400
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks#400
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tracking issue for M22 — UI consolidation. Cuts route count from 14 → 10 leaves (~30% reduction) by collapsing the over-subdivided Monitor surface and promoting Specs to a first-class top-nav entry.
Context
UX audit 2026-04-26 (driven by operator complaint "too many screens, redundant, hard to navigate") identified:
/monitor/tasksand/monitor/task/:idduplicate/monitor's data with a competing mental model (task-centric vs issue-centric)/monitor/issue/:nand.../ganttrun identical fetch + identical SSE patch logic, only the viz differs/specsexists only as a redirectProposed simplified IA
Stories
Out of scope (deferred)
/stats?tab=capsinto/stats?tab=tasks. Depends on issue #231 (cost-controls) landing first.Suggested implementation order
UI-1, UI-2, UI-3 are independent — can land in any order. Suggested: UI-2 first (smallest, exercises pattern of consolidating-into-tab), then UI-1 (introduces drawer pattern), then UI-3 (broader IA reshape).
References
apps/web/CLAUDE.md— radius/shadow conventions for any new drawer/dialog surfacesClosing — UI-1 #397, UI-2 #398, UI-3 #399 all merged. Phase 3 (fold stats caps) explicitly deferred against #231. Verified 2026-04-28.