Skip to content

Re-seal the GNN bridge source binding at GNN 5.0.2 - #234

Merged
docxology merged 1 commit into
mainfrom
codex/gnn-502-bridge-repin-20261030
Oct 30, 2026
Merged

docxology merged 1 commit into
mainfrom
codex/gnn-502-bridge-repin-20261030

Conversation

@docxology

Copy link
Copy Markdown
Collaborator

Why

The GNN 5.0.2 release candidate bumps pyproject.toml and uv.lock. Both are
declared 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:

"source_binding": {"passed": false,
  "errors": ["gnn: owner content changed: pyproject.toml",
             "gnn: owner content changed: uv.lock"]},
"finite_freshness": {"passed": false, "status": "STALE"},
"continuous_freshness": {"passed": false, "status": "STALE"}

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 as
the final GNN commit.

What changed

bridge pin re-seals owner digests against GNN
3dc3fb45a65072a0ed4e823a6c3f9f024bdbbce9 — the published GNN revision
carrying 5.0.2 — and the emitted finite/continuous documents are refreshed.

field before after
gnn.commit 4582f99cec57… (5.0.1) 3dc3fb45a650…
gnn.owners.pyproject.toml f9cd40f6… 02188340…
gnn.owners.uv.lock 73ebb61b… 4c62f954…
fep_lean.commit 605315652e96… 4aff49c6a4a6…

Emitted-document diffs are limited to Signature custody 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

Gate Result
bridge pin --gnn-root … ok
bridge emit --model finite --refresh-digests ok
bridge emit --model continuous --refresh-digests ok
bridge emit … --check (both models) ok
bridge status ok
Q7 generate_probe.py --check exit 0, artifacts current
pytest tests/test_gnn_bridge_operations.py tests/test_custody_refresh.py specs/gnn-semantic-witness-v1/test_composition.py 302 passed
docs/pin_audit.py --check-latest OK, 305 files, no drift
docs/xref_audit.py OK
docs/check_orphan_compiles.py 46 modules warning-free
ruff check / git diff --check clean

Q7 requires no refresh: its --check passes against this pair, and current-source
regeneration correctly refuses an in-place --output-root.

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.
@docxology
docxology merged commit 169b5a6 into main Oct 30, 2026
22 checks passed
@docxology
docxology deleted the codex/gnn-502-bridge-repin-20261030 branch October 30, 2026 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant