Repository navigation
fix(prime): retain safe session closure diagnostics - #607
Merged
Merged
Conversation
…king private errors
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This was referenced Sep 18, 2026
This branch was successfully 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
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.
Unexpected Prime session closures were reduced to a generic “stopped before sending a final response” error, leaving no safe way to distinguish provider closure from internal proof, capacity, snapshot, or MCP recovery failures.
Record a bounded internal closure classification and generation metadata in provider event logs. Ignore classifications supplied by raw provider events, retain private-error redaction, and preserve existing terminal behavior and recovery fences. This is diagnostic instrumentation: the historical incident could not be reproduced or assigned a proven root cause from the available logs.
Validation: 574 tests across the four focused Prime daemon runtime, adapter, and event suites; scoped lint; server typecheck (existing Effect suggestions only); diff whitespace check. Includes regression coverage for private-error suppression, untrusted diagnostic fields, and internally synthesized recovery failures. No client or wire changes.
Implemented through Pylon delegation by Antigravity (gemini-3.8-flash-high); reviewed, corrected, and verified by GPT-6 in the Codex harness.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.