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/config.md

@@ -14,7 +14,7 @@ hyperhive.docs.enable = true;  # default: false (true for the manager agent)
 Makes the hyperhive `docs/` tree available inside the container at a nix
 store path read from `$HIVE_DOCS_DIR`, and injects a single pointer
 sentence into the agent's system prompt so it knows the docs exist and
-where to find them. The tree is served by `claude --add-dir` so the full
+where to find them. `claude --add-dir` serves the tree so the full
 markdown is readable during every turn.
 
 Enabled by default only for the root/manager agent (`nix/templates/ruth.nix`). Any
@@ -81,8 +81,8 @@ entry has:
 | `url`   | yes      | Absolute URL — may include a different port (the dashboard renders it as a plain anchor). |
 | `icon`  | no       | Emoji or short glyph prefix. Defaults to empty string.                                    |
 
-The list is written to `<state>/hyperhive-dashboard-links.json` by a
-one-shot systemd unit at container boot. The harness's own web UI
+A one-shot systemd unit writes the list to
+`<state>/hyperhive-dashboard-links.json` at container boot. The harness's own web UI
 (`agent_links` in `hive-agent/src/web_ui/state.rs`) reads the file on
 each `/api/state` snapshot and appends the entries to the per-agent
 nav as `kind = External` links — no `hive-c0re` / operator-dashboard
@@ -116,8 +116,8 @@ attribute defines one overlay entry:
   (`"games/bitburner"` serves at `/games/bitburner/…`).
 
 Constraints: `target` must start with an alphanumeric or `_` and
-contain only alphanumerics, `_`, `.`, `/`, `-`. `..` segments are
-rejected by a config assertion. The merge step refuses to overwrite
+contain only alphanumerics, `_`, `.`, `/`, `-`. A config assertion
+rejects `..` segments. The merge step refuses to overwrite
 files already present in the default dist — pick a target name that
 doesn't collide with existing paths (`static/`, `index.html`, etc.).
 
@@ -153,8 +153,8 @@ to the wrong machine. With `null` the `tea-login` and `forge-avatar-sync`
 units aren't generated at all: an absent integration rather than a
 misdirected one. You don't normally set this — hive-c0re renders the
 host's real forge URL into every agent, and refuses to write a meta
-flake without one, so `null` only survives where the agent modules are
-evaluated outside a hive.
+flake without one, so `null` only survives where nix evaluates the
+agent modules outside a hive.
 
 **`hyperhive.matrix.url`** — homeserver URL used by
 `hive-matrix-daemon` when connecting via the matrix-sdk. hive-c0re
@@ -170,7 +170,7 @@ agent's own netns to the agent itself, not the homeserver). With
 `null` the daemon has no homeserver and no-ops exactly as it does
 without a token. The hive only forwards `HIVE_MATRIX_URL` when it
 actually has a matrix vhost to name, so `null` survives where a hive
-runs no homeserver, or where the agent modules are evaluated outside a
+runs no homeserver, or where nix evaluates the agent modules outside a
 hive.
 
 ## Claude Code plugins
@@ -199,9 +199,9 @@ hyperhive.claudePluginsAutoUpdate = false;               # default
   to add custom marketplaces. Idempotent — re-adding an existing
   source is a no-op.
 - **`claudePlugins`** — list of plugin specs passed to
-  `claude plugin install <spec>`. Each spec is installed on every boot
-  (`install` is expected to be idempotent); failures log a warning but
-  don't abort boot. Defaults to Anthropic's `skill-creator` (so every
+  `claude plugin install <spec>`. The harness installs each spec on
+  every boot, assuming `install` is idempotent; failures log a warning
+  but don't abort boot. Defaults to Anthropic's `skill-creator` (so every
   agent can author, refine, and evaluate its own skills) plus
   hyperhive's own `base` plugin — skills that apply to every agent
   regardless of role (currently just `state-hygiene`) — all without
@@ -234,8 +234,8 @@ window, leaving only warnings and errors.
 
 The function handles `+toolchain` selectors (`cargo +nightly build`)
 and passes through cleanly when `--message-format` is already present.
-Non-compile subcommands (`new`, `add`, third-party `cargo-*`) are
-left untouched.
+It leaves non-compile subcommands (`new`, `add`, third-party
+`cargo-*`) untouched.
 
 Set to `false` for agents that parse cargo's JSON output
 programmatically and don't pass `--message-format json` themselves.
@@ -256,12 +256,12 @@ is a no-op without the other:
 - **`useApiKey`** tells the harness itself not to wait for a Claude OAuth
   session: at boot, `LoginState::from_dir` reports `Online` without
   checking `~/.claude/` (`hive_agent::login::using_api_key`, reads
-  `HIVE_USE_API_KEY`), and the fact is stamped into the consolidated
-  harness state file so the operator dashboard also stops reading this
+  `HIVE_USE_API_KEY`), and the harness stamps the fact into the
+  consolidated harness state file so the operator dashboard also stops reading this
   agent's empty `~/.claude/` as "needs login." An api-key agent that hits
-  a real 401 (the key itself is bad) still surfaces `needs_login` — only
-  the boot-time "have I ever logged in" check is bypassed, not the
-  auth-failure path.
+  a real 401 (the key itself is bad) still surfaces `needs_login` — the
+  harness skips only the boot-time "have I ever logged in" check, not
+  the auth-failure path.
 - **`backendEnvironmentFile`** points at an operator-managed file
   (outside the nix store, one `KEY=value` per line, systemd
   `EnvironmentFile` syntax) supplying the credentials `claude` itself