gen/integration contracts - #528
Open
Skidamek wants to merge 34 commits into
Open
Conversation
Skidamek
force-pushed
the
gen/integration-contracts
branch
from
August 20, 2026 11:12
6998245 to
543852a
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 69982454d4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
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.
Summary
This PR makes the boundaries between generation storage, release flow, bootstrap, file lifecycle, and legacy loaders executable.
It adds generation checkpoints and compaction receipts. A patch-note-only publication creates a new generation even when the file manifest is unchanged. Object source resolution handles extensionless content-addressed files, and generated nested copies carry generation state. Release, deletion, overlay, quarantine, and history fixtures check the corresponding storage and lifecycle contracts.
Most of the change is integration coverage. The autotester exercises authenticated bootstrap and preload, release gates, deletion and content convergence, editable overlays, quarantine restore, installed-pack removal, nested mod copies, client and server compaction, and trust roots. Legacy Forge coverage checks metadata, bootstrap ownership, readiness, disconnect recovery, and cache deserialization. The layer also makes test artifacts reproducible.
Coverage
The contract tests cover both normal releases and the legacy loader paths used by the stack.