v0.245.0 — R-543: the household is asked for the recovery code, the page says "szunetel" until then

Off-site backup is ON by default and does not RUN until the household creates its
recovery code. The pause is the zero-knowledge escrow design and is untouched here;
what was missing is that nothing ASKED, while the app-backup page promised the very
copy that had never run.

- a reminder bar on every authenticated page while the off-site tier is configured
  and its escrow is not complete, linking /backup/escrow. It is the R-241 bar, second
  instance: same session-cookie dismissal, back next visit, gone for good when
  escrowed. No second banner system. It hangs off executeTemplate, the single render
  choke point, so it cannot reach only the pages someone remembered.
- the tier-1 file sentence renders by tier3State's own vocabulary instead of the
  app's shape: active -> "vedi", escrow_pending -> "vedene ... szunetel" + the route,
  no copy at all -> says so and names both ways out.
- both fixes red-proofed: the bar test fails on BOTH pages with the hook removed; the
  sentence test quotes the exact v0.244.0 promise when the state is ignored.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

controller/internal/web/backup_page_state.go

@@ -47,3 +47,36 @@ func tier3State(configured, toggled bool, escrowState string) string {
 		return "active"
 	}
 }
+
+// driveFilesNoteFor is the one sentence under a class-A app's Tier-1 row: where the household's own
+// FILES are protected, said in the state the box is actually in.
+//
+// R-543. v0.244.0 shipped this sentence in one form — „a távoli másolat … védi" — and it was true of
+// the design and false of a fresh box: off-site is ON by default (hub v0.116.0) but PAUSED until the
+// household performs the escrow ceremony, which nothing asked them to do. A sentence that promises a
+// copy which is not running is the same class of lie R-537 and R-538 were filed for, committed by the
+// fix for them.
+//
+// It is pure, and it takes tier3State's OWN vocabulary rather than re-deriving the state, so the row
+// and the sentence can never disagree:
+//   "active"          → the copy exists and runs        → „védi"
+//   "escrow_pending"  → enabled, paused for the code    → „védené … szünetel" + the route to fix it
+//   "off"/"unconfig"  → no off-site at all              → say so, and name both ways out
+// The link is returned separately so the template renders a real anchor and the copy gate sees plain
+// text; empty note means render nothing (an app whose data is in its volumes needs no sentence).
+func driveFilesNoteFor(hasDriveFileLegs bool, tier3State string, tier2Configured bool) (note, linkHref, linkText string) {
+	if !hasDriveFileLegs {
+		return "", "", ""
+	}
+	switch tier3State {
+	case "active":
+		return "Az alkalmazás fájljait a távoli másolat (és a második meghajtó) védi — ez a helyi mentés a beállításokat és az adatbázist tartalmazza.", "", ""
+	case "escrow_pending":
+		return "Az alkalmazás fájljait a távoli másolat védené — a távoli mentés a helyreállítási kód létrehozásáig szünetel.", "/backup/escrow", "Helyreállítási kód létrehozása"
+	default:
+		if tier2Configured {
+			return "Az alkalmazás fájljait a második meghajtóra készülő másolat védi — ez a helyi mentés a beállításokat és az adatbázist tartalmazza.", "", ""
+		}
+		return "Az alkalmazás fájljairól jelenleg nincs másolat — kapcsold be a távoli mentést vagy adj hozzá második meghajtót.", "/backups/remote", "Távoli mentés beállítása"
+	}
+}