docs: clear write-good.Passive hits in matrix/persistence docs

Part of #4548 — second batch. This PR: docs/integrations/matrix.md
(18 hits), docs/agent-lifecycle/persistence.md (17 hits) = 35 more of
the 353 (99 total across the two PRs so far).

Same method as the first batch (#4551): minimal, meaning-preserving
active-voice rewrites only, no restructuring beyond what each flagged
sentence needed, no vale-off silencing.

Genuine false positives left in place, with per-file reasoning in the
PR body: predicate-adjective state descriptions ("is wedged", "is
stopped", "are unrelated", "is unaffected", "is needed"), one
design-intent idiom ("was meant to prevent" — same shape as earlier
docs-lint work), and one vale parsing artifact: "is read" flagged
inside the hyphenated compound adjective "read-only", not real passive
voice at all.

docs/agent-lifecycle/persistence.md

@@ -20,7 +20,7 @@ keeps its state, purging it doesn't.**
 
 Beyond that:
 
-- **Approvals are kept forever** — they're an audit trail, not a
+- **hive-c0re keeps approvals forever** — they're an audit trail, not a
   cache. Nothing about them ever ages out.
 - **Broker messages**: acked ones vacuum after 30 days; anything
   undelivered or delivered-but-not-yet-acked is always kept, however
@@ -89,7 +89,7 @@ Retention:
   rows are always kept — the harness `ack_turn`s only after a
   successful turn, so `requeue_inflight` can still requeue
   an unacked row on a crash.
-- Approvals are kept indefinitely — an audit trail. `actions::destroy`
+- hive-c0re keeps approvals indefinitely — an audit trail. `actions::destroy`
   rows stay visible to anything that queries by id.
 - Scheduled prompts: the worker deletes one-shot rows on fire;
   recurring rows live until the operator cancels them
@@ -275,7 +275,7 @@ Under `/var/lib/hyperhive/agents/<name>/`:
     by `set_status`; cleared on explicit `set_status("")`. Read by
     hive-c0re and the per-agent `/api/dashboard-state` endpoint to
     surface the status chip on the dashboard. Absent when no status
-    is set.
+    has a value.
   - `hyperhive-harness.json` — rate-limited / needs-login flags read
     by the dashboard's async container-state fetch. See
     `docs/web-ui/dashboard.md::Container row`.
@@ -353,7 +353,7 @@ tree anyone edits in place. Mounting it writable would leave a second
 path to the same file that skips the review entirely, which makes the
 boundary a convention rather than a permission.
 
-⚠️ Not to be confused with the config-repo seeding hive-c0re does at
+⚠️ Don't confuse it with the config-repo seeding hive-c0re does at
 spawn (`lifecycle::setup_proposed`): that writes the child's initial
 config repo as **hive-c0re, against the host path**, and `read_only` on a bind
 constrains writers *inside* a container only. The two are unrelated —
@@ -410,10 +410,10 @@ Contents:
 The root agent has the meta dir RO-mounted at `/meta/`.
 
 The `.meta-migration-done` marker no longer exists: the
-one-shot container repoint it guarded has been removed, since
+one-shot container repoint it guarded no longer exists either, since
 hive-c0re renders containers onto `meta#<n>` at creation. A stale
-marker file left over from an older hive is inert and can be
-deleted.
+marker file left over from an older hive is inert and the operator can
+delete it.
 
 ## Destroy vs purge
 
@@ -439,7 +439,7 @@ On a btrfs host, `lifecycle::ensure_agent_state_subvolume` creates a brand-new a
 **btrfs subvolume** instead of a plain directory (progressive
 enhancement). This is a no-op fallback on
 non-btrfs hosts and for any agent whose root already exists, so
-nothing is automigrated: existing agents keep their plain dirs
+hive-c0re automigrates nothing: existing agents keep their plain dirs
 until an explicit opt-in upgrade.
 
 - **Creation:** `lifecycle::ensure_agent_state_subvolume` runs before
@@ -451,8 +451,8 @@ until an explicit opt-in upgrade.
   succeed inside it.
 - **DESTR0Y keeps the subvolume** exactly like a plain dir — revival
   reuses it untouched.
-- **PURG3 deletes it correctly:** a subvolume root can't be removed
-  with `rmdir`/`remove_dir_all`, so purge first calls hive-priv
+- **PURG3 deletes it correctly:** `rmdir`/`remove_dir_all` can't remove
+  a subvolume root, so purge first calls hive-priv
   (`DeleteAgentSubvolume`) which `btrfs subvolume delete`s it iff it's
   actually a subvolume, then the normal `remove_dir_all` sweep covers
   plain-dir agents + the applied dir.
@@ -491,7 +491,7 @@ controller serves is unaffected.
 `/run/hyperhive/` is tmpfs-backed (systemd `RuntimeDirectory=`) but
 preserved across hive-c0re restarts via `RuntimeDirectoryPreserve=yes`.
 Without that, every restart wipes bind sources and existing
-containers can't be started.
+containers can't start.
 
 - `/run/hyperhive/host.sock` — admin socket (host-side CLI).
 - `/run/hyperhive/agents/<name>/mcp.sock` — per-agent socket
@@ -585,7 +585,7 @@ bring-up loop, so it sets the avatar for **every** account.
 Nix rasterizes the SVG to a 512x512 PNG at build time (`iconPng`, via
 librsvg) and forwards its store path as `HIVE_ICON_PNG` on the daemon
 unit, gated on `services.hyperhive.agent.icon != null`. No icon configured → the env is
-unset → `sync_avatar` returns early and no avatar is set.
+unset → `sync_avatar` returns early and sets no avatar.
 
 Idempotency is **per-account**: an `avatar-icon-hash` file in each
 account's matrix-sdk `state_dir`. The daemon hashes the PNG bytes and