E-2d teardown complete: drill customer + host removed from the hub

The delete was correctly refused at four successive gates while the host still
read ONLINE (acknowledgements -> typed confirm_id -> expect_hosts stale-preview
-> "host is ONLINE"). Rather than force it, the run waited for the destroyed
host to age to DOWN; delete-impact then reported deletable:true and the
documented cascade ran:

  host deleted (escrow demoted to retained custody), tenantsync deprovisioned,
  PBS tenancy deprovisioned, claim reset to unclaimed, residue purged
  (reports=5 app_telemetry=5 notif_prefs=1 appliance_registrations=1)

Verified after: 0 occurrences of "e2d" anywhere on the hosts page; demo-felhom
and demo-hp ONLINE on agent 0.113.0; drill-r50 and peti-felhom unchanged;
demo-hp carries only guest 9201 and VM 300.

Scoping checked rather than assumed: the single purged appliance_registration
was this run's own appliance (810d10c5, bound to e2d-fresh). The unrelated stale
2026-07-25 appliance (206c8838 / QWA-WJE) was NOT touched by the cascade — the
operator removed it separately.

- OPEN-ITEMS.md: the drill-cleanup WATCHING row is removed (done, not open).
- audits/E2D-fresh-vm-2026-07-29.md §8 + REPORT-e2d.md: teardown recorded as
  complete, with the cascade output and the appliance-scoping note.

REPORT-e2d.md

@@ -65,7 +65,8 @@ from `raw/branch/main` and the hub vouches a sha for **one**; E-2a's wrapper is
 
 - `OPEN-ITEMS.md` — **R-112/R-113/R-114 opened**; E-2d re-stated with results and left open for the
   residue; E-2's "NOT yet live-proven" list resolved into proven / known-broken; R-94 fully unblocked;
-  R-110 extended; a WATCHING row for the drill cleanup.
+  R-110 extended. The drill-cleanup row was opened and then **closed the same session** once the
+  teardown completed, so it is not carried in the register.
 - `ROADMAP.md` — R-112/R-113/R-114 under P1; R-111 marked SHIPPED.
 - **`architecture/00-capability-map.md` not touched** — for two reasons: the customer-facing legs are
   broken rather than proven, and the map has **no E-2 / backup-target rows at all** (worth noting
@@ -74,10 +75,7 @@ from `raw/branch/main` and the hub vouches a sha for **one**; E-2a's wrapper is
 ## Teardown
 
 VM destroyed, scratch storage removed, **`pvesm status` after == before** (`local-lvm` 38.77 %,
-byte-identical), guest 9201 and drill-r50 untouched. **Hub records for `e2d-fresh` remain** — the
-delete was attempted and correctly refused at four gates, finally `host … is ONLINE`; it becomes
-deletable once the destroyed host ages to DOWN (>1 h). Command recorded in `OPEN-ITEMS.md`. The stale
-2026-07-25 appliance (`206c8838…`) was left alone — not mine.
+byte-identical), guest 9201 and drill-r50 untouched. **Hub records removed — teardown complete.** The delete was correctly refused at four gates while the host still read ONLINE; once the destroyed host aged to DOWN (`delete-impact` → `deletable:true`) the documented cascade ran and completed: host deleted, PBS tenancy deprovisioned, claim reset, residue purged. Verified after: **0** `e2d` occurrences on the hosts page, fleet unchanged. The one purged `appliance_registrations=1` was this run's own appliance; the unrelated stale 2026-07-25 appliance (`206c8838…`) was not touched by the cascade — the operator removed it separately.
 
 ## One human step, and a premise correction