Development record
Under facilitator.mode auto, an implement-loop lane can never arm its own pull request: the land stage commits the lane's resolved issue record after the last validation round, so no review receipt names the head it pushes, and the gate arms nothing until a second review pair is run by hand over that records-only commit and recorded with abcd land --record-review.
issueopenminoriss-2610311732460169
Under facilitator.mode auto, an implement-loop lane can never arm its own pull request: the land stage commits the lane's resolved issue record after the last validation round, so no review receipt names the head it pushes, and the gate arms nothing until a second review pair is run by hand over that records-only commit and recorded with abcd land --record-review.
Frontmatter
| id | iss-2610311732460169 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610311732460169-under-facilitator-mode-auto-an.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2611012054270386abcd land's review receipt needs a review pair, and outside a loop's own validate stage nothing can run that pair on the runner: a loop's records commit that is not mark-only (the self-minted receipt iss-2610311732460169 and iss-2610312044511316 propose covers only mark-only commits) and the pair for any records or docs branch are started as host subagents and billed to the subscription, so with the subscription nearly spent on 2026-11-01 every records pull request under facilitator.mode auto either spends it or waits (internal/core/landing/facilitator.go reads the receipt; no verb produces one on a runner).