M22 Tracking — UI consolidation #400

Closed
opened 2026-04-26 19:59:31 +00:00 by claude-desktop · 1 comment
Collaborator

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 over-subdivided into 5 sub-routes for what is essentially one workflow (issue + task lifecycle inspection)
  • /monitor/tasks and /monitor/task/:id duplicate /monitor's data with a competing mental model (task-centric vs issue-centric)
  • /monitor/issue/:n and .../gantt run identical fetch + identical SSE patch logic, only the viz differs
  • Specs are a first-class entity but buried in the Planner sidebar; /specs exists only as a redirect

Proposed simplified IA

BEFORE                          AFTER
/monitor (5 leaves)             /monitor (2 leaves)
  /tasks                          /issue/:n?view=graph|gantt
  /task/:id                       [/?detail=:id drawer]
  /issue/:n
  /issue/:n/gantt
  /grid → redirect
/specs → redirect               /specs (2 leaves)  ← promoted
/usage → redirect                 /:specName

Stories

  • UI-1 #397 Monitor tasks → slide-out drawer (kill /monitor/tasks + /monitor/task/:id + /monitor/grid)
  • UI-2 #398 Monitor issue Gantt → view tab on issue detail
  • UI-3 #399 Promote Specs to top-level nav (/specs + /specs/:specName)

Out of scope (deferred)

  • Phase 3 — fold /stats?tab=caps into /stats?tab=tasks. Depends on issue #231 (cost-controls) landing first.
  • Planner board vs chat merge — kept separate by design; Kanban + chat are distinct mental models.

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

  • UX audit conducted 2026-04-26 (chat history)
  • apps/web/CLAUDE.md — radius/shadow conventions for any new drawer/dialog surfaces
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 over-subdivided into 5 sub-routes for what is essentially one workflow (issue + task lifecycle inspection) - `/monitor/tasks` and `/monitor/task/:id` duplicate `/monitor`'s data with a competing mental model (task-centric vs issue-centric) - `/monitor/issue/:n` and `.../gantt` run identical fetch + identical SSE patch logic, only the viz differs - Specs are a first-class entity but buried in the Planner sidebar; `/specs` exists only as a redirect ## Proposed simplified IA ``` BEFORE AFTER /monitor (5 leaves) /monitor (2 leaves) /tasks /issue/:n?view=graph|gantt /task/:id [/?detail=:id drawer] /issue/:n /issue/:n/gantt /grid → redirect /specs → redirect /specs (2 leaves) ← promoted /usage → redirect /:specName ``` ## Stories - [ ] UI-1 #397 Monitor tasks → slide-out drawer (kill /monitor/tasks + /monitor/task/:id + /monitor/grid) - [ ] UI-2 #398 Monitor issue Gantt → view tab on issue detail - [ ] UI-3 #399 Promote Specs to top-level nav (/specs + /specs/:specName) ## Out of scope (deferred) - **Phase 3** — fold `/stats?tab=caps` into `/stats?tab=tasks`. Depends on issue #231 (cost-controls) landing first. - **Planner board vs chat merge** — kept separate by design; Kanban + chat are distinct mental models. ## 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 - UX audit conducted 2026-04-26 (chat history) - `apps/web/CLAUDE.md` — radius/shadow conventions for any new drawer/dialog surfaces
Author
Collaborator

Closing — UI-1 #397, UI-2 #398, UI-3 #399 all merged. Phase 3 (fold stats caps) explicitly deferred against #231. Verified 2026-04-28.

Closing — UI-1 #397, UI-2 #398, UI-3 #399 all merged. Phase 3 (fold stats caps) explicitly deferred against #231. Verified 2026-04-28.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/claude-hooks#400
No description provided.