finalwalk teardown complete; R-244 filed; session report

All five layers gone, each verified with a positive control that must
survive and does:
  VM 324 + 4 disks   -> absent (VM 300 drill-r50 remains)
  hub: 13 tables at 0, incl. BOTH escrow tables (demo-felhom/demo-hp/peti remain)
  Storage Box u629488-sub4 -> gone (sub1/2/3 remain)
  ep0 PBS ns finalwalk     -> gone (demo-felhom, demo-hp remain)
  WireGuard 10.77.0.5      -> gone from the LIVE wg show on ep0, not just
                              the hub DB (.2/.3/.4/.250 remain)
14.06 GiB reclaimed against 15 G measured before deletion.

R shredded with a planted-copy control: plant -> search finds both ->
shred -> the same search finds 0. The zero was not believed until the
instrument was proven.

R-244 (NEW): a FULL census after the cascade logged COMPLETE full teardown
found 61 rows still matching finalwalk. Four sources are deliberate
provenance; the fifth, app_log_issues (29 rows), is NOT covered by the
residue purge - and it is systematic: c11 40, rewalk 20, part4 24 still
present from the 2026-08-06 teardown, whose ledger recorded zero
occurrences. That claim used a narrower query than a census and does not
hold; the correction is recorded in both the prior ledger and the register
rather than the measurement quietly redone.

No secret material is involved. The table is a fleet-wide aggregate: 12 of
the 29 rows are finalwalk-only orphans, 17 are shared with LIVE customers
and must be de-referenced, not deleted - very likely why the leg was never
written. Not fixed; a cascade change needs its own red-proof.

Lesson, and it is the reusable part: a per-table absence query is not a
census.

documentation/tests/teardown-2026-08-06.md

@@ -107,3 +107,18 @@ under `~/.config/part4/` on DooPlex were shredded.
 **One operational note carried over from the walk:** the `part4` retrieval passphrase was leaked into
 a session transcript on 2026-08-06 and rotated at the time; the customer it belonged to no longer
 exists.
+
+---
+
+## ⚠ CORRECTION, 2026-08-07 — the "0 occurrences" claims above are narrower than they read
+
+Verifying the `finalwalk` teardown with a **full census** (every table, every column) rather than a
+per-table query found rows this ledger's method could not see. `app_log_issues` is **not** covered by
+the cascade's residue purge, and it still holds **`c11` 40 rows, `rewalk` 20, `part4` 24** — plus 29
+for `finalwalk`.
+
+The tables this ledger *did* check are genuinely at zero; the claim that is wrong is the implied
+completeness of the sweep. **A per-table absence query is not a census.** Filed as **R-244**, with the
+reason the leg is not trivial (the table is a fleet-wide aggregate whose rows are shared with live
+customers, so the fix is a de-reference plus an orphan sweep, not a delete). No secret material is
+involved. Full working: `teardown-finalwalk-2026-08-07.md`.