docs: supervisor (03), node_* ruling (08, CONTEXT), per-tier page + tier skip (07), self-bind triggers + PBS-DR lifecycle (05), settings after install (02), park + No TLS Verify runbooks, volunteer prerequisites

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-15 10:42:53 +02:00
parent d8cd4d4412
commit 4c4e3b3a3f
9 changed files with 109 additions and 1 deletions
@@ -479,6 +479,20 @@ sentence, covers installed-but-no-resolvable-data-root. **R-356**; reasoning als

 ---

+### 6.4 The customer's page speaks per tier, and a tier without storage is skipped (2026-09-15)
+
+**What the page may claim** (controller v0.243.0 + agent v0.131.0, R-517). The whole-system tile used
+to show the agent's single latest record — so a failed 0-byte PBS attempt read „Naprakész" and ticked
+„Távoli rendszermentés — külön hardveren" (BIGNIGHT 2026-09-14). Now `GET /backup/status` returns per
+tier the newest **success**, the last **attempt** kept apart, and whether the tier's storage exists.
+The page shows each tier's newest success; a failed attempt under it as „sikertelen"; a tier whose
+storage does not exist as „nincs beállítva". „Naprakész" and the remote tick are computed from
+successes only. After an agent restart the success is read back from the tier's storage (size unknown).
+
+**What a run may do** (R-518, cheap half). A tier the agent reports `storage: absent` is dropped before
+anything is stopped, logged, and reported once as `backup_tier_skipped`; `unknown` is never skipped.
+**Still open:** quiescing per tier, so a slow second tier does not keep every app down.
+
 ## 7. The recovery chain (D3) — the reason this document exists

 **[DESIGN] 3-2-1 describes copies. It does not describe recovery.**