Repository navigation
Keep conversation steering through final checkpoints - #415
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.
Keep rapid-fire messages attached to the active run through its final checkpoint. Pair with the loop-live fix in microsoft/amplifier-module-loop-live#13, reject worker admission once the completion gate closes, and verify three ordered messages reach the next request without another generation or replay.
Delivery feedback now distinguishes waiting for the next step from insertion into context; it no longer implies the model already acted on the message. Command receipts retain first observed queue/context timestamps for latency diagnosis.
Validation in the owned DTU: 20 Unified steering tests, 106 loop-live tests (four optional dependency skips), delivery UI tests, outbox browser flow and production frontend build passed. Model execution uses deterministic fixtures; no live-provider acceptance claim.
Depends on microsoft/amplifier-module-loop-live#13 landing before rollout. Preserve the repository’s main-tracking runtime dependency policy; DTU validation uses loop-live commit 46723db070e31c68d847b8997285d88f2f06e669. Synchronous tools can still delay the next model request. This change does not add provider-native steering or make natural-language pause a hard cancellation command.