Repository navigation
Release 0.96.3: reduce repeated browser notice work - #2109
Merged
Brian Krabach (bkrabach) merged 2 commits intoNov 15, 2026
Merged
Conversation
Brian Krabach (bkrabach)
changed the title
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.
Browser snapshots repeated the same global notice/read join for selected items, off-page decision receipts, presence and counts. Build those results from one materialized query, keeping exact notice order, fingerprints, selected bodies and transaction boundaries. This reduces the maintained 600-owner/20,000-receipt fixture from 1,178,400 to 465,400 SQLite instructions.
Validation: exact legacy attention oracles, concurrent rename/rollback, dormant-body isolation, changed fingerprints and native catalog bounds. Focused publication, stream and real-pipe tool acceptance are recorded in the review packet; no persistence format, permissions, cache lifetime or provider changes. An unrelated failed-terminal test also fails on unchanged main and is retained separately.
This PR also prepares 0.96.3, a patch for existing behavior. Canonical client build and locked dev/artifacts dry-run passed; generated client bytes are unchanged. No high-impact notice is needed. Independent source review is clear on feature6c4ce638a; final successor changes only the four release metadata files. Final focused checks:33passed; real-pipe/tool acceptance and four-window Chromium workload pass. The browser workload retained all drafts across22,915chats/3,932workspaces. Exact published-package smoke and live Spark-2 adoption follow the normal release path.