Repository navigation
Anchor opt-in steering to one generation and preserve uncertain outcomes - #12
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.
Anchored steering now targets one live generation and reports whether its context update was applied, held without execution, or has an unknown outcome. Previously, a steering input accepted near the end of a turn could remain in the loop inbox and start a new turn after the original finished.
The opt-in
live.steeringv1 capability exposessubmit_steeringwith an immutable generation ID. Request-boundary steering is supported; provider-native steering explicitly reports unavailable until it can prove safe disposition. Existing unanchored standalone inputs retain their current behavior.Validation: 101 tests passed, 4 optional integration tests skipped (provider/context dependencies absent). Deterministic tests cover application, late completion, cancellation, interrupted context writes, generation mismatch, and unaffected unanchored behavior. The native ACP adapter and AHP host also passed an independent-process Core/Foundation fixture with both applied and late-held inputs; no model account calls were made. See
docs/anchored-steering.mdfor the public contract and limitations.