Repository navigation
fix: keep agent handoff and recovery on a fixed procedure - #270
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents use the fixed status → enqueue → stop handoff. Runner guidance exposes eligible batch work despite unrelated failures, and points an ordered queue at its current failed submission before historical verification warnings.
An ordered position completes when its Git push succeeds. Post-push verification warnings remain in Attention and history, so an approved corrective submission can land. Uncertain pushes still require reconciliation. Earlier unreleased ordered approvals are invalidated; published batch approval hashes, destination fencing, manual approval, retry order and default pre-push checks are preserved.
MCP terminal fallback retains the selected repository, configuration and queue. Duplicate errors identify the existing job, and inspect provides the existing retry command only for ordinary pre-push failures. Generated agent instructions and contract documentation match these procedures. No commands, options, modes, configuration fields or MCP tools are added.
Validation:
Mergetrain job 184 deployed ef0bfb6 to main. Push and post-push verification succeeded. The initial main rerun exposed an existing Windows cancellation-test startup race. #271 replaces the 0.5-second assumption with readiness from the actual gate subprocess and preserves all heartbeat/cancellation assertions. Its 15-job PR CI passed, and Mergetrain job 185 deployed the follow-up as 7966a90. Final workflows: main CI, demo.
Version remains 3.5.1. These changes stay under Unreleased for the next regular package release.