diff --git a/README.md b/README.md
index fdb61b1..a0947c9 100644
--- a/README.md
+++ b/README.md
@@ -19,9 +19,10 @@ and the archive checksums in [.almide-checksums.sha256](.almide-checksums.sha256
 Results checked on **2026-10-04**. Most rows below were first established with a
 source build of the earlier pin, commit
 [`852b028`](https://github.com/almide/almide/commit/852b028a5706801fd008a753bcbdf8b3ea93156f)
-(`0.66.0 (dev)`); after the switch, every local suite, Docker/Compose on macOS arm64
-and on the ConoHa VPS, and GitHub Actions were rerun with the release binary.
-Cloudflare and Google deployments have not been repeated with it.
+(`0.66.0 (dev)`); after the switch, every route in the table that was run before
+(local suites, Docker/Compose on macOS arm64 and on the ConoHa VPS, Cloudflare
+Workers, Google Cloud Run container and functions, GitHub Actions) was rerun with
+the release binary and gave the same results.
 See [verification notes](docs/verification.md#compiler-pin-moved-to-the-v0660-release).
 
 | Route | Build / bundle | Shared API contract | Live cloud |
diff --git a/docs/verification.md b/docs/verification.md
index cd410c3..9b38a98 100644
--- a/docs/verification.md
+++ b/docs/verification.md
@@ -214,8 +214,26 @@ commits apart), so it is a different compiler and was re-verified:
 6. ConoHa VPS x86_64 (below): 91 s including base-image pulls, 24 s with
    `--no-cache`; 18 cases passed
 
-The earlier Cloudflare and Google deployments used the source-built compiler and
-were not repeated with the release binary. License texts are identical at both pins.
+License texts are identical at both pins.
+
+### Cloudflare and Google rerun with the release binary
+
+Same day, from main at `916f22c`, using the same procedure as the earlier
+[Cloudflare](#cloudflare-workers-edge-deployment) and
+[Google](#google-cloud-deployments) sections (a new disposable Google project,
+deleted afterwards):
+
+1. Cloudflare Workers: upload 28.90 KiB (gzip 11.47 KiB), startup 18 ms. Two
+   requests got the 1042 propagation 404, then 18/18 passed from the KIX colo; no
+   500 this time. `wrangler delete` removed it
+2. linux/amd64 image under QEMU on Apple silicon: 91 s
+3. Cloud Run container from the digest-pinned image: 18/18 from the in-VPC VM
+   with an ID token; 403 without a token; 404 from the internet with a token
+4. Cloud Run functions via `deploy.sh --execute`: 18/18 as
+   `application/octet-stream`; as JSON the same 3 framework rejections; 403 / 404
+   negatives as before
+5. Waiting about 90 seconds after granting `roles/run.invoker` avoided the
+   propagation failures seen in the first run
 
 ## ConoHa VPS
 
@@ -247,7 +265,6 @@ locally and used through `dev_overrides`), region c3j1.
 - Native x86_64 Docker build outside the ConoHa VPS
 - ConoHa TLS/reverse proxy, restart behavior, production load, or plans smaller
   than `g2l-t-c4m4`
-- Cloudflare and Google deployments with the release compiler
 - Azure Container Apps or ECS Fargate provider validation/deployment
 - Lambda managed runtime or Azure Functions host execution/authentication
 - Google Cloud costs, load, cold-start latency or long-running behavior