Verify native release integrity on adoption tuple re-pins (partial R1)

[seathatflowsinourveins]

Scope

Extend the existing NAS release-due seam to compare the full (release_tag, release_commit) tuple and invoke the upstream GH verifier once on a re-pin. Keep ordinary reports, unchanged tuples and the local before-cut --strict check offline; add the native release check before the existing consumer asset check.

• Base commit: c148e049efee75f8ea8a9a009e7b96b1e97f5c28
• Lane: lane:foundation
• Owned paths: scripts/release_due.py, tests/test_release_pin_contents.py, adoption/update.md, the new dated decision and compact R1 receipt; evidence registry is the last commit.
• Explicitly partial campaign R1. Publisher Currency wave W1: eight foundation pins to their latest clean upstream releases (mcporter held) #642 and bootstrap Currency wave W1: eight foundation pins to their latest clean upstream releases (mcporter held) #642/PR-metadata gates in their own workflow, reading the current PR; suite counts in the validate summary (G-1, G-6) #706 remain with their owners. The existing validation workflow owner (PR-metadata gates in their own workflow, reading the current PR; suite counts in the validate summary (G-1, G-6) #706/Upstream quality audit of the definitive manifest's foundation repositories #596/Final catalog of 2026-10-01: the blind GPT-6.1 Sol half of the clean-install selection and its comparison with the Claude record #595) must supply native GH authentication to its release-due step before a real future re-pin can pass (Q15). This draft makes no workflow edit.

SOTA sources

• cli/cli@v2.102.0:pkg/cmd/release/verify/verify.go:172–187: native cryptographic verification and successful-result exporter. Installed GH 2.102.0 help and official source GET independently confirmed the command; Git blob c1a9ae4a20a019133f1bac6ef4d5039eda00e5cc.
• Native GH release verification and GitHub release-integrity documentation: supported verifier and consumer instructions.
• GitHub CLI in workflows: token environment required in the invoking step. Existing source at base validate.yml:109–113 sets only BASE_REF; token in the zizmor step is confined to that step.
• NAS@c148e049:scripts/release_due.py:136,260–294: reuse existing pin/report seams. docs/lanes.md:94 and acceptance policy: registry-last and evidence separation.

Evidence-class table

Claim	Evidence class	Command / receipt
GH verified the existing v2026.10.05.1 release	native_proven	Unchanged gh release verify ... --format json, exit0; actual attestation/verification output retained and hashed in evidence/artifacts/github-ci-r1-20261005.json. Scope is that release and native command only.
Full-tuple comparison, one-call and offline controls	local_integration / synthetic	30 release-pin tests pass; real local Git/report paths, mocked GH success/failure/malformed results.
Adoption instructions remain consistent	local_integration	21 focused adoption-doc checks pass.
Hashes and declared scope are consistent	local_integration	scripts/validate.py passes; this is integrity evidence only.
Four implementation paths are unowned	source_review	Fresh 41-PR snapshot; 15 explicit native GETs exit0, 27 identical-head findings reused; no intersections.
Bounded native SDK unit completed	source_review	Native report finished, 10 model requests; tests executed independently by root.
New gate has hosted acceptance	unknown	No actual hosted re-pin, publisher or bootstrap acceptance is claimed.

Local commands run

gh release verify v2026.10.05.1 --repo seathatflowsinourveins/native-agent-stack --format json
exit 0; retained native attestation and verificationResult
python3 -m unittest discover -s tests -p test_release_pin_contents.py
exit 0; 30 tests after shape-repair controls
PYTHONPATH=tests python3 -m unittest test_adoption_docs_consistency.ReleasePinQuotesTests test_adoption_docs_consistency.RelativeLinkTests test_adoption_docs_consistency.ExclusiveFlagTests test_adoption_docs_consistency.ScriptPathTests test_adoption_docs_consistency.UnreleasedStepMarkerTests
exit 0; 21 tests
python3 scripts/component_matrix.py --write
exit 0; 32 rows, 0 flip violations
python3 scripts/new_host_grand_list.py --write
exit 0; generated outputs unchanged
python3 scripts/validate.py
exit 0; 69 components, 10145 hashed files, 4 profiles, 203 receipts
git diff --check
exit 0
git rebase origin/main
exit 0; current after clean commits, registry last

An independent completeness critic caught unsupported nonempty-object verification results. The gate now requires the two native nonempty object fields, permits extra fields, and delegates all cryptography to GH. The receipt retains that correction, the stopped owner-conflicted first unit and two failed command attempts with their corrections; they are not promoted to acceptance.

Decision record

docs/decisions/2026-10-05-ci-release-repin-verification.md names alternatives, source evidence, owner prerequisites, October12 review and concrete overturn conditions. Receipt: evidence/artifacts/github-ci-r1-20261005.json.

Host evidence

No host receipt or platform-status change.

Checklist

• New/changed actions and workflow permissions: not applicable; no workflow edit.
• No secrets printed, logged or committed; existing native sign-ins were used without inspecting values or credential files.
• No new paid hosting, subscription or billing surface.
• Peer-owned paths and worktrees preserved.
• Registry committed last.
• Existing workflow owner wires native GH authentication and one real re-pin establishes hosted integration acceptance.
• Held publisher/bootstrap R1 work completes.
• Command-center Claude cross-family read. Keep draft until that read; command center lands.

[seathatflowsinourveins]

Closed with a record by the PR triage of 2026-10-07 (the command center's ruling, item review-ns2604-coop-20261007T023012Z (the command center's PR-triage ruling of 2026-10-07; proposal by github-ci-finalize, triage-20261007.json)). Not merged; the branch codex/ns2604-ci-r1-20261005 stays on origin at 08c85e1.

What it holds: docs/decisions/2026-10-05-ci-release-repin-verification.md; evidence/artifacts/github-ci-r1-20261005.json; scripts/release_due.py, tests/test_release_pin_contents.py and adoption/update.md (modified)

Superseded by: not superseded; unprioritized under the 2026-10-07 PR triage (confidence: high that nothing supersedes it: main's scripts/release_due.py is byte-identical to the PR's base c148e04, so the tag-only re-pin gap it fixes is still on main)

Reopen trigger: A release-tuple re-pin changes only the tag, or the adoption release gate must call the native gh release verify. Reopen with gh pr reopen 739.