v0.263.2: the undo keeps the probe of the pinned version (R-637)

Found live on 9202 (romm): .felhom.yml flows into the stack dir on every
catalog sync, so "the old .felhom.yml" saved at update time was already the
new one, and the serving old version was judged with the new probe.

New record applied-meta/.felhom.yml, written whenever a version is pinned
(deploy, adoption, pin advance) and put back by the undo, like
applied-compose.yml. The fixture now places the new file at sync time.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

controller/README.md

@@ -640,7 +640,7 @@ finished-marker last. **Bind-mounted folders (photos, documents, the drive) are
 touched.** On failure: every copy is validated (marker present) before anything is put back; the
 volumes are emptied and refilled from the copies; the previous compose, applied definition and pin
 come from the job's own pre-update copies (never the recovery unit); the old version is checked with
-the OLD `.felhom.yml` probe (kept in `pre-update-meta/`). Success → phase `undone`, the copies go, and
+the OLD `.felhom.yml` probe — the pinned version's own file, recorded in `applied-meta/` whenever a version is pinned (deploy, adoption, update) because `.felhom.yml` flows in on every catalog sync (v0.263.2), and copied to `pre-update-meta/` for the undo. Success → phase `undone`, the copies go, and
 `app.yaml` records `last_update_undone: {to, at, why}` — the page shows one line under the badge until
 the next successful update. Failure → the hold, whose sentence now opens with *„A frissítés nem
 sikerült, és az automatikus visszaállítás sem."* and what state the data is in (`untouched`, `half`,