controller v0.296.0: a backup run cut off by a power cut or restart is said on the backup pages (R-519); the whole-system backup text states today's measurement (R-518)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-05 12:14:54 +02:00
parent 477e2548db
commit ff69074514
21 changed files with 2700 additions and 21 deletions
@@ -1128,6 +1128,13 @@ was off at the backup time (from the metrics record, one sample a minute), and s
 on — it never changes the time itself. Closing it lasts until the next missed backup time; a successful night removes
 it. Design: `felhom.eu/documentation/architecture/07-backup-architecture.md` §6.1.1.

+**A backup run cut off by a power cut or a restart is said (v0.296.0, R-519).** `internal/backup/run_record.go`. The
+app-data run is on record (`<data>/appdata-run.json`) while it runs; a start that finds it still "running" turns it
+into a notice on /backups and /backups/apps („A legutóbbi mentés (…) megszakadt…"), kept until a run ends with every
+step OK. After a restart the page's "last database backup" (synthesised from the files) no longer reads OK over a cut
+run. Each restore point already carries the time of its OLDEST part (the data block, v0.275.0). The whole-system
+"Mentés most" text states two measurements: ≈6 min on a 9-app box (demo-hp, 2026-10-05), ≈8 min on a 12-app box.
+
 **The restore carries the customer's own previous answers (v0.217.0, R-351).**
 `internal/backup/offbox_placement.go`. Every recovery unit's `manifest.json` records `drive` and
 `namespace_root`, and its `compose/app.yaml` records `SUBDOMAIN`/`DOMAIN`. Until v0.217.0 nothing read