Share exact Git sources and reuse installs within preparation attempts - #415
Merged
Merged
Conversation
This was referenced Oct 1, 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
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.
Repeated bundle and module preparation clones the same Git source and repeats installations within one update attempt. Add an opt-in shared store with immutable exact-commit objects and per-cache bindings, plus installation receipts valid only within one preparation attempt while source, policy and installed metadata still match.
Build backends use a serialized writable view and install wheels; shared objects remain read-only. Existing local edits, legacy caches, non-Git handlers and consumers that do not opt in retain their current behavior.
Validation: 111 focused source, refresh and activation tests passed, followed by two real offline uv installation tests (including wheel installation from shared storage). Follow-up source and long-path coverage: 83 tests passed after adding long-path-safe shared-object verification and an explicit private Windows fixture home. New modules and shared-source tests pass Ruff. These are local tests, not deployment acceptance.
This supplies the optional API used by the related Skills and Amplifier Unified update-efficiency changes. Recommended merge order: Foundation, Skills, Unified. See docs/shared-source-store.md for contracts and compatibility boundaries.
Related consumer PRs: microsoft/amplifier-bundle-skills#83 and microsoft/amplifier-unified#315.
Hosts can opt out of saved registry reads using
read_persisted=False, whileCLI/library defaults continue reading their existing registrations. Unified
uses settings as registration authority without importing CLI registry/cache.
Follow-up registry coverage: 61 tests passed, including unchanged defaults and
no-read/no-write isolation.