I2812 — The IDD loop is accepted end to end in a real browser on one commit
Add case 3220: on a fixture repository and a real server, a real browser picks a test intent in /ui/idd, reads its issues and the dependency between them, starts an issue from its move form, sees the row change without the test reloading, writes and commits the work, runs the issue's own check as a real test and records its command and result as evidence, verifies the issue from a second tab while the first shows it without navigating, marks it done, and reads the standing panel's explanation and the issue page's evidence; the recorded command, run again, gives the recorded result. No feature is added.
DONE wave 4 · 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
Add case 3220: on a fixture repository and a real server, a real browser picks a test intent in /ui/idd, reads its issues and the dependency between them, starts an issue from its move form, sees the row change without the test reloading, writes and commits the work, runs the issue's own check as a real test and records its command and result as evidence, verifies the issue from a second tab while the first shows it without navigating, marks it done, and reads the standing panel's explanation and the issue page's evidence; the recorded command, run again, gives the recorded result. No feature is added.
Why
The owner's acceptance for v1.0.0-alpha.1 is the IDD loop walked once, on one exact commit, in CI: the pieces each have their own tests, and nothing proved that they make one loop a person can walk.
Current state
Each step of the loop is tested on its own (ui_idd, ui_idd_moves, ui_idd_live, ui_idd_evidence); none walks them together in a browser.
Desired state
One case walks the whole loop in a real browser in the suite, and fails under CI when no browser runs it.
Scope
- test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
- .github/workflows/validate.yml
- .ai/repo/ci/gates.yaml
- .ai/repo/project
- docs
- site
Dependencies
What waits on this
- I2900DONE 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
- I2906READY Every id and chip on the workspace leads to its record
- I2907DONE The workspace's headline numbers are the chosen intent's
- I3213BLOCKED One case walks a fresh clone from init to published evidence on the release candidate
- I3216BLOCKED The IDD loop is accepted at a phone's width as it is at a desktop's
Acceptance criteria
- The case walks pick, read, move, test, live, done, explained, evidence and reproduced, each step printed, and fails naming the step that did not happen
- Under CI=true a missing browser fails the case
Validation
- majordomus plan validate
- bash test/run.sh 3220_the_idd_loop_is_walked_in_a_browser
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 (--runs-in ui) of validate run 39137437606 on 2dfff96988a, the v0.30.0 top carrying I2812's merge 627eae88290 | dd4c0a8 |
Timeline
- started
- 2026-10-19T09:59:34Z
- verified
- 2026-10-19T09:59:50Z
- completed
- 2026-10-19T10:00:01Z
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/I2812.yaml. Read it back with majordomus plan show I2812.