Repository navigation
Lock dependencies and isolate reproducible delivery verification - #20
Merged
Merged
Conversation
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.
What changed
Make a fresh installation and full service verification independent of the operator's running stack and historical image cache. Lock Python dependencies/build tooling, pin base images, add read-only doctor, isolate fast checks/Mock, and add zero-skip full-service CI with aggregate-only artifacts. Map the native Linux Docker socket group while retaining non-root containers. The owned synthetic adapter regression now gets a separate temporary identity tied to the freshly built locked sandbox; historical manifests and real experiments retain their original identities.
Builds on the read-only analysis in merged #19. No application migration or new real-model experiment.
Evidence
Safety review
No credentials, OAuth directory or local reports enter builds. Verification forces Mock and disables publication, uses a fresh project/port/volumes, and uploads only aggregate service evidence. No global cleanup or socket permission weakening. Frozen source/test bytes and historical results are unchanged; new real-model requests: 0.
Resume claim impact
Adds reproducible installation and isolated engineering-delivery evidence. Supported Python versions are 3.12/3.13. No repair-quality improvement, exact billing, automatic crash recovery or Worker fencing claim.