docs: v0.242.0 report, context; R-489 measured limit recorded (row kept open)

A volume recreated by a unit restore carries no compose label, so the
before/after difference misses it; proven on the scratch guest. Docs only,
no release.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

CHANGELOG.md

@@ -27,7 +27,11 @@
   reader of the empty `cfg.Paths.HDDPath` already had (R-465).
 - **R-489 — `volumes_removed` reports the volumes a removal removed**, `[]` when none — never `null`:
   the project's volumes are listed before and after `down --volumes` and the difference is reported
-  (compose's progress lines are printed to a TTY it does not have here).
+  (compose's progress lines are printed to a TTY it does not have here). **Measured limit, live on
+  9202 the same night (row kept open):** the listing filters on the compose project LABEL, and a
+  volume recreated by a unit restore (`docker volume create <name>`, `restore.go`) carries no labels
+  — compose still removes it, and the response says `[]`. A fresh compose-created volume is
+  reported. Next release lists by the `<project>_` name prefix as well.
 - **R-456 — the boot-orphan rule is pinned:** an absent member does not make a stack degraded, so a
   partly-dead stack is not a boot orphan; a present-but-dead member is (`internal/bootrecon/r456_partly_dead_test.go`).