docs: fix genuine passive-voice hits in docs/agent-lifecycle

Ninth batch of the ongoing write-good.Passive pass (hyperhive#4042):
read all 75 hits across agent-hierarchy.md/persistence.md/approvals.md
in context and rewrote 46 with a clearly nameable actor -- mostly
hive-c0re, a specific fn/type named right there or a sentence or two
earlier (approvals.md's numbered "Reminder delivery" list all share
hive-c0re as the established actor across three consecutive bullets),
or "the worker"/"the daemon" reused from the section's own established
subject.

Left 29 alone. Recurring buckets: predicate-adjective state pairs
("is wedged"/"is stopped", "is unaffected", "are unrelated", "is
overloaded" -- matches the established "is trusted"/"is privileged"
family), negative-capability/invariant idioms ("no X is needed",
"can't be removed/started", "no such transient was cleared"),
forward-looking design-intent statements about not-yet-built
enforcement (agent-hierarchy.md's whole "Planned topology semantics"
section leans on this: "are meant to run", "once enforcement is
finished", "will be gated"), the "audit trail, not cache" policy
invariant restated twice verbatim ("Approvals are kept forever" /
"indefinitely" -- left both alone consistently), and a config-
conditional state idiom ("when interval_seconds is set"). One more
false-positive tokenization, same bug as knowledge.md's earlier case:
persistence.md's "`config` is read-only" trips vale's "is read" match
inside the compound adjective -- not a real passive at all.

One deliberately-conservative leave: agent-hierarchy.md's "Reminder
cancellation is handled fully in-agent" had an ambiguous actor (the
in-agent socket vs. the hive-c0re source file the doc points readers
to for detail) -- left alone rather than risk a wrong attribution,
unlike the higher-confidence rewrites elsewhere in the same batch.

Verified via vale before/after: 75 -> 29 write-good.Passive hits,
exactly the 29 left alone above; error count and other warning
categories unchanged. Re-read every changed line in full surrounding
context after editing before running the final vale check.

docs/agent-lifecycle/agent-hierarchy.md

@@ -1,8 +1,8 @@
 # Agent hierarchy & privileges
 
 Every agent has a place in an operator-editable parent/child tree, used
-to scope which agents can manage which others. This doc covers how the
-tree is stored and edited today, the rules that are meant to run on top
+to scope which agents can manage which others. This doc covers how
+hive-c0re stores and edits the tree today, the rules that are meant to run on top
 of it once enforcement is finished, and where the manager still gets
 special-cased in the meantime. Tracking issue: hyperhive#361
 (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/361`).
@@ -24,7 +24,7 @@ Topology lives in the hive-c0re-owned **meta repo**, alongside
 structural manager that everything hangs under. Hierarchy is built
 explicitly: an agent that requests a sub-agent gets a
 requester-as-parent edge written at its `init_config` approval (so
-`bob` above was spawned by `alice`), and the operator can reparent any
+`alice` spawned `bob` above), and the operator can reparent any
 agent, including the bootstrap container (`ruth`) — it's just another
 root. The manager is reparentable like any other agent; there's no
 "structurally root" carve-out. Its privileges live on its MCP socket,
@@ -64,11 +64,11 @@ where system-level facts live.
   install that hasn't synced yet).
 - **Reconcile** — runs alongside the periodic meta/flake regeneration.
   New agents default to root unless they already carry an explicit
-  parent edge from an `init_config` approval; existing entries
-  (including operator overrides) are preserved; removed agents drop.
+  parent edge from an `init_config` approval; Reconcile preserves existing entries
+  (including operator overrides); removed agents drop.
   Agents that are approved but not yet spawned keep their edge too, so
   it survives the gap until the container actually appears.
-- **Inject** — each container's parent (if any) is exposed to its own
+- **Inject** — hive-c0re exposes each container's parent (if any) to its own
   environment as `HIVE_PARENT`, so the harness / system-prompt
   renderer can see it.
 - **Surface** — every rescan re-reads `topology.json` and populates
@@ -98,8 +98,8 @@ umount-old / mount-new / restart-cascade step.
 | `send` / `recv` routing                                     | parent ↔ same-parent siblings ↔ self ↔ descendants; explicit allow-list for anyone else |
 | `request_update_meta_inputs` (bump meta lock)               | root agents only (today: just `manager`)                                                |
 
-"Ancestor" walks `ContainerView.parent` chains; cycles are guarded by a
-visited-set at dispatch time (a malformed `topology.json` can't lock
+"Ancestor" walks `ContainerView.parent` chains; a visited-set guards against
+cycles at dispatch time (a malformed `topology.json` can't lock
 the dispatcher into a loop).
 
 ## Manager special-casing today