Repository navigation
Conversation
This branch has not been deployed
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.
Default map discovery reconstructs the embedded dataset catalog after DataRelease has already verified it. Reuse that verification and its existing stat cache while retaining the campus identity-schema check.
Keep published SQLite catalog verification, default module map/entity/boundary readers, and publication on the SHA-verified main file. Explicit mutable paths and required-path cached stores retain their read-only WAL behavior. The engine boundary attachment keeps its existing catalog-build fence; this change does not make every engine attachment immutable.
Validation: independent adversarial review of the exact seven-file diff; full canonical scripts/check on Python 3.14.10 and 3.15.2, each with 563 passed and 1 skipped, plus Ruff, ty, dependency checks, and explicit receipt verification. The skipped PostgreSQL round-trip requires a fresh opt-in test database.
This removes duplicate work and aligns artifact integrity checks. Memory behavior and application runtime qualification remain separate gates.