Repository navigation
Re-seal the GNN bridge source binding at GNN 5.0.2 - #234
Merged
Merged
Conversation
The GNN 5.0.2 release candidate bumps two declared contract owner files (pyproject.toml, uv.lock). That is exactly the re-drift the paired-revision policy predicts, so the FEP-side binding closes it before the GNN companion pin lands: `bridge pin` re-seals owner digests against GNN 3dc3fb45a65072a0ed4e823a6c3f9f024bdbbce9 — the published GNN revision that carries 5.0.2 — and the emitted finite/continuous documents are refreshed. Only Signature custody fields change: source_commit, pipeline_commit and pipeline_owners_sha256. No GNN roster, contract mirror, syntax surface or formal projection is affected; the GNN owner roster stays at six files.
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.
Why
The GNN 5.0.2 release candidate bumps
pyproject.tomlanduv.lock. Both aredeclared contract owner files for the GNN bridge's source binding, so the
version bump re-drifts the custody pair — exactly the condition the
paired-revision policy predicts.
Demonstrated on merged main before this change:
This follows the documented closeout order: the FEP-side bridge re-pin lands
first, and GNN's companion pin bump (
.github/fep-lean-pair.json) follows asthe final GNN commit.
What changed
bridge pinre-seals owner digests against GNN3dc3fb45a65072a0ed4e823a6c3f9f024bdbbce9— the published GNN revisioncarrying 5.0.2 — and the emitted finite/continuous documents are refreshed.
gnn.commit4582f99cec57…(5.0.1)3dc3fb45a650…gnn.owners.pyproject.tomlf9cd40f6…02188340…gnn.owners.uv.lock73ebb61b…4c62f954…fep_lean.commit605315652e96…4aff49c6a4a6…Emitted-document diffs are limited to
Signaturecustody fields:source_commit,pipeline_commit,pipeline_owners_sha256.Scope discipline
This is a custody re-seal, not a semantics change. The GNN owner roster stays at
six files. No GNN roster, contract mirror, syntax surface or formal
projection is modified — the checks below report the first three passing and an
empty projection drift list. Existing receipts are not promoted.
Verification
bridge pin --gnn-root …bridge emit --model finite --refresh-digestsbridge emit --model continuous --refresh-digestsbridge emit … --check(both models)bridge statusgenerate_probe.py --checkpytest tests/test_gnn_bridge_operations.py tests/test_custody_refresh.py specs/gnn-semantic-witness-v1/test_composition.pydocs/pin_audit.py --check-latestdocs/xref_audit.pydocs/check_orphan_compiles.pyruff check/git diff --checkQ7 requires no refresh: its
--checkpasses against this pair, and current-sourceregeneration correctly refuses an in-place
--output-root.