Refresh current release evidence

Author: Manablaq

README.md

@@ -99,19 +99,20 @@ newer release commit.
 See
 [`docs/DEPLOYMENT_LOG_STUDIO_DEV.md`](./docs/DEPLOYMENT_LOG_STUDIO_DEV.md).
 
-### Published application release
+### Current published application release
 
 - Public application: `https://commit-protocol.vercel.app`
 - Deployed application source commit:
-  `f63c0cb19993b0ae79fffb34908fe3571bdfb768`
+  `8726ce7924fd78281a117b92ce4733396501ebac`
 - Deployed application source tree:
-  `31af728d04d39608bfd2c21932a1d201cdae2c73`
+  `997644a9cb62c2ac03296e16106ed3facc243888`
 - Vercel production deployment:
-  `dpl_9KCsNE68QaDZrYLcE9M2FGbH5vzn`
+  `dpl_DWRmgLJVvz8hvQVcxyC25ntmvkfq`
 - 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 `35134050898`: **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,11 +24,11 @@ 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:
-  `f63c0cb19993b0ae79fffb34908fe3571bdfb768`
+  `8726ce7924fd78281a117b92ce4733396501ebac`
 - Production source tree:
-  `31af728d04d39608bfd2c21932a1d201cdae2c73`
+  `997644a9cb62c2ac03296e16106ed3facc243888`
 - Vercel production deployment:
-  `dpl_9KCsNE68QaDZrYLcE9M2FGbH5vzn`
+  `dpl_DWRmgLJVvz8hvQVcxyC25ntmvkfq`
 - Served coordinator:
   `0xEE21cCFF8f3755487f774BFd5Da9Ff51D5688581`
 
@@ -128,9 +128,9 @@ executions of the newer release commit.
 Full historical record:
 [`DEPLOYMENT_LOG_STUDIO_DEV.md`](./DEPLOYMENT_LOG_STUDIO_DEV.md).
 
-## Published-release verification snapshot
+## Historical published-release verification snapshot
 
-The currently published release has the following certification record:
+The earlier published release has the following historical certification record:
 
 - coordinator source SHA-256:
   `be0ef1686314354ac1b87ccd50ab42f0c933c312a4980c0e5479f2d3037e4e58`;

docs/PRODUCTION_RELEASE_2026-09-16.md

@@ -6,16 +6,16 @@ canonical Vercel alias and the exact Studio Next coordinator it targets.
 ## Release identity
 
 - Repository: `https://github.com/Manablaq/commit-protocol`
-- Deployed application source commit: `f63c0cb19993b0ae79fffb34908fe3571bdfb768`
-- Deployed application source tree: `31af728d04d39608bfd2c21932a1d201cdae2c73`
+- Deployed application source commit: `8726ce7924fd78281a117b92ce4733396501ebac`
+- Deployed application source tree: `997644a9cb62c2ac03296e16106ed3facc243888`
 - Public application: `https://commit-protocol.vercel.app`
 - Vercel project: `mr-albert-s-projects/commitprotocol-genlayer`
-- Vercel production deployment: `dpl_9KCsNE68QaDZrYLcE9M2FGbH5vzn`
+- Vercel production deployment: `dpl_DWRmgLJVvz8hvQVcxyC25ntmvkfq`
 - Deployment state: `READY` / `PRODUCTION`
 
-The later documentation-only commits on `main` do not change the deployed
-application source. The source commit above is the exact release built and
-published by the recorded Vercel deployment.
+The source commit and tree above are the exact release built and published by
+the recorded Vercel deployment. The deployment includes the narrow-viewport
+overflow fix certified by the browser E2E gate.
 
 ## Served contract binding
 
@@ -49,8 +49,8 @@ Read-only checks against `https://commit-protocol.vercel.app` passed:
 - browser rendering of `/app` and `/verify`: passed with no console errors
 - verification-center “Read index” action: passed without a page reload or
   client-side error
-- GitHub Actions `Verification` run `35110066086` for the release documentation:
-  completed successfully
+- GitHub Actions `Verification` run `35134050898` for the deployed source:
+  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

@@ -43,5 +43,5 @@ success, or automatic reconciliation as part of semantic atomicity.
    already present.
 
 The repository's GitHub Actions `Verification` workflow is active. Run
-`35110066086` completed successfully for documentation release commit
-`a86f4effc219b06378e586beefb88c2d689d9eb4`.
+`35134050898` completed successfully for the deployed source commit
+`8726ce7924fd78281a117b92ce4733396501ebac`.