docs: fix genuine passive-voice hits in docs/turn-loop

Fifth batch of the ongoing write-good.Passive pass (hyperhive#4042):
read all 42 hits across the four docs/turn-loop files in context and
rewrote the 36 with a clearly nameable actor, usually one already
sitting in the same sentence or established a sentence or two earlier
(the broker, the harness, drive_turn, the renderer, hive-c0re, or a
specific fn/type named right there). Left 6 alone: predicate-adjective
copulas that only look passive ("is gone", "Bash is disallowed", "is
documented behavior" — nothing actually acts on the subject), a
config-conditional idiom with no in-file inconsistency to fix ("when
hyperhive.docs.enable is set"), and a paraphrase of what a rendered
message tells the agent ("the docs are mounted at that path").

Verified via vale before/after: 42 -> 6 write-good.Passive hits in
docs/turn-loop, exactly the 6 left alone; error count and other
warning categories unchanged. Re-read every changed line in its full
surrounding context after editing (not just the vale count) per the
lesson from the docs/process batch.

docs/turn-loop/mcp.md

@@ -1,8 +1,8 @@
 # MCP surface
 
-The harness ships an embedded MCP server (rmcp 2). The built-in
-`hyperhive` surface is served over streamable HTTP by a persistent
-`hive-mcp-http` daemon (loopback, `127.0.0.1:<hyperhive.mcp.httpPort>`,
+The harness ships an embedded MCP server (rmcp 2). A persistent
+`hive-mcp-http` daemon serves the built-in `hyperhive` surface over
+streamable HTTP (loopback, `127.0.0.1:<hyperhive.mcp.httpPort>`,
 per-container private netns). Claude connects to its stable URL via
 `--mcp-config` rather than respawning a stdio child each turn, so the
 URL survives the per-turn claude re-spawn (and a host-side hive-c0re
@@ -15,7 +15,7 @@ stdio bridge, `bash` runs its own persistent streamable-http listener
 server name is `hyperhive`, so the tools land in claude as
 `mcp__hyperhive__<tool>`.
 
-Tool access is gated by tool groups (`HIVE_TOOL_GROUPS`). The default
+Tool groups (`HIVE_TOOL_GROUPS`) gate tool access. The default
 preset (`AGENT_DEFAULT`) includes `messaging`, `meta`, `inbox`, and
 `execution`. Privileged groups (`lifecycle`, `approvals`, `scheduling`,
 `diagnostics`) are opt-in via the P3RM1SS10NS tab.
@@ -36,8 +36,8 @@ preset (`AGENT_DEFAULT`) includes `messaging`, `meta`, `inbox`, and
   (the topology parent is always reachable regardless of this list —
   that carve-out is structural, keyed on parent relationship, not name).
 - `recv` — drain inbox. Always an immediate peek, never blocks. `max`
-  (default 1, cap 5) drains up to N rows. Each returned row is prefixed with
-  `[msg #<id>]` (broker row id; note the highest id seen, then pass
+  (default 1, cap 5) drains up to N rows. `recv` prefixes each returned row
+  with `[msg #<id>]` (broker row id; note the highest id seen, then pass
   it to `ack_until` to bulk-triage the batch). **Graceful shutdown**: when the harness
   receives a stop signal, the inbox becomes fenced and `recv` returns an
   explicit `from: "graceful-stop"` message instead of an empty inbox.
@@ -47,17 +47,17 @@ preset (`AGENT_DEFAULT`) includes `messaging`, `meta`, `inbox`, and
   other turn: if the context crossed the watermark the harness runs a
   notes-checkpoint turn and then `/compact`. Compacting before shutdown
   keeps a later cold start cheap instead of re-uploading a large transcript.
-- `ack_until(up_to)` — bulk-mark inbox rows handled: every row with
-  broker id `<= up_to` is stamped as acked in a single UPDATE.
+- `ack_until(up_to)` — bulk-mark inbox rows handled: it stamps every row
+  with broker id `<= up_to` as acked in a single UPDATE.
   Recipient-scoped (agents can only ack their own rows). Use when a
   restart redelivers a large backlog of already-handled messages: read
   the highest `[msg #N]` from the set you've actually processed, then
   `ack_until(N)` to prevent re-pop. Acked rows never redeliver.
   Transient pings (sentinel id 0) have nothing to ack and show no marker.
 
-**System messages** (from sender `system`): the higher-urgency
-lifecycle events (`hive_sh4re::manager::HelperEvent`) are
-delivered as regular inbox messages (same `recv` path; body is a JSON
+**System messages** (from sender `system`): the broker delivers the
+higher-urgency lifecycle events (`hive_sh4re::manager::HelperEvent`)
+as regular inbox messages (same `recv` path; body is a JSON
 object with an `event` discriminant field). The **submitting agent**
 (the root agent for top-level containers; an agent with the `approvals`
 tool group for its own subtree) receives `container_crash`,
@@ -136,7 +136,7 @@ hive_name?, swarm_name?, matrix_accounts? }`. `matrix_accounts` is a
   [`docs/tools/scheduling.md`](../tools/scheduling.md).
 - **Forge repos** (`forge`) — `create_repo` — the only agent path to
   create a repo under the `agents/` org (direct forge token creation is
-  disabled for agents). The repo is created in the c0re-owned `agents`
+  disabled for agents). The repo lands in the c0re-owned `agents`
   org; the calling agent gets write collaborator access; the default
   branch is branch-protected (operator-team must approve merges, so the
   agent can't self-merge). Opt-in; not in any default preset.
@@ -202,8 +202,8 @@ status hint lives in the wake prompt + UI header, not here.
   `Skill` is what makes an installed plugin's `SKILL.md` invokable —
   without it, a skill's `description` frontmatter never gets seen by
   the model no matter how well it matches the task.
-- Tool-group-gated built-ins: `WebFetch`, `WebSearch` (added when the
-  `web_tools` tool group is enabled — see P3RM1SS10NS tab).
+- Tool-group-gated built-ins: `WebFetch`, `WebSearch` (added once the
+  operator enables the `web_tools` tool group — see P3RM1SS10NS tab).
 - Denied by omission (absent from the harness `--tools` /
   `--allowedTools`, so they "literally don't exist" in a harness turn):
   `Bash`, `Task`, `NotebookEdit`, `TodoWrite`.