From b03ac9c2a6fd6914a1e3386741abc85f52f9f607 Mon Sep 17 00:00:00 2001
From: Codex <codex@localhost>
Date: Tue, 13 Oct 2026 22:09:32 +0300
Subject: [PATCH] Clarify update replay state after full base restoration

---
 docs/system-recovery.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/system-recovery.md b/docs/system-recovery.md
index f535064..b8003c3 100644
--- a/docs/system-recovery.md
+++ b/docs/system-recovery.md
@@ -12,6 +12,12 @@ subvolumes beneath `@root` are refused. Boot and fstab must select the filesyste
 UUID plus `subvol=@root`, never a numeric root subvolume ID. `@home` and VM disks
 stored there survive restoration; files stored elsewhere in `@root` roll back.
 
+This includes `/var/lib/hydra-update`: a full root restoration also restores the
+checkpoint's runtime update receipts and replay floor. The signed updater's
+monotonic sequence guarantee applies to runtime apply/recovery/rollback, not to
+replacing the entire root with an older checkpoint. Check the available signed
+release again after base recovery.
+
 Record the Btrfs filesystem UUID and ESP PARTUUID at installation. From the live
 ISO, inspect the plan before executing it: