docs: fix genuine passive-voice hits in docs/tools (hand-written files)

Read all 62 write-good.Passive hits across the 6 hand-written files in
docs/tools/ (bash.md, lifecycle.md, forge.md, hivectl.md, matrix.md,
scheduling.md) in context. Excludes forge-cli.md/hivectl-cli.md/
swarmctl-cli.md (57 more hits) -- those are CI-generated from the
clap doc-comment strings in hive-forge/hivectl/swarmctl, freshness-
checked against the committed markdown, so a fix there has to go in
the Rust source and get regenerated -- separate batch.

33 rewritten to active, actor usually already established in the same
paragraph or given via a 'by X' clause (the daemon, hive-c0re,
hive-forge, hivectl, hyperhive itself, or an established module name
like nix/agent-modules/mcp.nix). Several sibling-inconsistency fixes:
a passive clause next to an already-active sibling stating the same
fact (lifecycle.md's server-scoping sentence, forge.md's clone-derives
sentence, hivectl.md's daemon-hashes-passwords sentence, matrix.md's
daemon-upserts-a-todo paragraph).

29 left alone: no-X-is-Y / no-X-is-needed invariant idioms, config-state
conditionals (whenever/when X is set/configured/given), requirement-
list idiom, a false-positive tokenization (vale matching 'are read'
inside 'read-only'), definitional facts about CLI/attrset structure
with no real actor, hypothetical/counterfactual clauses describing a
rejected design alternative, a forward-looking not-yet-real removal,
compressed bullet-fragment conventions, and one deliberately-parallel
sentence structure left both halves alone to avoid breaking the
symmetry.

Verified via vale on the 6 touched files, diffed against main's exact
baseline (not just the Passive count): write-good.Passive 62 -> 29
exactly, every other category unchanged in count AND location
(TooWordy 16, Microsoft.We 1, Microsoft.FirstPerson 1, and the same
4 pre-existing Microsoft.Contractions errors at the same 4 lines).

docs/tools/bash.md

@@ -25,14 +25,14 @@ delivered the terminal result inline, in which case no todo is created
 - `wait_seconds` — inline poll before returning (capped at 30).
   When the task finishes within the window the full status is
   returned immediately and no todo is created; when the window expires
-  the task keeps running and the normal `task started: id=<id>`
-  response is returned. **Defaults to 3** — pass `wait_seconds: 0`
+  the task keeps running and the daemon returns the normal
+  `task started: id=<id>` response. **Defaults to 3** — pass `wait_seconds: 0`
   to disable inline waiting and always get the immediate response.
 - `name` — optional caller-chosen task id. When set it replaces the
   autogenerated hex id, so it surfaces in `status(<name>)` lookups and
   the loose-ends list — a memorable label instead of an opaque id. A name
-  is **reusable once its previous task has finished**; submitting a
-  name whose task is still `pending`/`running` is rejected. Allowed
+  is **reusable once its previous task has finished**; the daemon
+  rejects a name whose task is still `pending`/`running`. Allowed
   characters: `[a-z0-9-]` (a valid identifier — lowercase, digits,
   hyphen; max 63). Omit for the autogenerated id.
 
@@ -48,7 +48,7 @@ Poll the status of a task submitted with `run`. Returns:
 - last 4 KiB of stdout and stderr (full output in the `.out` / `.err` files)
 
 `wait_seconds` — optional inline poll (capped at 30): when the task
-finishes within the window the full status is returned immediately.
+finishes within the window the call returns the full status immediately.
 Useful to avoid a separate round-trip when the task is expected to
 finish soon.
 
@@ -77,7 +77,7 @@ in the agent's loose-ends; handle it on a future turn.
 - `force: true` — SIGKILL.
 
 If a SIGINT'd task doesn't exit, call `kill` again with `force: true`.
-A still-pending task is cancelled before it starts. The task ends as
+The daemon cancels a still-pending task before it starts. The task ends as
 `killed` and surfaces in the loose-ends like any completion.
 
 Exposed as `mcp__bash__kill`.
@@ -86,7 +86,7 @@ Exposed as `mcp__bash__kill`.
 
 `run` and `status` live in the `bash` MCP server, not `hyperhive`. The
 tool names in claude are `mcp__bash__run` and `mcp__bash__status`.
-The `Bash` built-in tool is blocked — all shell execution goes through
+hyperhive blocks the `Bash` built-in tool — all shell execution goes through
 this structured path so tasks get task-id tracking and structured output.
 
 ## Architecture
@@ -109,8 +109,8 @@ When a bash task changes state, `hive-bash-daemon` upserts a single keyed
 todo (`key = task id`) on the harness's in-agent socket (`HIVE_AGENT_SOCKET`)
 — "running" at start, then the completion summary when it finishes. The
 summary change signals the harness turn loop directly (in-process, no broker
-round-trip), so the agent is driven a turn to handle it via `get_loose_ends`,
-then clears the todo with `cancel_loose_end(kind: "todo", id: N)` (dials the
+round-trip), so the harness drives a turn for the agent to handle it via
+`get_loose_ends`, then clears the todo with `cancel_loose_end(kind: "todo", id: N)` (dials the
 in-container socket directly — no bash task involved, so clearing doesn't
 spawn another todo; see #2639). Same mechanism the matrix daemon uses for
 unread rooms. An inline `wait_seconds` / `status` observation that already
@@ -123,5 +123,5 @@ loose-end follows.
 `tools()` returns `["run", "status"]` which the harness expands to
 `mcp__hyperhive__run` / `mcp__hyperhive__status` — tools that don't
 exist in the hyperhive MCP server (dead entries). Removing `execution`
-from an agent's groups has no effect on bash availability. Bash is
-registered separately via the `extraMcpServers` path described above.
+from an agent's groups has no effect on bash availability.
+`nix/agent-modules/mcp.nix` registers Bash separately via the `extraMcpServers` path described above.