You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
impl(aggregator): /roadmap drill-down - roadmap row expands to its epic, progress, and issues #1168
Evidence (live review 2026-10-26 ~22:40 CDT, laptop loopback + gh, cross-checked): /roadmap renders 23 Grist rows flat at every horizon (the ?h= switch re-buckets the same rows; it adds no depth). A row links out to an issue but shows no progress: Drew cannot see "Phase 12 = 40% of its issues closed" or open the row into its epic + children from the dashboard.
Proposal
Rows expand (server-rendered details) to: linked epic (from the Grist<->Project reconciliation), child issue list with states (live from pool/items), a simple done/total progress bar, and the row's notes. Horizon switch keeps working; expansion state is per-row links (no client JS needed beyond
Details).
Acceptance
Sampled rows (one per Area) expand to children whose states match GitHub at fetch time.
Sampled /roadmap rows (one per Area) expand to their linked epic, child issue list with live states, and a done/total progress bar whose states match GitHub at fetch time.
Rows with no epic yet say so explicitly.
The horizon switch (?h=) keeps working and expansion needs no client JS beyond .
Notes / risks: Child states must be live from pool/items at fetch time — a cached snapshot would recreate the staleness problems the quota batch is fixing.
Suggested approach: Server-rendered
Details expansion per the proposal; no client JS.
Live check: verified still open and unheld this run; a merged-PR search on this run (2026-10-28T10:35:00Z) returned no PR resolving this issue, so it remains live work. Acceptance criteria appended to the body (original text preserved verbatim above it) and labels normalized by the fleet monitor.
Next: confirm repository CI/check applicability and targeted-test evidence, then merge if all criteria remain satisfied; otherwise park with a resume condition.
Verification: targeted tests 45/45 pass; Codex review completed with no findings. Full suite had one unrelated registry-source failure previously reproduced on clean main. No required CI checks are configured.
Activity
developing-today commentedon Oct 27, 2026
CODE-304
dezren39 commentedon Oct 28, 2026
Intake review
Related: Live-review finding (2026-10-26). Refs #910. Sibling batch: #1170, #1171.
Notes / risks: Child states must be live from pool/items at fetch time — a cached snapshot would recreate the staleness problems the quota batch is fixing.
Suggested approach: Server-rendered
Details
expansion per the proposal; no client JS.Live check: verified still open and unheld this run; a merged-PR search on this run (2026-10-28T10:35:00Z) returned no PR resolving this issue, so it remains live work. Acceptance criteria appended to the body (original text preserved verbatim above it) and labels normalized by the fleet monitor.
12 remaining items
dezren39 commentedon Nov 1, 2026
🤖 Agent note · parked
dezren39 commentedon Nov 1, 2026
agent-note:v1 — state: picked-up (small_fix task 4904, OpenChamber scheduled lane)
dezren39 commentedon Nov 1, 2026
agent-note:v1 — state: done (small_fix task 4904, OpenChamber scheduled lane)