Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2743

The public roadmap draws every milestone in the graph's order, each issue with its inferred delivery

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
1
Waiting on
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI2740I2740 is not DONE
issueI2742I2742 is not DONE
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2743

majordomus plan verify I2743

majordomus plan done I2743

What it is

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/.
Now
roadmap.html keeps milestones whose version is set; the issue counts are stamp-derived; nothing links a stage to its proof.
Wanted
One template over roadmap.json and delivery.json; scripts/site-check asserts that every milestone id of plan.json appears on /roadmap/.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • 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 present
unknown: the record carries no `evidence` entries

Scope

Touches
site/templates/roadmap.htmlsite/templates/plan-section.htmlsite/templates/milestone.htmlsite/content-srcsite/content/roadmap.mdscripts/site-checktest/cases/3103_the_roadmap_draws_every_milestone.sh
Not
unknown: the record declares no `non_scope`
Depends on
Priority
p0
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-16
Updated
2026-10-16
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.