charles/claude-hooks

Fork 0

UI consolidation — spec breakdown tracker #259

New issue

Closed

opened 2026-04-21 20:19:44 +00:00 by architect · 5 comments

architect commented

2026-04-21 20:19:44 +00:00

Collaborator

Tracking issue for the breakdown of specs/ui-consolidation.md.

The spec collapses three redundant nav pairs:

Specs → Planner (UC-1)
Grid → Pipeline (UC-2)
Usage → Stats (UC-3)

Nav shrinks 9 → 6. Deep-link redirects preserve bookmarks.

Dispatch: /breakdown specs/ui-consolidation.md

Tracking issue for the breakdown of `specs/ui-consolidation.md`. The spec collapses three redundant nav pairs: - **Specs → Planner** (UC-1) - **Grid → Pipeline** (UC-2) - **Usage → Stats** (UC-3) Nav shrinks 9 → 6. Deep-link redirects preserve bookmarks. Dispatch: `/breakdown specs/ui-consolidation.md`

architect commented

2026-04-21 20:20:11 +00:00

Author

Collaborator

/breakdown specs/ui-consolidation.md

code-lead commented

2026-04-21 20:21:51 +00:00

Collaborator

No such spec file: specs/ui-consolidation.md

Checked main, every remote branch, and the repo's code search index — the path does not exist. The issue body sketches the UC-1 / UC-2 / UC-3 consolidation plan, but the breakdown skill needs a committed specs/*.md file as its source of truth (so dedup + ## Acceptance criteria parsing work against a stable snapshot).

Likely cause: the foreman drafted the spec in /foreman/chat but the file was never committed to main. Next step for the operator:

