REPORT + CONTEXT: R-101 + F-DIAG (v0.182.0), rendered dialog proven live

CONTEXT.md

@@ -7,7 +7,22 @@
 >
 > Ask Claude Code: "Please update CONTEXT.md with what we did today"
 
-Last updated: 2026-07-28 (v0.181.0 — R-100: the offsite last-SUCCESS anchor)
+Last updated: 2026-07-28 (v0.182.0 — R-101 + F-DIAG: the restore dialog names the last SUCCESSFUL copy)
+
+> **2026-07-28 — v0.182.0 (R-101 + F-DIAG).** `Tier2LastRun` is the ATTEMPT clock (written on failure)
+> and was rendered as „Legutóbbi másolat" in the **restore confirm dialog** — misinformation at a
+> decision point: the restore fills in MISSING files, so a customer with a failing Tier-2 restored and
+> silently got OLDER files. New `CrossDriveBackup.LastSuccess` + **`SuccessTracked`**; the marker is
+> load-bearing because **all 7 fleet rows were pre-anchor at deploy** — without it every customer sees
+> „Még nincs sikeres másolat" at once. Legacy rows migrate on first touch (`ok` adopts its time,
+> `error` seeds nothing). **PART 2 — the three `record*` helpers rebuilt the WHOLE struct with only 2
+> fields carried over; the naive fix would have had `recordTier2Failure` CLEAR the anchor.** Replaced
+> by `tier2Update` (copy-and-overlay = safe by construction). New `fmtTimeStr` → Budapest-local dates
+> in the dialog instead of raw UTC RFC3339. **F-DIAG:** 6 classes incl. an honest `unknown`, and the
+> notification no longer passes `err.Error()` through raw — **LESSON: my first sanitiser was regex-only
+> and leaked a bare hostname; its own test caught it. Redact KNOWN values, don't guess at shapes.**
+> Live on demo-hp: rendered dialog read in the failed, healthy AND legacy states. F-OPS documented at
+> `felhom.eu/documentation/runbooks/RUNBOOK-manual-guest-restore.md`.
 
 > **2026-07-28 — v0.181.0 (R-100).** `OffboxTarget.LastSuccess` + wire field `last_success`; the hub
 > (v0.80.0) anchors offsite staleness on it. **`LastRun` is written unconditionally on every run