Record green verification and branch protection

Merge the documentation-only release record after all three required checks passed.

Author: Manablaq

README.md

@@ -115,8 +115,7 @@ See
 - Production smoke checks: `/`, `/app`, `/verify`, health, typed index lookup,
   typed transaction lookup, security headers, and browser verification action:
   **passed**
-- GitHub Actions `Verification` for this release is recorded after the next
-  push; prior deployed-source run `35134050898`: **passed**
+- GitHub Actions `Verification` run `35140950751`: **passed**
 
 The complete production release record is in
 [`docs/PRODUCTION_RELEASE_2026-09-16.md`](./docs/PRODUCTION_RELEASE_2026-09-16.md).

docs/AGENT_TANK_SUBMISSION.md

@@ -31,6 +31,7 @@ uses the SDK's authoritative eligibility, charge, and appeal operations.
   `dpl_Cwh63QydtcGyVD9MeZ7jrSo3A1QE`
 - Served coordinator:
   `0xEE21cCFF8f3755487f774BFd5Da9Ff51D5688581`
+- GitHub Actions `Verification` run: `35140950751` — all jobs passed
 
 Production smoke checks and the exact served-bundle binding are recorded in
 [`PRODUCTION_RELEASE_2026-09-16.md`](./PRODUCTION_RELEASE_2026-09-16.md).

docs/PRODUCTION_RELEASE_2026-09-16.md

@@ -51,9 +51,8 @@ Read-only checks against `https://commit-protocol.vercel.app` passed:
   client-side error
 - deployed JavaScript bundle contains the certified coordinator anchor and the
   strict `EXTERNAL MESSAGE OBSERVATION` claim surface
-- GitHub Actions `Verification` run `35134050898` for the previous deployed
-  source: completed successfully across Python, Direct Runtime, and frontend
-  jobs; CI for this release is recorded after the next push
+- GitHub Actions `Verification` run `35140950751` for the repository release:
+  completed successfully across Python, Direct Runtime, and frontend jobs
 
 The verification API remains read-only. It does not reconstruct chain truth or
 claim that an external GEN transfer was delivered after native-value dispatch.

docs/THREAT_MODEL.md

@@ -45,5 +45,9 @@ success, or automatic reconciliation as part of semantic atomicity.
    already present.
 
 The repository's GitHub Actions `Verification` workflow is active. Run
-`35134050898` completed successfully for the deployed source commit
-`8726ce7924fd78281a117b92ce4733396501ebac`.
+`35140950751` completed successfully for the current repository release
+commit `abc5b1883b10eec022875becc8660a724fb8f671`.
+
+The `main` branch now requires the Frontend checks, Python checks, and Direct
+Runtime checks, with force-push and deletion disabled and conversation
+resolution required.