I2743 — The public roadmap draws every milestone in the graph's order, each issue with its inferred delivery
Rewrite site/templates/roadmap.html and site/content-src roadmap so /roadmap/ lists every milestone of the plan in the milestone graph's order (no filter on any hand field), shows released_in, each issue's declared status beside its inferred stage linked to the pull request, commit and tag that prove it, states the commit and time observed, and draws the milestone graph through the ADR 0152 viewer with nodes linked to milestone pages.
READY wave 1 · p0 · implementation profile · parallel safe
Ready. Every dependency is done, so majordomus plan start I2743 will be accepted.
Objective
Rewrite site/templates/roadmap.html and site/content-src roadmap so /roadmap/ lists every milestone of the plan in the milestone graph's order (no filter on any hand field), shows released_in, each issue's declared status beside its inferred stage linked to the pull request, commit and tag that prove it, states the commit and time observed, and draws the milestone graph through the ADR 0152 viewer with nodes linked to milestone pages.
Why
ADR 0166 decisions 4 and 6. The page lists 8 of 38 milestones and none of the work in flight; its front matter still names .majordomus/project/milestones/.
Current state
roadmap.html keeps milestones whose version is set; the issue counts are stamp-derived; nothing links a stage to its proof.
Desired state
One template over roadmap.json and delivery.json; scripts/site-check asserts that every milestone id of plan.json appears on /roadmap/.
Scope
- site/templates/roadmap.html
- site/templates/plan-section.html
- site/templates/milestone.html
- site/content-src
- site/content/roadmap.md
- scripts/site-check
- scripts/site-build
- docs/GITHUB_PAGES_ARCHITECTURE.md
- test/cases/3103_the_roadmap_draws_every_milestone.sh
Dependencies
- I2740DONE An issue's delivery is inferred from branches, pull requests, merges, tags and the published site
- I2742DONE A milestone's version is inferred from the release that carried it, never typed
Acceptance criteria
- Every milestone id in plan.json appears on the built /roadmap/, in the graph's order
- An issue with a merged pull request shows merged with a link to that pull request
- The page names the commit and time its data was observed
Validation
- bash test/run.sh 12_site_build 3103_the_roadmap_draws_every_milestone
Evidence required
- roadmap_complete_case
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| roadmap_complete_case | test | bash test/run.sh 3103_the_roadmap_draws_every_milestone | ok, 1 passed at 4d75789ea99: 13h green over the built page (39 milestones, 403 issues, graph order, observed commit), red over a dropped milestone, a reversed order and a wrong commit; delivery stage drawn only with delivery.json; mutations of the old filter and of the delivery path both turn it red | 4d75789 |
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2743.yaml. Read it back with majordomus plan show I2743.