Development record
On 2026-11-01 at 00:39 abcd implement receipt refused a build run's receipt because the run's state.json was schema version 17 and the binary that answered reads versions 1 to 16. The run had been started through the main checkout's scripts/abcd.sh, which builds and runs whatever that checkout has checked out; a peer session working in the same main checkout switched its branch to an older one in between, so the next invocation rebuilt an older binary under the running session. A session's abcd should not change because a peer switched the shared checkout, and the refusal's remedy (abcd update) does not apply to a source checkout.
On 2026-11-01 at 00:39 abcd implement receipt refused a build run's receipt because the run's state.json was schema version 17 and the binary that answered reads versions 1 to 16. The run had been started through the main checkout's scripts/abcd.sh, which builds and runs whatever that checkout has checked out; a peer session working in the same main checkout switched its branch to an older one in between, so the next invocation rebuilt an older binary under the running session. A session's abcd should not change because a peer switched the shared checkout, and the refusal's remedy (abcd update) does not apply to a source checkout.
Frontmatter
| id | iss-2611010041545467 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2611010041545467-on-2026-11-01-at-00-39-abcd-implement.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26110109331595742026-11-01 — iss-2611010041545467 is resolved by the remedy change alone. A source checkout's build refusing a newer run or drain state now says that abcd update does not change it, and tells the person to run the command from the same directory with the scripts/abcd.sh of a newer checkout, such as a worktree of origin/main; this was proved live on 2026-11-01 against a schema-17 run in the main checkout. Two parts of the issue's remedy are not taken. Recording the writing abcd's version and commit in the run state would bump the state schema, and every bump makes every older build refuse every run the newer one touches, the very refusal this fixes, for a gain of one named commit in a message that already names a working route. A CONCURRENCY rule that a session drives its runs from its own worktree's scripts/abcd.sh is not added, because a run lives in the local tier of the checkout that started it, so the rule would strand every run already started in a main checkout; the refusal now teaches the route at the moment it is needed.