I2781 — An issue is started, verified and finished from the intent workspace
Render, for the issue picked in /ui/idd, the same plan.transition form the Cockpit's issue page offers — start, verify, done — started through executions.start and followed through executions.get, with the effect the capability declares confirmed before the move, the buttons disabled while it runs, and the refusal's own reason shown when the plan does not allow the move.
DONE wave 1 · p0 · 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
Render, for the issue picked in /ui/idd, the same plan.transition form the Cockpit's issue page offers — start, verify, done — started through executions.start and followed through executions.get, with the effect the capability declares confirmed before the move, the buttons disabled while it runs, and the refusal's own reason shown when the plan does not allow the move.
Why
The first slice links a ready issue to the Cockpit's move; the criterion asks for the move where the work is read, and the form, its script and the capability already exist.
Current state
Moves are offered on /cockpit/plan/issues/<id> only.
Desired state
/ui/idd?issue=<id> offers the moves with the result in place; the screen reads again after a move succeeds.
Scope
- apps/majordomus-cli/src/ui
- apps/majordomus-cli/src/cockpit/plan.rs
- apps/majordomus-cli/tests/ui_idd_moves.rs
- share/ui/ui.js
- share/cockpit/api.js
- share/cockpit/moves.js
- share/cockpit/plan.js
- share/cockpit/cockpit.js
- docs/MAJORDOMUS_UI.md
Dependencies
What waits on this
Acceptance criteria
- A ready issue is started from /ui/idd and its status reads ACTIVE on the next paint
- A move the plan refuses shows the refusal's reason and changes nothing
- A double click starts one execution
- A request from another origin is refused by the server, not by the page
Validation
- majordomus plan validate
- cargo test --lib ui::idd
- cargo test --test ui_idd_moves
Evidence required
- ui_idd_moves_tests
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| ui_idd_moves_tests | ci | validate run 39192952944 at master dd4c0a87cba: rust (1-3) runs cargo test --test ui_idd_moves and --lib ui::idd | success | dd4c0a8 |
Timeline
- started
- 2026-10-19T13:54:02Z
- verified
- —
- completed
- 2026-10-19T13:54: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/I2781.yaml. Read it back with majordomus plan show I2781.