REPORT: Scenario F measured on real CI (runs 69 vs 70, same commit)

REPORT.md

@@ -71,6 +71,25 @@ never released at all. Nothing here can see that; it belongs at vouch time in th
   agent gates OK"**. Restored → **rc=1, CONVICTED: published**. The guard is what catches it, not
   something else.
 
+### Scenario F measured on REAL CI, not inferred
+
+Runs **69** and **70** are on the **same commit** `0db7766`:
+
+| run | state of the repo | CI |
+|---|---|---|
+| 69 | no `v9.9.9` | **success** |
+| 70 | `v9.9.9` tagged, not published | **failure** |
+
+Same code, same workflow, one variable — so the gate demonstrably RUNS in CI and fails for exactly
+the R-115 condition. This also retrospectively explains runs 67/68, which were red in the window when
+`v9.9.9` first existed. **One deliberate CI failure e-mail reached the operator — that was this
+proof, not an incident.**
+
+I could not read CI's own step log to attribute those runs directly: the Gitea jobs endpoint requires
+an API token, and the only credential available on this host (`~/.docker/config.json`) is a registry
+password, which the API rejects. The controlled before/after above replaced that log rather than an
+assumption standing in for it.
+
 `v9.9.9` was deleted afterwards; `git ls-remote --tags` shows only `v0.120.0`.
 
 ## Tag convention