Refresh release certification metadata (#4)

Author: Manablaq

README.md

@@ -106,16 +106,16 @@ See
 
 - Public application: `https://commit-protocol.vercel.app`
 - Deployed application source commit:
-  `53fb52f2d8d7c5a3636810501b740d859d5a2c14`
+  `77442659b06f1ddaa7ec1215fae9048671ac0c76`
 - Deployed application source tree:
-  `91c5f458dd77f7d38f0c8107f00eb15a74c3ce37`
+  `a52c55fdded8ba096c5f7527aad894943d458809`
 - Vercel production deployment:
-  `dpl_BvXSZgubPSzs3Z9cyck6eY5dzvDt`
+  `dpl_ChVMybCDSWombsWhsikRJPLtagN5`
 - Served coordinator: `0xEE21cCFF8f3755487f774BFd5Da9Ff51D5688581`
 - Production smoke checks: `/`, `/app`, `/verify`, health, typed index lookup,
   typed transaction lookup, security headers, and browser verification action:
   **passed**
-- GitHub Actions `Verification` run `35142284628`: **passed**
+- GitHub Actions `Verification` run `35146518481`: **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

@@ -24,14 +24,14 @@ uses the SDK's authoritative eligibility, charge, and appeal operations.
 - Public app: `https://commit-protocol.vercel.app`
 - GitHub: `https://github.com/Manablaq/commit-protocol`
 - Production source commit:
-  `53fb52f2d8d7c5a3636810501b740d859d5a2c14`
+  `77442659b06f1ddaa7ec1215fae9048671ac0c76`
 - Production source tree:
-  `91c5f458dd77f7d38f0c8107f00eb15a74c3ce37`
+  `a52c55fdded8ba096c5f7527aad894943d458809`
 - Vercel production deployment:
-  `dpl_BvXSZgubPSzs3Z9cyck6eY5dzvDt`
+  `dpl_ChVMybCDSWombsWhsikRJPLtagN5`
 - Served coordinator:
   `0xEE21cCFF8f3755487f774BFd5Da9Ff51D5688581`
-- GitHub Actions `Verification` run: `35142284628` — all jobs passed
+- GitHub Actions `Verification` run: `35146518481` — 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/ENVIRONMENT.md

@@ -78,10 +78,9 @@ application release. It is not the current source-bound coordinator.
 
 Contract source-binding release commit: `6fe34484acb4bb21afd8f438ecac00e7780042e1`
 
-The current `main` branch is `d2e46de82b9c269d59ed77d97c1844dc9943b7b3` at
-this audit base. It contains later frontend, documentation, and verification
-commits; the source-binding commit above identifies the exact contract code
-revision used for the certified deployment.
+The current application release was verified from `main` commit
+`77442659b06f1ddaa7ec1215fae9048671ac0c76`; the source-binding commit above
+identifies the exact contract code revision used for the certified deployment.
 
 Base GitHub main before publication:
 

docs/PRODUCTION_RELEASE_2026-09-16.md

@@ -6,11 +6,11 @@ canonical Vercel alias and the exact Studio Next coordinator it targets.
 ## Release identity
 
 - Repository: `https://github.com/Manablaq/commit-protocol`
-- Deployed application source commit: `53fb52f2d8d7c5a3636810501b740d859d5a2c14`
-- Deployed application source tree: `91c5f458dd77f7d38f0c8107f00eb15a74c3ce37`
+- Deployed application source commit: `77442659b06f1ddaa7ec1215fae9048671ac0c76`
+- Deployed application source tree: `a52c55fdded8ba096c5f7527aad894943d458809`
 - Public application: `https://commit-protocol.vercel.app`
 - Vercel project: `mr-albert-s-projects/commitprotocol-genlayer`
-- Vercel production deployment: `dpl_BvXSZgubPSzs3Z9cyck6eY5dzvDt`
+- Vercel production deployment: `dpl_ChVMybCDSWombsWhsikRJPLtagN5`
 - Deployment state: `READY` / `PRODUCTION`
 
 The source commit and tree above are the exact release built and published by
@@ -52,7 +52,7 @@ 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 `35142284628` for the application release:
+- GitHub Actions `Verification` run `35146518481` for the application release:
   completed successfully across Python, Direct Runtime, and frontend jobs
 
 The verification API remains read-only. It does not reconstruct chain truth or

docs/THREAT_MODEL.md

@@ -45,8 +45,8 @@ success, or automatic reconciliation as part of semantic atomicity.
    already present.
 
 The repository's GitHub Actions `Verification` workflow is active. Run
-`35142771890` completed successfully for `main` commit
-`d2e46de82b9c269d59ed77d97c1844dc9943b7b3`.
+`35146518481` completed successfully for `main` commit
+`77442659b06f1ddaa7ec1215fae9048671ac0c76`.
 
 The `main` branch now requires the Frontend checks, Python checks, and Direct
 Runtime checks, with force-push and deletion disabled and conversation