Add the resolver runway to the run-bounds recitation#1265
Merged
Conversation
The resolve cap is the harshest of the silent bounds: an over-cap spawn wave is refused and the run continues, but an over-cap resolve force-stops the whole run (ResolveAttemptsExceeded) — and the decider could not see the count. With the default cap of 1, the model's first resolve already stands at the cliff edge; the next one is the run's death, spent blind. The turn context now carries the plan's MaxResolveAttempts (the same plumbing as MaxTotalSpawns), the RUN BOUNDS recitation renders the attempt count against the effective cap with the fail-safe exit named (stop and leave the conflict to a human — mirroring the resolution verdict's own copy), and the prompt counts resolves off the tape exactly the way SupervisorBounds.PostDecision does, so producer and recitation cannot drift. Zero counters still render nothing.
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
1 participant
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.
Summary
ResolveAttemptsExceeded) — and with the default cap of 1, the first resolve already stands at the cliff edge. The line names the distinction and the fail-safe exit ("stop and leave the conflict to a human", mirroringAppendResolutionVerdict's copy — no new verbs for the model to pick up wrongly).SupervisorTurnContext.MaxResolveAttemptscarried from the plan (same plumbing asMaxTotalSpawns; null legacy contexts fall back toDefaultMaxResolveAttempts); the prompt counts resolves offPriorDecisionsexactly the waySupervisorBounds.PostDecisioncounts them, so the bound and its recitation cannot drift.Test plan