Commit the spec to main at specs/ui-consolidation.md (foreman can do this via /foreman/chat — it has write access to specs/*.md, or via a dev PR if a review pass is wanted first).
Re-run /breakdown specs/ui-consolidation.md on this issue.

No issues were created. No side effects.

No such spec file: `specs/ui-consolidation.md` Checked `main`, every remote branch, and the repo's code search index — the path does not exist. The issue body sketches the UC-1 / UC-2 / UC-3 consolidation plan, but the `breakdown` skill needs a committed `specs/*.md` file as its source of truth (so dedup + `## Acceptance criteria` parsing work against a stable snapshot). Likely cause: the foreman drafted the spec in `/foreman/chat` but the file was never committed to `main`. Next step for the operator: 1. Commit the spec to `main` at `specs/ui-consolidation.md` (foreman can do this via `/foreman/chat` — it has write access to `specs/*.md`, or via a `dev` PR if a review pass is wanted first). 2. Re-run `/breakdown specs/ui-consolidation.md` on this issue. No issues were created. No side effects.

charles referenced this issue from a commit

2026-04-21 20:22:57 +00:00

docs(specs): add ui-consolidation spec (UC-1/UC-2/UC-3)

architect referenced this issue

2026-04-21 20:23:10 +00:00

docs(specs): add ui-consolidation spec #260

architect commented

2026-04-21 20:23:18 +00:00

Author

Collaborator

The spec file was missing from main on the first dispatch — boss correctly bailed with no side effects. I have opened #260 landing specs/ui-consolidation.md on a branch (foreman/ui-consolidation-spec).

Next step (operator): merge #260, then re-run /breakdown specs/ui-consolidation.md on this issue. The boss pool will then see the committed spec in its clone and produce one type:user-story per ## Story UC-N section.

(Foreman cannot merge PRs or push to main directly — by design.)

The spec file was missing from `main` on the first dispatch — boss correctly bailed with *no side effects*. I have opened #260 landing `specs/ui-consolidation.md` on a branch (`foreman/ui-consolidation-spec`). **Next step** (operator): merge #260, then re-run `/breakdown specs/ui-consolidation.md` on this issue. The boss pool will then see the committed spec in its clone and produce one `type:user-story` per `## Story UC-N` section. (Foreman cannot merge PRs or push to `main` directly — by design.)

charles referenced this issue from a commit

2026-04-21 20:25:54 +00:00

docs(specs): add ui-consolidation spec (#260)

architect commented

2026-04-21 20:27:34 +00:00

Author

Collaborator

/breakdown specs/ui-consolidation.md

code-lead referenced this issue

2026-04-21 20:31:17 +00:00

feat(web): merge Specs route into Planner page (UC-1) #262

code-lead referenced this issue

2026-04-21 20:31:18 +00:00

feat(web): merge Grid route into Pipeline as view toggle (UC-2) #263

code-lead referenced this issue

2026-04-21 20:31:19 +00:00

feat(web): merge Usage route into Stats as tab (UC-3) #264

code-lead commented

2026-04-21 20:33:02 +00:00

Collaborator

Created #262, #263, #264 from specs/ui-consolidation.md.
No security-sensitive sections — none of the three carry the security label.

Issue	File	Assignee
#262 — feat(web): merge Specs route into Planner page (UC-1)	`specs/ui-consolidation.md`	dev
#263 — feat(web): merge Grid route into Pipeline as view toggle (UC-2)	`specs/ui-consolidation.md`	dev
#264 — feat(web): merge Usage route into Stats as tab (UC-3)	`specs/ui-consolidation.md`	dev

Labels applied: type:user-story, area:dashboard on all three.

Native dependency registered (Forgejo /dependencies API): #263 is blocked by #262. #264 is independent; can run in parallel with either once #262 lands if the operator wants to parallelise.

Suggested implementation order (mirrors the spec's own "Suggested implementation order"):

#262 (UC-1, Specs → Planner) — smallest merge; establishes the /old-route → /new-route?param redirect pattern UC-2 and UC-3 both reuse.
#263 (UC-2, Grid → Pipeline) — depends on #262 for the redirect helper; otherwise independent. Lifts the shared usePipelineSSE hook.
#264 (UC-3, Usage → Stats) — independent of the other two; parallelisable.

All three are dev-sized per the spec's own note ("No boss-level architecture changes; the boss agent's role is limited to producing the spec breakdown.") — hence dev assignees, no boss routing.

No duplicates skipped. No unknown area:* labels (only area:dashboard needed and it exists). Batch size 3 well under the 15-issue cap.

Created #262, #263, #264 from `specs/ui-consolidation.md`. No security-sensitive sections — none of the three carry the `security` label. | Issue | File | Security | Assignee | |-------|------|---------|----------| | #262 — feat(web): merge Specs route into Planner page (UC-1) | `specs/ui-consolidation.md` | | dev | | #263 — feat(web): merge Grid route into Pipeline as view toggle (UC-2) | `specs/ui-consolidation.md` | | dev | | #264 — feat(web): merge Usage route into Stats as tab (UC-3) | `specs/ui-consolidation.md` | | dev | Labels applied: `type:user-story`, `area:dashboard` on all three. **Native dependency registered** (Forgejo `/dependencies` API): #263 is blocked by #262. #264 is independent; can run in parallel with either once #262 lands if the operator wants to parallelise. **Suggested implementation order** (mirrors the spec's own "Suggested implementation order"): 1. **#262 (UC-1, Specs → Planner)** — smallest merge; establishes the `/old-route` → `/new-route?param` redirect pattern UC-2 and UC-3 both reuse. 2. **#263 (UC-2, Grid → Pipeline)** — depends on #262 for the redirect helper; otherwise independent. Lifts the shared `usePipelineSSE` hook. 3. **#264 (UC-3, Usage → Stats)** — independent of the other two; parallelisable. All three are dev-sized per the spec's own note ("No boss-level architecture changes; the boss agent's role is limited to producing the spec breakdown.") — hence `dev` assignees, no `boss` routing. No duplicates skipped. No unknown `area:*` labels (only `area:dashboard` needed and it exists). Batch size 3 well under the 15-issue cap.

charles closed this issue

2026-04-22 11:25:26 +00:00