Repository navigation
docs(dashboard): document the per-project pages — README, spec alignment, home docs, status reports #1123
Description
Summary
Documentation completeness for the per-project pages program (Drew, 2026-10-26: "all aspects are documented and have appropriate issues and descriptions"). The code/docs side of the epic:
Work
- Aggregator README: /program hub + /program/ documented in the views table; the project-registry recipe ("add a project") written next to the existing page-manifest recipe; the registry file named in the layout/file list.
- Project-structure spec alignment: the dashboard pages implement layer 3/4 rendering of the 2026-10-26 project-structure spec (goal workspace, lab-cluster). Where implementation diverges from the spec, either fix the implementation or amend the spec — record which, in the spec file, dated.
- Per-project home docs: every configured project links its planning/roadmaps/.md home (or its design-record equivalent); homes that don't exist yet (basement-cluster.md) are created by the owning project's seeding work — this issue tracks that every /program/ home link resolves to a real file on main, and files follow-up issues where a home is missing rather than leaving a dead link.
- Status-report layer (spec layer 2): each project page links its latest dated status record (doc/status/) when one exists; when none exists the page says "no status report yet" — and the per-project issues in the epic carry the first-report task.
- /pages and nav: /program's manifest blurb updated to describe the hub; no other chrome changes.
Acceptance
- Every link on every /program/ page resolves (checked against the repo on main + live dashboard).
- README + spec tell the same story as the shipped pages.
- A reader starting from the dashboard alone can reach: project description, current status, roadmap, tracked work, and the project's home doc — for every configured project.
Refs: #1046, project-structure spec (2026-10-26).
Activity
developing-today commentedon Oct 27, 2026
CODE-261
dezren39 commentedon Oct 27, 2026
Epic: #1129 — per-project status pages for all projects (generalize /program beyond pm-dashboard).
dezren39 commentedon Oct 29, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 29, 2026
🤖 Agent note · done
bd88019448ad397cdbcadaf8e0d29171fb1d661dEvidence (fresh GitHub reads at HEAD):
pm-stack/aggregator/README.mdviews table documents/program(projects index, Dashboard: add program status/roadmap page (/program) #1046/impl(aggregator): /program hub + /program/<project> pages for all configured projects #1121) and/program/<id>(all six projects named), the "add a project" registry recipe sits next to the page-manifest recipe, andproject-config.tsis named in the layout/file list.src/pages.ts/program blurb reads "The projects hub: every project's status, roadmap, and tracked work, one page per project under /program/…".src/render.tsrenderProgramProjectpushes aStatus report:link onlyif (config.statusReport)and renders nothing otherwise — unlike the home-doc branch directly above it, which states the gap. Only lab-cluster has a statusReport insrc/project-config.ts(2026-10-27, basement-cluster); the other five pages silently omit the layer instead of saying "no status report yet".Route: first remaining slice enqueued as queue task 3020 (
small_fix, deduperepo-health:v1:fix:developing-today/code:issue:1123): render a "no status report yet" note on project pages without a statusReport (mirroring the home-doc pattern) + a both-branches render test. The cloud-program home doc and the item-2 spec-alignment record stay on this issue as later slices. The issue stays open; this triage task completes astriaged.35 remaining items
dezren39 commentedon Oct 29, 2026
Agent note — merge-ready, enqueued, parked on the merge queue (#2403)
Queue task 3020 resumed by Lane B. PR #2395 verified fresh: head
b08d7806, diff is exactly the packet slice (render.ts no-status-report note + both-branch assertions in program.test.ts), Codex review completed with no findings, checks green, MERGEABLE/CLEAN. Independently re-ran the defining test on the laptop worktree:bun test test/program.test.ts— 14 pass / 0 fail.The PR has been enqueued in the merge queue (position 1, AWAITING_CHECKS at park time). #2403 documents the queue ejecting entries 2–6 minutes into AWAITING_CHECKS with no merge landing since #2233, so this task parks instead of waiting: resume by checking the queue entry — if it merged, complete task 3020 (issue #1123 stays open for its remaining slices); if it was ejected, re-enqueue once #2403 is fixed.
dezren39 commentedon Oct 30, 2026
🤖 Agent note · done — merged
repo-worker-code), OpenChamber scheduled lanerenderProgramProjectgained the else branchNo status report yet for this project.(mirroring the home-doc pattern), plus both-branch assertions intest/program.test.ts.origin/main(2e01ec1) merged into the branch, conflict-free;bun test test/program.test.ts— 14 pass / 0 fail; diff against main is exactly 2 files / +8 lines, matching the packet.562663favia the merge queue (entry was stuck in AWAITING_CHECKS until a merge_group runner picked it up; ci: merge queue ejects every PR — no merge since #2233 (10:57Z), entries dropped 2-6 min into AWAITING_CHECKS #2403's settings fix holds).