REPORT: record the 0.226.1 patch and which version the live evidence describes

The section 6 live validation ran against 0.226.0, which was already on the box
when the fallback defect was found. Saying so rather than re-attributing the
evidence to 0.226.1: they differ only by CountsUnknown and its two tests, and
neither touches any path that validation exercised.

REPORT.md

@@ -1,6 +1,6 @@
 # REPORT — R-353 / R-357 / R-358 / R-360: the restore tells the truth
 
-**Controller v0.226.0 · 2026-08-30 · implemented on DooPlex, validated live on `demo-hp`**
+**Controller v0.226.0 → v0.226.1 · 2026-08-30 · implemented on DooPlex, validated live on `demo-hp`**
 
 ---
 
@@ -112,9 +112,16 @@ unmodified. The only test-file edits were mechanical call-site updates for the c
 
 ```
 $ ssh hp "pct exec 9201 -- docker ps --filter name=felhom-controller --format '{{.Image}} {{.Status}}'"
-gitea.dooplex.hu/admin/felhom-controller:0.226.0 Up 13 seconds (healthy)
+gitea.dooplex.hu/admin/felhom-controller:0.226.1 Up 13 seconds (healthy)
 ```
 
+**A patch, not a rebuilt 0.226.0.** The live validation in §6 ran against **0.226.0**, which was
+already on the box when §11 item 4's defect was found. Re-pushing a changed image under a tag already
+running somewhere is the `:latest` hazard with extra steps — two images, one name, no way for a box to
+tell which it has — so the fix shipped as **0.226.1** and the box was redeployed. **The §6 evidence
+therefore describes 0.226.0**, and that is stated rather than quietly re-attributed; 0.226.1 differs
+from it only by `CountsUnknown` and its two tests, neither of which touches any path §6 exercised.
+
 **`demo-hp` only.** `demo-felhom` stays on 0.225.0 and the rest of the fleet on 0.223.0 (the floor).
 
 ## 6. Live validation — endpoint level, on `demo-hp`