Repository navigation
fix: stop queued sections after summary failure - #53
Merged
Merged
Conversation
This was referenced Nov 2, 2026
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.
Description
Closes #49. Stop claiming queued summary sections as soon as a worker fails, preserving the original error and the order/concurrency behavior of successful calls. Requests already started may settle. Updated the development guide to state that boundary.
Validation
PROVIDER_ERROR.npm run verify: lint, typecheck and all 313 tests pass.npm run test:coverage: all 313 tests pass; 94.5% statements and 84.49% branches, above configured floors.commit.gpgsign=falsefor synthetic Git fixture commits; no Git configuration was modified.Risks and rollback
Already-started provider requests are not cancelled and may still complete after the task returns an error. No permissions, provider payloads, settings or persistence formats change. Revert this commit to restore previous scheduling.