Skip to content

backlog-burndown: Promotion Boundary step 5 dispatches a worker under the freeze step 6 forbids #1273

Description

@ptr727

In backlog-burndown "The Promotion Boundary", step 5 ends by dispatching a worker, and step 6 forbids exactly that.

Step 5: "The orchestrator retires that group's worktree ... and then dispatches a fresh worker on that same branch, briefed either to merge develop in to pick the fix up or to narrow the change to drop the file."

Step 6: "Nothing else pushes, and nothing else is dispatched. The promotion fix of step 4 is the one exception to both."

That fresh worker's one procedure is drive-pr, "whose second step pushes and opens a pull request", so it is both a second dispatch and a second pusher under the freeze. Step 5 says the opposite two sentences earlier, "waits untouched until the freeze lifts" and "Reconciling its content is the next round's worker's job", so the dispatch has no stated timing and cannot legally happen where the step puts it.

The fix is presumably to state that the retire happens when the freeze lifts and the dispatch is the next round's, rather than both being step 5's, but the ordering is a design call rather than a wording one.

Raised by a local-strict-review carried-content pass on the pull request that added this skill, and deferred there under that skill's own review-round budget.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    decisionNeeds the maintainer's decision before it can be workedskillsAgent skill

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions