R-203 shipped: the app and its backup agree, and 'ok' means it — R-201 unblocked

STATUS.md

@@ -46,16 +46,15 @@ Proven end to end on real hardware.
   recovered key back*, reopens the old backup store with it, or **restores a single file**. Today
   proves the key survives and returns; it does not prove the backups do. *(R-199 closed; R-200 half;
   R-201 open)*
-- **A backup reported success while leaving out a folder the customer was told is protected.** Found
-  this evening on the HP machine, while setting up the wipe-and-restore proof. We deployed an app whose
-  book folder is declared *mandatory* — the strongest protection class — put a marked file in it, and
-  ran an off-site backup. **The backup said OK. Three snapshots. The folder was not in any of them.**
-  The machine knew: one warning line inside the container says the folder was skipped. Nothing else
-  does — not the card, not the counters, not the hub, not you. This is the same shape as everything
-  else we have been fixing this month: *a path the customer thinks is protected is not in the copy.*
-  It is the reason the proof stopped before the wipe — wiping would have destroyed the marked file and
-  proven nothing. **The two apps that were already backing up off-site are unaffected** — they declare
-  no such folders. *(R-203)*
+- *(fixed 4 Aug)* ~~A backup reported success while leaving out a folder the customer was told is
+  protected.~~ **Both halves fixed the same day.** The app was writing to one folder and the backup was
+  looking in another — one directory apart, on machines whose apps live on the system disk. They now
+  resolve to the same place, from a single piece of code instead of the three near-copies that had
+  quietly drifted. **And a backup that cannot capture a folder marked essential no longer reports
+  success**: it reports *Hiányos* (incomplete), names the app and the folders, and tells you — while
+  still recording what it genuinely did capture, because half a backup is not no backup. Proved on the
+  HP machine by listing the backup's own contents and finding the marked file there by name and size —
+  not by trusting a green tick. *(R-203)*
 - **One screen still tells the customer something we cannot yet promise.** The „elárvult tároló" card
   says the old backups may later be restorable with the matching recovery code. From today that is true
   for machines that re-seal from now on and **false for anything already orphaned** — and the machine
@@ -104,9 +103,10 @@ Proven end to end on real hardware.
 
 ## What we're working on
 
-- **Now:** fixing the folder-left-out-of-the-backup problem above. The wipe-and-restore proof is
-  **staged and waiting on it** — the machine, the code, the working off-site store, the app and the
-  marked file are all in place; only the missing folder blocks it. Nothing was wiped. Both honesty fixes shipped today: a changed backup key now
+- **Now:** the wipe-and-restore proof, which is **unblocked and staged**. The marked file now lands in
+  the off-site backup, so there is finally something to recover. Everything else is already in place on
+  the HP machine — the recovery code you saved, a working off-site store, the app and the file. Nothing
+  has been wiped; that step waits for your go-ahead at a marked stop point. Both honesty fixes shipped today: a changed backup key now
   raises an alarm on the day, and the email that stated the opposite of what it measured now describes
   what it actually saw.
 - **Also tomorrow:** confirming what the 04:15 off-site run does on both machines. We expect it to
@@ -158,6 +158,10 @@ Proven end to end on real hardware.
 
 ## Changed since last update
 
+- **2026-08-04 (latest)** — **Fixed the folder-left-out-of-the-backup problem, both halves.** The app
+  and its backup now look in the same directory, and a backup that misses a folder marked essential
+  reports *incomplete* instead of success. Proved by listing the backup's own contents and finding the
+  marked file. The wipe-and-restore proof is unblocked. *(R-203, R-201)*
 - **2026-08-04 (late)** — Set up the wipe-and-restore proof on the HP machine and **stopped before the
   wipe**: a folder marked as protected was missing from the off-site backup while the backup reported
   success. Three things were proved on the way, all firsts: a rebuilt machine's off-site backup now