I2906 — Every id and chip on the workspace leads to its record
Make every milestone chip, the roadmap's current milestone and the issues that serve a criterion links: a milestone to /ui/roadmap?milestone=<id>, an issue to its inspector; one href per kind in ui/view.rs that /ui/mesh can reuse.
READY wave 5 · p1 · implementation profile · runs alone
Part of idd-reads-at-a-glance — The intent workspace reads at a glance and leads everywhere it names.
Ready. Every dependency is done, so majordomus plan start I2906 will be accepted.
Objective
Make every milestone chip, the roadmap's current milestone and the issues that serve a criterion links: a milestone to /ui/roadmap?milestone=<id>, an issue to its inspector; one href per kind in ui/view.rs that /ui/mesh can reuse.
Why
On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: \"Roadmap now M002\" and the milestone chips lead nowhere, and the issues under \"Issues that serve it\" are bare chips.
Current state
Milestone ids and served-by issues are text.
Desired state
Every id the workspace shows is a link.
Scope
- apps/majordomus-cli/src/ui/idd.rs
- apps/majordomus-cli/src/ui/intent.rs
- apps/majordomus-cli/src/ui/view.rs
- test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
- .ai/repo/project
- docs
- site
Dependencies
Acceptance criteria
- No milestone or issue id on /ui/idd is bare text
- Case 3220 asserts it for milestones as it does for issues
Validation
- majordomus plan validate
- bash test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
- scripts/ui audit --only /ui/idd
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
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/I2906.yaml. Read it back with majordomus plan show I2906.