Repository navigation
Re-pin GNN bridge custody after the urllib3 security fix - #78
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
1 participant
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 GNN 4.0.0 urllib3 security update changes two bridge owner files, so the retained source pin would fail drift checks. This successor re-pins published GNN source/artifact commit
dbba3d0b9f5d9cb36052b604f27e28b79aa8ead7and regenerates only the finite/continuous provenance signatures.All 191 FEP owner hashes and 746 other GNN owner hashes remain identical. Model bodies and numerical semantics are unchanged. Explicit bridge status and both read-only emit checks pass, along with 61 bridge operation cases. Historical Q5/Q6/Q7 native and execution receipts retain their original epochs; source custody does not promote them.
Exact head
0bb565bd29e0f6e3994f8d481994c3918817b2c8now has all 20 required jobs successful, documentation explicitly skipped and all 15 OS/Python distribution cells successful. The successful Python retry reports 2,637 passed / 20 skipped and 91.45% coverage against the 89% floor. The run history preserves attempt 1's single Chrome CDP startup failure (2,636 passed / one failed / 20 skipped; 91.48% coverage). Only that Python job was rerun at unchanged source; no test, timeout or threshold was bypassed. Its cause remains unproved.Native/render artifacts are retained from successful attempt 1, explicitly distinct from Python attempt 2: 557 serial Lean cases passed / five skipped; all 168 native topics validate with zero warnings or
sorry; the formal audit resolves all 1,596 declarations. Independent packet review verifies the 356-page PDF, all 11 artifact members, 1,424 tracked source inputs plus six generated inputs, the pinned template tree, appendix, fonts, figures, finite PDF views and public context. Both render receipts exactly equal committed bytes, so no promotion commit is required. CI-generated variables/cache raw bytes retain the documented downstream reconstruction limit; their source hashes and fail-closed CI bookends are retained.Normal companion merge precedes the final GNN companion-main pin and renewed GNN checks. This PR does not publish a FEP or GNN software release.