I0101 — Reproduce the escaped blocker as an executable case
Write a behavioural case that runs the documented sequence — open a question, hand over, start a new task, finish completed — and records what happens today, so that the gap stops being a sentence in a claim note and becomes something a command demonstrates.
DONE wave 0 · p1 · debugging profile · parallel safe
Part of M001 — A blocking question survives a handover.
Objective
Write a behavioural case that runs the documented sequence — open a question, hand over, start a new task, finish completed — and records what happens today, so that the gap stops being a sentence in a claim note and becomes something a command demonstrates.
Why
A defect described in prose is a defect nobody can prove was fixed. The case has to exist before the fix, or the fix has no witness.
Current state
docs/CLAIMS.yaml says the blocker is escapable and cites no test. Nothing in test/cases exercises the sequence across a handover.
Desired state
A case in test/cases runs the sequence and asserts the behaviour that exists today, labelled as the gap it is, so that changing the behaviour turns it red and forces the claim and the case to move together.
Scope
- test/cases
Out of scope
- Any change to lib/question.sh or lib/check.sh
Dependencies
None. This issue is a root of the graph.
What waits on this
Acceptance criteria
- The case opens a question against a task, hands over, starts a new task, and reaches a completed finish
- It asserts the current outcome explicitly and says in a comment that this is the gap, not the goal
- It runs in a disposable repository like every other case
Validation
- bash test/run.sh 50_blocker_across_handover
Evidence required
- gap_reproduced
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| gap_reproduced | test | bash test/run.sh 50_blocker_across_handover | 1 passed, 0 failed — the case runs the documented sequence and asserts that a completed finish is accepted while a question raised by the same line of work is still unresolved | 82f23ef |
Risk
A characterisation test pinning the wrong behaviour is a trap if nobody reads the comment. The comment is the whole safety mechanism, so it has to be unmissable.
Timeline
- started
- 2026-09-04T04:12:46Z
- verified
- 2026-09-04T04:12:53Z
- completed
- 2026-09-04T04:12:54Z
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/I0101.yaml. Read it back with majordomus plan show I0101.