Repository navigation
epic(dashboard): per-project status pages for all projects — generalize /program beyond pm-dashboard #1129
Description
Summary
Epic for Drew's direction (2026-10-26): the dashboard's program/project pages must be fully integrated for all projects, not just the PM dashboard — every project gets a documented section (description, status, what's built, what's next, long-term roadmap, known gaps), driven by an improved per-project configuration, built out until fully functional, with every aspect tracked by an issue with a real description.
Background: #1046/PR #1060 shipped /program for the pm-dashboard project only, hard-coded as one editorial object. The 2026-10-26 project reviews (dashboard, id, home cluster, SaaS) each found the same gap for their project. The project-structure spec (2026-10-26, lab-cluster goal workspace) sets the standard these pages implement: project home docs in planning/roadmaps/, dated status reports, org Project #4 rows with Area = project, epics/issues as the work layer.
Project set (v1, verified live 2026-10-26: pool 90 items, roadmap 23 rows)
pm-dashboard · lab-cluster (Basement cluster) · id (id-train) · repo-fleet (fleet-ops) · mcpx · cloud-program (SaaS/accounts)
Children
- design(aggregator): project configuration registry — one config per project for the program pages #1120 — design: project configuration registry (the config improvement; one entry per project, validated, documented recipe)
- impl(aggregator): /program hub + /program/<project> pages for all configured projects #1121 — build: /program hub + /program/ pages + JSON twins for all configured projects (closes the pm-only gap)
- impl(aggregator+collector): complexity-weighted project visualization (rollup, hands queue, blocked weight, depth graph) #1122 — phase B: complexity-weighted visualization (rollup / hands queue / blocked weight / depth graph) + the collector data it needs
- docs(dashboard): document the per-project pages — README, spec alignment, home docs, status reports #1123 — docs: README, spec alignment, home docs, status-report layer
- docs(dashboard): build out the Basement cluster project section (/program/lab-cluster) #1124 — build out: Basement cluster section
- docs(dashboard): build out the id platform project section (/program/id) #1125 — build out: id platform section
- docs(dashboard): build out the Repo fleet project section (/program/repo-fleet) #1126 — build out: Repo fleet section
- docs(dashboard): build out the mcpx project section (/program/mcpx) + decide its Project/roadmap integration #1127 — build out: mcpx section + its Project/roadmap integration decision
- docs(dashboard): build out the Cloud program / SaaS project section (/program/cloud-program) #1128 — build out: Cloud program / SaaS section
Related (not children; they gate "fully functional")
- impl(fleet): work-picking jobs consult the orchestrator published priorities before choosing work #911 — work-picking jobs consult the orchestrator (last unimplemented item of the original program)
- fix(aggregator/orchestrator): orchestration section rejected — provenance is an object, isOrchestrationSection requires a string #1110 — orchestration section rejected on a provenance shape mismatch (the pages' freshness sections light up when this lands)
Done when
Every child is closed: all six projects have live, sourced, documented pages on the laptop dashboard; the weighted visualization renders from real data; a reader starting at the dashboard can reach each project's description, status, roadmap, tracked work, and home doc; and no page asserts a status a live source contradicts.
Activity
developing-today commentedon Oct 27, 2026
CODE-267
dezren39 commentedon Oct 27, 2026
Relationship note (2026-10-26 coherence review): the PM stack coherence epic is #1184 - it owns the stack's own coherence/UX/health (single-URL front door, freshness honesty, triage actions, queue visibility, hierarchy rollups, health page). This epic (#1129) remains the multi-project DOCUMENTATION program (/program hub + per-project pages). The two share surfaces (/program, /projects, /roadmap) but not scope: #1184 children should not duplicate #1120/#1121/#1122 work, and this epic's children should not absorb coherence fixes. Cross-references live in both epic bodies.
dezren39 commentedon Oct 27, 2026
Agent note — slice pickup (2026-10-27): a bounded aggregator PR is in progress carrying the #1186 route-status fix plus researched partial slices for #1124, #1125, #1126, and #1128. Parent build-out issues remain open except #1186, which the PR is intended to close.
dezren39 commentedon Oct 27, 2026
Agent note — slice complete (2026-10-27): PR #1305 MERGED (merge e246a33, verified via gh + git log), deployed to the laptop aggregator (restart 00:48 CDT) and verified live on loopback + MagicDNS. It closes #1186 (unknown /program/ now a real styled 404) and lands bounded partial slices of #1124 (status-report link + CPCOE-29381 gap), #1125 (validation wording, pkgs/id doc links, trackedRefs refresh), #1126 (stale #257/#292 editorial corrected, current fleet program + dated 665-issue scope note), and #1128 (cloud-program roadmapArea fix — OCI row renders). Those four parents stay open with slice notes recording what remains.
4 remaining items
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/none). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: picked-up
worker: repo-worker-code (lane c8b9355e-319a-4640-8096-7ad19480d151, openchamber scheduled lane)
task: 7645 (triage)
Coverage pass 2026-11-03: claiming the triage to decide close-vs-keep for this epic at current main. Prior 2026-11-01 note proposed closure if the nine children cover the acceptance; verifying that fresh (children states, live /program pages for all six projects, docs layer) before any close.
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: done (triaged → closed as complete)
worker: repo-worker-code (lane c8b9355e-319a-4640-8096-7ad19480d151, openchamber scheduled lane)
task: 7645
Verified at origin/main 4c75cc8 on 2026-11-03.
Children — all 9 CLOSED (fresh gh, not from the packet):
#1120 closed 2026-10-27 · #1121 2026-10-27 · #1122 2026-10-30 · #1123 2026-10-30 · #1124 2026-10-30 · #1125 2026-10-30 · #1126 2026-10-30 · #1127 2026-10-30 · #1128 2026-10-30.
Gating related issues also CLOSED: #911 (2026-11-01), #1110 (2026-10-27).
Registry (#1120/#1121) — pm-stack/aggregator/src/project-config.ts carries six entries: pm-dashboard (L101), lab-cluster (L119), id (L250), repo-fleet (L347), mcpx (L489), cloud-program (L555). One config per project; adding a project is a config change (README "Add a project").
Live pages (laptop aggregator :4870, this run):
projectslist of 6 with id/title/roadmapRows/homeDoc.Docs layer (#1123): aggregator README documents /program, /program/, JSON twins and the add-a-project recipe; home docs resolve for five projects (planning/roadmaps/{basement-cluster,id,repo-and-ci,mcpx}.md, pm-dashboard design doc) and the status-report layer is wired (statusReport config + lab-cluster's 2026-10-27 status doc). cloud-program has no homeDoc/statusReport — it renders as an honest "No home doc configured for this project yet" gap note, which is the designed null behaviour (#1120), not an empty section.
No open PR targets #1129 and no child is reopened, so nothing is pending to finish the epic. The only open issue in this neighbourhood is #1184 (PM-stack coherence), explicitly a separate scope per the 2026-10-26 relationship note.
Done-when check: six projects have live, sourced, documented pages; weighted visualization renders from real data; a reader can reach each project's description, status, roadmap, tracked work and home doc (or an explicit honest gap where one does not exist). Closing the epic as complete. Reopen if a phase was deliberately left unfiled — name it and it becomes the epic's next step.