Repository navigation
Preserve storage diagnostics while recording session errors - #122
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
2 participants
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 the original storage failure when persisting its transcript-only error notice also fails. Saving a diagnostic no longer masks the failed checkpoint with a generic message-write error.
Update failed-compaction and blocked-input assertions for durable error notices, and explicitly select Chat Completions in the existing reasoning HTTP fixture, whose server only implements that protocol.
Validation: 41 focused regressions passed. Full Windows regression passed: 6229 passed, 9 skipped, zero failures, one disabled benchmark (6239 inventory entries). Strict source/OpenSpec checks and
git diff --checkpassed. This completes the v1.0.3 integration follow-up to #120 and #121.