diff --git a/REPORT.md b/REPORT.md
index 9b91407..48ff647 100644
--- a/REPORT.md
+++ b/REPORT.md
@@ -1,7 +1,14 @@
-# REPORT — the shared rule file (2026-10-06 evening)
+# REPORT — the second burn-down night (2026-10-06 → 07): R-894 and the R-330 wire half, on main, unreleased
 
-Operator ruling 2026-10-06 14:24 (`09` §3 decision 152): the agent repo gets its copy of the shared rule file. Added
-`.claude/rules/unprompted-work.md`, byte-identical to the other copies (`diff` against felhom-controller's copy: no
-output; md5 `c1e6c881…` across all five before the copies line changed, one md5 after). No code changed; no release.
-`agent_gates.py --fast`: reuse-refs, instructions, release-complete, observations OK. The session report is
-`felhom.eu/REPORT.md`.
+Nothing was released or delivered (brief fence). Both changes ship with the memory-kill check as **v0.150.0**, after the
+2026-10-07 night read-back. Session report: `felhom.eu/REPORT-night-burndown-2026-10-06.md`; night log
+`felhom.eu/documentation/audits/night-burndown-2026-10-06/NIGHT-LOG.md`.
+
+- **R-894** (`74b5eae`): the newest successful backup per tier is kept on disk (`backup-success-state.json` in the OOB
+  state dir) and read by `/backup/due` **only when the tier's storage cannot be read**: fresh → not due, older than the
+  cadence → due, none → due with age unknown (as before). A storage that answers stays the ground truth. Tests
+  `TestBackupDue_R894_*`, `TestBackupSuccessState_*`, `TestR894_LastKnownBackupsIsWiredIntoTheDaemon`; four red-proofs
+  `felhom.eu/documentation/audits/night-burndown-2026-10-06/s4/`. Architecture: `07` §6.1 updated.
+- **R-330, wire only** (`adaf86a`): the host report's SMART summary carries 187 `reported_uncorrect`, 188
+  `command_timeout`, 199 `udma_crc_errors` (pointers, omitted when unknown). No verdict reads them.
+- Suite `go test ./...` rc 0; `scripts/agent_gates.py` (full) all OK; CI green on each push (runs 1451, 1467).