I2900 — Every issue id on the intent workspace is a link, the shared-scope pairs are one folded line, and no missing library is asked for
On /ui/idd, the plan's next issue tile leads to that issue, and each shared-scope pair names both of its issues as links; the pairs fold into one line that gives their count and opens to them. The UI names the vendored graph library only when the distribution holds it, so a checkout without it serves the graph's table with no request, no 404 and no console error. Case 3220 asserts all three in a real browser. No new feature.
DONE wave 5 · p1 · implementation profile · runs alone
Part of idd-workspace — The UI is where the owner directs the work, from an intent to its next move.
Objective
On /ui/idd, the plan's next issue tile leads to that issue, and each shared-scope pair names both of its issues as links; the pairs fold into one line that gives their count and opens to them. The UI names the vendored graph library only when the distribution holds it, so a checkout without it serves the graph's table with no request, no 404 and no console error. Case 3220 asserts all three in a real browser. No new feature.
Why
A read of the workspace on 2026-10-17 (a3) found most issue ids in its text were not links — the plan's next issue and every id of the shared-scope lines — the shared-scope lines outweighed the waves they qualify on an intent of three issues, and every /ui/idd load on a fresh master checkout asked for the untracked cytoscape.min.js, a 404 and a console error on the alpha's product page.
Current state
The next-issue tile and the shared-scope lines show issue ids as text; the pairs are listed in full under a heading.
Desired state
Every issue id the workspace shows is a link, and the pairs are one counted, folded line.
Scope
- apps/majordomus-cli/src/ui/idd.rs
- test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
- .ai/repo/project
- docs
- site
- .gitattributes
Dependencies
Acceptance criteria
- No issue id in the workspace's main is bare text
- The shared-scope pairs are one closed disclosure whose summary gives their count, and open to links to both issues of each pair
- A distribution without the vendored graph library is never asked for it: no request, no failed response, no console error
Validation
- bash test/run.sh --runs-in ui
- cargo test --test ui_idd
Evidence required
- idd_loop_case
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| idd_loop_case | ci | gh run view --job 117706042728 --log | ok 3220_the_idd_loop_is_walked_in_a_browser in the ui job of validate run 39137437606 on 2dfff96988a, the v0.30.0 top carrying I2900's merge a119ab21337 | dd4c0a8 |
Timeline
- started
- 2026-10-19T10:00:11Z
- verified
- 2026-10-19T10:00:28Z
- completed
- 2026-10-19T10:00:37Z
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/I2900.yaml. Read it back with majordomus plan show I2900.