Keep scoped bundle registry views out of shared persistence - #409
Merged
Merged
Conversation
Brian Krabach (bkrabach)
marked this pull request as ready for review
September 22, 2026 11:22
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
1 participant
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.
Session-local bundle aliases can leak to later sessions because ordinary loads and include tracking persist the registry. Add an opt-in
BundleRegistry(persist=False)view: it reads shared registrations and uses the normal source cache, but all registration, source identity, relationship and stale-path changes remain in that instance, including explicitsave()calls. The default persistent registry API is unchanged.Validation: 80 registry/source-binding tests pass, including sequential and concurrent scoped views, exact URI aliases, transitive self namespaces, failure isolation, stale-path cleanup, explicit global registration/update, and byte-identical baseline registry state. No model calls, production registry edits, or host restarts were used.
Unified will use this capability for session preparation in a companion PR. This is generic registry infrastructure and contains no bundle-specific policy.