AGENTS.md "Context and Delegation Discipline" carries an exception for a session orchestrating dispatched work:
The triggers above land on each dispatched task instead, one branch and one deliverable each, which is this rule applied rather than waived.
With the session-end triggers moved off it, that session is left with no ending condition of any kind. "One deliverable, one session ... ends when that work merges" does not reach it either, because its deliverable is the run and a run never merges. backlog-burndown has an "Ending the Run" section, but spec/files.json marks this AGENTS.md section "fidelity": "verbatim" and "appliesTo": "*", so it is carried byte-locked into every fleet repo and has to stand without any hub skill completing it.
Related, in the same bullet: "A session that starts editing the files a dispatched task would have edited is an ordinary one again and ends on the triggers above." Read literally, one such edit obliges the session to end at the next dispatched merge, abandoning the run mid-flight, and the bullet names no handoff step for that transition. If the intent is a prohibition on making such an edit at all, the sentence does not say so.
See #1286 for the other half of this, which is that an ordinary drive-pr to-main session is caught by two triggers it must cross mid-deliverable.
Raised by the local-strict-review carried-content passes on the pull request that added backlog-burndown, which edited this section, and deferred there under that skill's own review-round budget.
AGENTS.md"Context and Delegation Discipline" carries an exception for a session orchestrating dispatched work:With the session-end triggers moved off it, that session is left with no ending condition of any kind. "One deliverable, one session ... ends when that work merges" does not reach it either, because its deliverable is the run and a run never merges.
backlog-burndownhas an "Ending the Run" section, butspec/files.jsonmarks thisAGENTS.mdsection"fidelity": "verbatim"and"appliesTo": "*", so it is carried byte-locked into every fleet repo and has to stand without any hub skill completing it.Related, in the same bullet: "A session that starts editing the files a dispatched task would have edited is an ordinary one again and ends on the triggers above." Read literally, one such edit obliges the session to end at the next dispatched merge, abandoning the run mid-flight, and the bullet names no handoff step for that transition. If the intent is a prohibition on making such an edit at all, the sentence does not say so.
See #1286 for the other half of this, which is that an ordinary
drive-prto-main session is caught by two triggers it must cross mid-deliverable.Raised by the local-strict-review carried-content passes on the pull request that added
backlog-burndown, which edited this section, and deferred there under that skill's own review-round budget.