A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0101
Reproduce the escaped blocker as an executable case
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- 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.
- Now
- docs/CLAIMS.yaml says the blocker is escapable and cites no test. Nothing in test/cases exercises the sequence across a handover.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- 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.
Acceptance
- 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 present
gap_reproduced
Scope
- Touches
test/cases- Not
Any change to lib/question.sh or lib/check.sh- Depends on
- none
- Priority
- p1
- Profile
- debugging
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04T04:12:54Z
- Started
- 2026-09-04T04:12:46Z
- Verified
- 2026-09-04T04:12:53Z
- Completed
- 2026-09-04T04:12:54Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.