Repository navigation
test: Verify locked shared import provenance (ARCH-06A) - #511
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Compare source-loader code against a fresh compile of verified source. Cover stale timestamp and unchecked-hash caches in both import modes.
Pigbibi
marked this pull request as ready for review
November 2, 2026 04:58
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.
AI assistance
Implementation and this PR publication used Codex; the exact host model identifier was not exposed. A separate Codex AI agent reviewed the complete final diff and independently reran negative controls. The local receipt is unsigned and does not authenticate a trusted review identity.
What changed
Add an explicitly selected installed-lock pytest lane that binds shared dependency metadata to actual module origins and RECORD hashes in the collecting/running process. It rejects preloaded shared modules, sibling shadows, unknown origins and leaked test doubles. Default test import order stays unchanged.
Add 36 disposable negative controls, three safe real-parser/double contracts and concise documentation. Existing scanner/completion, coverage and verification steps remain in place. Production source, dependency declarations and lockfiles are unchanged.
How verified
Final local ordinary and instrumented suites each passed 1,776 tests and 118 subtests. Baseline collection was 1,737 tests; exactly 39 were added and none removed. Strict, repeated and reversed-order runs passed three tests each; incomplete selection and preloaded-module child processes failed without completion. Ruff, dependency/lock checks, documentation checks and package build passed. The package payload excludes test support. Coverage measured 71 files / 73% with the unchanged configuration, including the new support modules.
Full final diff and its preload correction received separate AI review at tree
92816a4ca9325d60cabb4f843d5f774b0150c895. These local results are taken from the ARCH-06 delivery report; tests were not rerun for this publication-only task. Hosted CI is pending and will be observed after this draft opens.Why
Ordinary test imports can resolve shared dependencies from sibling checkouts or test doubles, obscuring which locked implementation actually ran. This bounded parser lane makes the selected source contract explicit and rejects unverified origins.
Risk
High risk under the repository path policy because
.github/workflows/ci.ymlchanges. The additive step requires normal repository risk-gate evaluation. No approval label is requested or applied by this job. This bounded parser lane does not certify the ordinary full suite or eliminate its existing sibling-path ambiguity. No production, deployment, broker or cloud action is included. Keep the PR draft.