AGENTS.md "Session Scope" says a session "covers one branch and one deliverable, and ends when that work merges", and ends at "the branch changes, the pull request merges, or the next task is unrelated to the last". It then carves out one exception, for a session orchestrating dispatched work.
A session running drive-pr in its all-the-way-to-main mode fits neither shape:
- It holds a branch of its own and authors the work, so it is not the orchestrating exception.
- The trigger "the pull request merges" fires at
drive-pr step 4, "Merge the feature PR into develop", which is not the end of the deliverable. Following AGENTS.md literally ends the session there, before step 6's "land the fix as a fresh pass through steps 1 to 4 ... then return here" can run. That is exactly the early exit drive-pr's own description says it exists to prevent.
- The trigger "the branch changes" fires too, since step 6 lands each promotion-PR fix "in its own worktree and branch", so a single blessed drive changes branch repeatedly.
- The deliverable-landing merge is the
develop -> main one, which that session is forbidden to perform: drive-pr step 9 is "Report the promotion PR number and its ready state. Do not merge it."
So a to-main drive has no merge-based end it is allowed to reach, and two triggers that fire before it is done.
An attempt to settle this by adding a sentence to the exception bullet was reverted before merge, because it redefined which merge ends such a session without reconciling the "one branch" and "the branch changes" halves, and because the merge it named is the one drive-pr forbids that seat to make.
The design question, which is the maintainer's: does a to-main drive end at the promotion PR being reported ready (a fourth trigger, not a merge), or is it a second exception, or does "one deliverable" absorb the branch changes step 6 makes? AGENTS.md is the only surface stating the session-scope rule, so nothing else corrects it.
Raised by the local-strict-review passes on the pull request that added backlog-burndown, and deferred there under that skill's own review-round budget.
AGENTS.md"Session Scope" says a session "covers one branch and one deliverable, and ends when that work merges", and ends at "the branch changes, the pull request merges, or the next task is unrelated to the last". It then carves out one exception, for a session orchestrating dispatched work.A session running
drive-prin its all-the-way-to-main mode fits neither shape:drive-prstep 4, "Merge the feature PR into develop", which is not the end of the deliverable. FollowingAGENTS.mdliterally ends the session there, before step 6's "land the fix as a fresh pass through steps 1 to 4 ... then return here" can run. That is exactly the early exitdrive-pr's own description says it exists to prevent.develop -> mainone, which that session is forbidden to perform:drive-prstep 9 is "Report the promotion PR number and its ready state. Do not merge it."So a to-main drive has no merge-based end it is allowed to reach, and two triggers that fire before it is done.
An attempt to settle this by adding a sentence to the exception bullet was reverted before merge, because it redefined which merge ends such a session without reconciling the "one branch" and "the branch changes" halves, and because the merge it named is the one
drive-prforbids that seat to make.The design question, which is the maintainer's: does a to-main drive end at the promotion PR being reported ready (a fourth trigger, not a merge), or is it a second exception, or does "one deliverable" absorb the branch changes step 6 makes?
AGENTS.mdis the only surface stating the session-scope rule, so nothing else corrects it.Raised by the local-strict-review passes on the pull request that added
backlog-burndown, and deferred there under that skill's own review-round budget.