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/claude-invocation.md

@@ -27,8 +27,8 @@ harness unit's PATH. By default that's the `claude-code` in the agent's
 own nixpkgs (the meta flake's `nixpkgs` input) via
 `environment.systemPackages`. Since that's typically a release channel and
 this package moves fast, the operator can pin one hive-wide with
-`services.hyperhive.c0re.claudeCodePackage`: its store path is written
-into each agent's flake, and `claude` on PATH becomes a symlink to it
+`services.hyperhive.c0re.claudeCodePackage`: hive-c0re writes its
+store path into each agent's flake, and `claude` on PATH becomes a symlink to it
 instead of the container's own `claude-code` — so there's only ever one
 `claude` in the container. Agents pick up a new build on their
 next rebuild, not live. See docs/process/gotchas.md::`claude-code` is unfree.
@@ -37,21 +37,21 @@ Hive-enforced settings ship at `/etc/claude-code/managed-settings.json`
 (claude-code's canonical managed-settings path — precedence #1,
 read-only, un-overridable), wired in `nix/agent-modules/claude-settings.nix`
 from the `prompts/claude-settings.json` asset. `effortLevel` is
-deliberately not in that file — effort is controlled live via the
-`--effort` flag (`HIVE_DEFAULT_EFFORT` / the per-agent UI slider), which
-managed scope would otherwise lock.
+deliberately not in that file — the `--effort` flag
+(`HIVE_DEFAULT_EFFORT` / the per-agent UI slider) controls effort
+live, which managed scope would otherwise lock.
 
-`<name>` is read from `Bus::model()` on each turn. The initial
-default is set by `hyperhive.model` in the agent's `agent.nix`
-(NixOS option; propagates via `HIVE_DEFAULT_MODEL` env var; falls
+The harness reads `<name>` from `Bus::model()` on each turn.
+`hyperhive.model` in the agent's `agent.nix` sets the initial
+default (NixOS option; propagates via `HIVE_DEFAULT_MODEL` env var; falls
 back to `"haiku"` if unset). The operator can flip it at runtime
 with `/model <name>` in the web terminal — the next turn picks it
-up. The choice is persisted to `/harness/hyperhive-model` so it
+up. The harness persists the choice to `/harness/hyperhive-model` so it
 survives restart; override path: `HYPERHIVE_MODEL_FILE` env var
 for tests.
 
-Context-window size is looked up per-model via
-`harness_state::context_window_tokens(model)`. Resolution order (first
+`harness_state::context_window_tokens(model)` looks up
+context-window size per-model. Resolution order (first
 match wins):
 
 1. `HIVE_CONTEXT_WINDOW_TOKENS_<KEY>` env var, where `KEY`
@@ -65,8 +65,8 @@ match wins):
 3. Hard fallback: `200_000` (conservative; only reached outside
    NixOS where the env vars aren't set).
 
-The effective window drives watermarks and is exposed at runtime
-via `/api/state.context_window_tokens` so the UI can show a
+The effective window drives watermarks; the harness exposes it at
+runtime via `/api/state.context_window_tokens` so the UI can show a
 percentage-of-window ctx badge.
 
 **Session identity — a constant title.** Every turn keys on one fixed,
@@ -86,8 +86,8 @@ context (it won't carry our title). claude stores sessions in
 `--name` writes the title into the file as a `custom-title` event, which
 is what `--resume <title>` resolves against. We never pass bare
 `--continue` (it resumes the _latest_ session in the cwd — the hijack
-vector). Automemory and dynamic workflows (the `/workflows` feature) are
-disabled via the managed settings at `/etc/claude-code/managed-settings.json`:
+vector). The managed settings at `/etc/claude-code/managed-settings.json`
+disable automemory and dynamic workflows (the `/workflows` feature):
 `disableWorkflows` keeps the `/workflows` machinery from spawning sub-runs
 that burn usage on the harness's autonomous turns. Claude's own native
 autocompact is **on**, at the widest window claude-code allows — see
@@ -98,10 +98,10 @@ primary mechanism; hyperhive still owns that).
 `/new-session` slash command). It does _not_ touch the session inline —
 that would race a mid-write claude process. Instead `Bus::request_session_reset()`
 sets a one-shot flag consumed at the next turn boundary by `drive_turn`,
-which **archives** the current session: the backing `<uuid>.jsonl` is
-renamed to `<uuid>.jsonl.archived` (dropped out of claude's `*.jsonl`
+which **archives** the current session: it renames the backing
+`<uuid>.jsonl` to `<uuid>.jsonl.archived` (dropped out of claude's `*.jsonl`
 resolution glob, history preserved on disk, only the file carrying _our_
-title — any `choom` session sharing the cwd is left alone). The next
+title — it leaves any `choom` session sharing the cwd alone). The next
 turn's `--resume <title>` then misses and self-heals into a fresh session.
 
 ## Compaction
@@ -126,9 +126,9 @@ into its `run`:
   _then_ `/compact`s, so the agent can persist in-flight state before the
   detail collapses into a summary.
 
-**Both triggers above are checked between hive-agent's own turns** — the
-percent watermark is read from the last completed turn's telemetry
-(`PercentPolicy::should_compact`, checked after `attempt()` returns), and
+**hive-agent checks both triggers above between its own turns** —
+`PercentPolicy::should_compact` reads the percent watermark from the
+last completed turn's telemetry (checked after `attempt()` returns), and
 the reactive path only fires once claude-code has already refused a whole
 turn as too long. Neither can see context growth happening _inside_ a
 single long turn's own tool-calling before it returns — a turn whose tool
@@ -188,8 +188,8 @@ still applies.
   benefit over starting fresh. `drive_turn` **archives** the current
   session (same mechanism as the operator reset — rename `<uuid>.jsonl` →
   `.archived`) so the next turn's `--resume <title>` misses and starts
-  fresh. Unlike proactive compaction the session is dropped entirely, not
-  compacted — and _no_ preceding checkpoint turn runs, because any turn
+  fresh. Unlike proactive compaction, `drive_turn` drops the session
+  entirely rather than compacting it — and _no_ preceding checkpoint turn runs, because any turn
   before the reset would just re-warm the cache and defeat the purpose.
   Set `HIVE_AUTO_RESET_WATERMARK_TOKENS=0` to disable. Autoreset and the
   operator reset are mutually exclusive per turn (both archive → fresh
@@ -250,9 +250,9 @@ needs to `chown` a bind mount), once at startup:
 
   **Marker grammar.** `<!-- role:X -->` opens a block; any
   `<!-- /role:X -->` closes the current block. The renderer always uses
-  role `agent`, so blocks with other role tags are elided. Nesting is NOT
+  role `agent`, so it elides blocks with other role tags. Nesting is NOT
   supported — a stray opener with no closer runs until end of file.
-  Whitespace inside markers is tolerated (`<!--role:foo-->` parses the
+  The renderer tolerates whitespace inside markers (`<!--role:foo-->` parses the
   same as `<!-- role:foo -->`). Content outside any marker is always
   included. Today's `system.md` carries no markers (single agent role) —
   the grammar stays wired for a future manager / multi-role prompt.