I2919 — The graph and the intent list respond to a hand and a keyboard
A dependency graph node opens its issue when the vendored library is present (the table stays the fallback), and the intent list is navigable with the arrow keys and Enter, with an axe-clean focus order.
READY wave 0 · p2 · 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 I2919 will be accepted.
Objective
A dependency graph node opens its issue when the vendored library is present (the table stays the fallback), and the intent list is navigable with the arrow keys and Enter, with an axe-clean focus order.
Why
On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: the graph is a picture and the list needs a mouse.
Current state
A static graph.
Desired state
An interactive one, and a keyboard path.
Scope
- share/ui/ui.js
- apps/majordomus-cli/src/ui/idd.rs
- .ai/repo/project
- docs
- site
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- Clicking a node opens its issue
- The intent list is reachable and operable by keyboard
Validation
- majordomus plan validate
- 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/I2919.yaml. Read it back with majordomus plan show I2919.