Repository navigation
Add bounded Catalog materializer and delegated executor for v0.14.40 - #12
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.
The private Catalog launch materializer uses the existing Compose owner through bounded inspect/finalize phases and exact request skeletons. Delegated execution uses an event-local proof client bound to the exact Stack; control replies retain the trusted service channel. Missing/invalid proof cannot fall back to the launcher Full Key. Ordinary CLI/UI execution remains unchanged.
This prepares unpublished v0.14.40. Matching Engine live actor/Key read+create+update checks, private proxy blocking, encrypted plans, human confirmation, exact graph/ledger and deployment observation remain required. Unsupported graph shapes fail closed. The pinned legacy Server verifies ordinary compatibility only; runtime/browser/roles acceptance is pending.
Builder maintenance retains the exact pip wheel and Go dependencies. Each actual builder must now prove its 299 live vendor files, affected-module absence, exact seed/SBOM hashes and complete source inventory before narrow pip VEX applies. Unknown SBOMs, complete distributions, wrong PURLs and untracked seed copies fail closed. Another 222 exact Medium header findings are tied to a pinned official Canonical snapshot and header-only proof; raised severity or an available fix remains denied. The separate full integration setuptools dependency is updated from 84.0.0 to the official 84.1.0 fix, with its existing source contract aligned; it receives no VEX exception.
Validation: the frozen 25-file business-owner source still matches combined owner receipt 8c91eed17b62ba434c05e9c47b3d2bb2ccb3e3da03f5a8e01a9ab3c31864826d; previous 17 local Go cases are carried forward. Direct builder tests: 19 policy cases, 13 VEX cases and Bash syntax passed. Actual builder run 40943449946 passed and its raw/proof/effective bytes were independently compared. Initial security failures are retained (40941720622 / 40941823778: new header/pip findings; 40943441667: full setuptools source finding). Official Go 1.27.3 build/race/reproducibility/security/CodeQL must pass on final producer 1835f8d before merge. No tag/release/runtime acceptance is claimed.