R-212 CLOSED: the three orphaned stores deleted after a corrected list (~1.45 GB)

The register said 'two set-aside stores, ~1.2 GB'. Measured before touching
anything: THREE set-aside stores totalling ~1.45 GB, and the thing that was
exactly 1.2 GB was demo-felhom's LIVE felhom-repo. Matching on the size would
have deleted a working repository. The operator was shown the corrected list
and confirmed 'delete all three'.

Deleted: demo-felhom orphaned-20260717 (1.4 G) + orphaned-20260718 (3.0 M);
demo-hp orphaned-20260804 (43 M). Both LIVE repos untouched, confirmed by full
listings before and after on each account.

Proof nothing live was caught: a real off-site run on demo-hp immediately
afterwards returned status ok, orphaned false, no error, 6 snapshots.

Method note recorded for the next session: the storage box has a RESTRICTED
shell. 'test -d X && rm -rf -- X' returns 'Command not found' and does nothing
(it failed CLOSED, verified by an unchanged listing); 'rm -r <path>' as one
simple command is the working form.

STATUS.md

@@ -47,6 +47,14 @@ over; and the file was restored **byte for byte identical**. *(R-201)*
 
 ## What shipped recently
 
+- **2026-08-05** — **The orphaned backups are deleted — and the list you were given was wrong, which
+  is why you were asked again.** You had approved "about 1.2 GB in two set-aside stores". Measured
+  before touching anything: there were **three** set-aside stores totalling **~1.45 GB** — and the
+  thing that was exactly 1.2 GB was demo-felhom's **live** store. Matching on the size would have
+  deleted a working backup. With the corrected list confirmed, all three were removed and both live
+  stores left alone; a real off-site backup ran successfully straight afterwards to prove nothing
+  working had been caught. *(R-212)*
+
 - **2026-08-05** — **A rebuilt machine now asks for its storage credential, and the hub gives it back.**
   The machine says plainly what it needs — it can tell it has been rebuilt, because its data area is
   empty *and* the hub is holding a sealed recovery package for it — instead of leaving the hub to guess
@@ -107,13 +115,7 @@ over; and the file was restored **byte for byte identical**. *(R-201)*
   (controller up to 0.135.0, hub up to 0.57.0; everything newer is safely in the registry). **Nothing
   was deleted.** Worth knowing before you spend time on it: they only account for about 27 GB against
   199 GB now free, so this is about clutter, not space. *(R-210)*
-- **The orphaned-backup deletion is STOPPED and needs your ruling — the list does not match.** You
-  asked for about 1.2 GB in two set-aside stores to be deleted. Measured today, read-only: demo-felhom
-  holds a **live** store of 1.2 GB plus set-aside stores of **1.4 GB** and **3 MB**; demo-hp holds a
-  live store of 582 KB plus a set-aside store of **43 MB**. So there are **three** set-aside stores
-  totalling ~1.45 GB, not two — **and the thing that is exactly 1.2 GB is demo-felhom's LIVE store**,
-  which must not be deleted. **Nothing was deleted.** Tell me which of the three `orphaned` stores to
-  remove. *(R-212)*
+- **Nothing.**
 - **The recovery screen you described has been priced, and it can be built.** A freshly installed
   machine that finds a sealed package waiting should say so, offer a box for the recovery code, and
   show what would come back before doing anything. One thing to weigh, deliberately not decided: that