Repository navigation
Conversation
This branch has not been deployed
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.
When a subagent task is cancelled while it is still queued, its factory never starts and consumers receive no lifecycle signal for that skipped run. This adds an opt-in, inert-by-default hook that reports the skipped task once with its task and scope identity.
The hook does not report work after the factory has entered. A throwing observer leaves task state and counters intact.
Focused coverage in
InMemorySubagentTaskStore.run-skipped.spec.tsverifies queued cancellation, the factory-entry boundary, task/scope isolation, observer exceptions, and the inert default. All five cases pass against current upstreammain(97b2db3a). No dependency or public protocol changes are included.