Repository navigation
Preserve accepted steering through generation completion - #13
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.
Accepted generation-bound steering could wait behind manager inbox processing or be held when it arrived during the final checkpoint. Admit it directly to the request-boundary queue and continue the same generation when accepted input remains after a normal checkpoint. Close admission synchronously before terminal publication, so later arrivals fail before acceptance.
Preserves input identities, FIFO batches, original prompts, completed tools and explicit stop/cancellation/budget boundaries. Existing background-job waits also observe the direct steering queue. Provider-native steering remains unchanged.
Validation in an owned DTU: 106 tests passed, four optional native-provider/context-managed tests skipped; wheel/source build passed. New real Core/context/loop tests use scripted providers and tools to cover bursts during model/tool execution, checkpoint continuation, completion admission, cancellation, exhausted budget and waking a parent while its child continues. No live model or production execution was performed.