CHANGELOG + CONTEXT: v0.336.0 release line (the previous commit carried only REPORT)

CHANGELOG.md

@@ -3,6 +3,12 @@
 **MinAgent: 0.158.1** — the floor's, carried; no agent change. No golden (`09` §3 decision 250). Task: the night brief
 part 2 of 2026-10-20, Part 2 (operator answer: „D20 A").
 
+**Released 2026-10-20:** rc.1 on 9202 first (the forced-failure and normal-restore proof, felhom.eu
+`audits/night2-2026-10-20/P2/live/`); image `sha256:93cd67d8…8d73` from a clean clone at `93fb251`; per-box floors
+08:51 UTC → all three test boxes on 0.336.0 by 08:51:26 → box walk green (0 unhealthy, 0 refusals, https-only 28 OK,
+„Fájlok ↗" one sign-in on demo-hp and Tester 1) → **global floor 0.336.0 / MinAgent 0.158.1 at 08:54:35 UTC**, read
+back; per-box floors cleared. i18n: no page template changed; the new keys are Go-side messages (no fixture changed).
+
 - **R-893 option A — the off-site restore of one app keeps a copy of the app's live volumes and puts it back on
   failure** (`internal/backup/offbox_restore_undo.go`, `07` §6.3). Before anything stops, every volume the snapshot will
   replace is measured (`du` on the named volume) and the copy is added to the restore's own free-space need (R-357's

CONTEXT.md

@@ -1,5 +1,10 @@
 # CONTEXT.md — Project Memory
 
+> **2026-10-20 — v0.336.0 is the floor (MinAgent 0.158.1, 08:54 UTC).** R-893 option A (operator D20): a failed off-site restore
+> copies the app's live volumes first and puts them back exactly, then starts the app (proven on 9202: schema, data and row-count
+> md5 equal before and after a forced failure); R-1169 the held sentence. Follow-up row: the put-back's ERROR log level and an
+> empty `backups/restore-undo/` folder.
+
 
 > **2026-10-19 (day) — v0.332.0 is the floor (MinAgent 0.158.1): one sign-in for the file manager (R-1100, D16) and the
 > typed-back escrow confirm (R-1151).** Every dashboard folder link → `fileBrowserOpenLink` → `GET /__files/open` (pass: