Repository navigation
Reuse current reader data for fast read-only Reply opening - #24
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This was referenced Oct 22, 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.
Opening Reply repeated six serial Host authority round trips and downloaded an already rendered original message again. Live Runtime26 evidence showed 7.67 seconds in authority versus 0.38 seconds in the provider read for one completed hydration; other attempts exhausted the Host opening budget before reaching the provider.
Source-seeded metadata now uses the existing optimistic read path and the exact current reader presentation memo. Fresh entry/session/disclosure checks remain online; cold reads also keep the pre-provider check. Current custody generation, source digest and durable snapshot checks fence disclosure. The first persisted create still revalidates the original source and preserves user edits. No authority decision is cached, consent is unchanged, and opening creates no draft.
Prepares Email29 / App10 / Runtime27 with unchanged public Kit42 bytes and minimum Host136. Release/deployment remains held for the coordinated Host137 acceptance step; this PR makes no live acceptance claim.
Validation:
No live edit, save, permission review, reconnect, Send, deployment or release was performed.
🤖 Generated with Claude Code