CHANGELOG: record the two v0.235.0 live-test pushes and their reverts as a measurement, not a release

CHANGELOG.md

@@ -1,3 +1,26 @@
+## LIVE-TEST for controller v0.235.0 — two pushes, both reverted the same hour (2026-09-06) — NOT A RELEASE
+
+**No template is different after these four commits.** `dc7e548` moved bentopdf's healthcheck
+interval 30s → 45s (a NON-image change); `09b4ff5` moved its pin v2.8.6 → v2.8.5; `1798ce6` and
+`17cc784` reverted both. The tree is byte-identical to `8220f8d`.
+
+**Why real catalog pushes and not a hand-edited file on the box:** controller v0.235.0 changes what
+the CATALOG SYNCER does, so the only faithful test is a real change travelling the real 15-minute
+cycle — the same method the 2026-09-01 spike used.
+
+**What they measured, live on demo-hp:**
+
+- the non-image change **reached** the pinned app on the normal cycle (`[INFO] [sync] Updated
+  bentopdf/docker-compose.yml`, 08:01:51Z) with the image and the container untouched — *fixes flow*;
+- the image change **did not** (08:20:29Z): the live compose file still named v2.8.6 while the catalog
+  offered v2.8.5, and a `POST /api/stacks/bentopdf/restart` afterwards took **0.1 s**, did not recreate
+  the container, and **never pulled v2.8.5** — against the spike's measurement of **18.3 s with a
+  pull** for the identical sequence before the change.
+
+**Why bentopdf:** deployed on demo-hp only, file-based, with no database and no volume, so no data
+anywhere could be touched. Evidence:
+`felhom.eu/documentation/tests/VALIDATION-update-slice3-2026-09-06.md`.
+
 ## catalog_since on all 53 apps — how long has a newer pin been sitting here? (2026-09-02, update arc slice 2)
 
 **One new optional key in every `.felhom.yml`, no compose file changed, no image moved.**