I2789 — The intent workspace shows why an intent stands where it stands and every move made on its issues

✓DONE wave 3 · 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

Add to /ui/idd, for the open intent: a panel asked on its own route (/ui/panels/standing?intent=<id>) from intent_realization.explain — the sentences its stage and verdict rest on, each unmet criterion with its evidence state, the command that reproduces it and the issues serving it, the work realising the intent with each link's provenance, and its drift; and a panel from executions.list of every plan.transition this server ran on the intent's issues, newest first, each leading to its execution.

Why

The workspace shows what serves an intent and offers the next move, but not why the intent stands where it does or what was moved: the evidence and execution steps of the IDD loop are read on other surfaces, and intent_realization.explain takes seconds, so it cannot hold the screen's first paint.

Current state

intent_realization.explain and executions.list answer both questions; no screen reads them for an intent.

Desired state

/ui/idd shows the intent's standing from its own panel route and the moves made on its issues, both read only from those capabilities.

Scope

• apps/majordomus-cli/src/ui
• apps/majordomus-cli/tests/ui_idd_evidence.rs
• .ai/repo/project
• docs
• site
• .gitattributes

Dependencies

• I2783✓DONE The intent workspace reads itself again when a move ends on its server

What waits on this

• I2812✓DONE The IDD loop is accepted end to end in a real browser on one commit

Acceptance criteria

• The workspace's first paint does not ask intent_realization.explain; its placeholder names the panel route, and the route answers the intent's standing
• Each unmet criterion is shown with its evidence state, its reproduce command and the issues serving it, exactly as the capability answers
• A plan.transition started on one of the intent's issues is listed on the workspace, leading to its execution, and one on another intent's issue is not

Validation

• majordomus plan validate
• cargo test --test ui_idd_evidence

Evidence required

• ui_idd_evidence_tests

Evidence

Timeline

started

2026-10-19T09:58:57Z

verified

2026-10-19T09:59:14Z

completed

2026-10-19T09:59:24Z

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/I2789.yaml. Read it back with majordomus plan show I2789.