docs: fix write-good.So/ThereIs/Weasel lint findings

Fixes the "obvious ones first" slice of #4042 (mara: do the obvious
ones first) -- 81 hits across write-good.So, write-good.ThereIs, and
write-good.Weasel, all in docs/. Each is a genuine sentence rewrite
(lead with the real subject instead of "There is/are", drop a
sentence-initial "So ", replace a vague intensifier), not a blind
regex substitution -- read every hit in its real file context before
touching it.

3 of the 81 hits were in CI-generated CLI docs (docs/tools/{hivectl,
swarmctl,forge}-cli.md) -- fixed at the clap #[arg(...)]/doc-comment
source in hivectl/src/cli.rs, swarmctl/src/main.rs, and
hive-forge/src/verbs/repo_add_collaborator.rs, then regenerated via
each crate's `markdown-docs` subcommand so CI's freshness check stays
green.

Verified: fresh vale re-run shows 0 remaining So/ThereIs/Weasel hits
and no new hits introduced (983->982, exactly the one incidental fix
this pass also picked up at docs/scheduler/observability.md:48).
cargo fmt --check and clippy clean on the three touched crates.

Remaining write-good backlog (Passive: 726, TooWordy: 207) is
judgment-heavy and left for a follow-up slice of #4042, not bulk-
rewritten here.

docs/agent-lifecycle/agent-hierarchy.md

@@ -178,8 +178,8 @@ nspawn agent. Open questions, not yet wired:
 
 One harness serve binary (`hive-agent`, with its `hive-agent-mcp`
 sibling), one shared `nix/agent-modules/` tree, one service unit
-(`systemd.services.hive-agent`) for all agents. There is no separate
-manager service name or role distinction in the harness — privilege
+(`systemd.services.hive-agent`) for all agents. No separate manager
+service name or role distinction exists in the harness — privilege
 differences live server-side in the broker socket (which tool groups
 and manager-surface calls each agent receives).
 

docs/agent-lifecycle/approvals.md

@@ -56,7 +56,7 @@ flow.
 
 Config changes flow through a **forge pull request** on the agent's
 `agent-configs/<name>` repo — the same surface agents use for code PRs.
-There is no bespoke MCP tool for config changes: opening the PR IS the
+No bespoke MCP tool exists for config changes: opening the PR IS the
 request.
 
 1. The submitting agent (the child's parent, holding the `approvals`
@@ -349,7 +349,7 @@ per-hive config — is the idempotent reconciler called by `spawn`,
 `destroy`, `rebuild`, and the startup migration. Renders `flake.nix`
 from the agent list; if it differs from disk, runs
 `nix flake lock` + commits as `regenerate meta flake` (or
-`seed meta from N agent(s)` on the very first call).
+`seed meta from N agent(s)` on the first call).
 
 The root agent has `/meta` RO-bound inside its container:
 `git -C /meta log --oneline` is the swarm-wide deploy log,
@@ -499,8 +499,8 @@ current config — not an editing surface.
 An agent with the `approvals` tool group submits a change the same way
 any other change is made: **clone the child's config repo from the
 forge into its own state dir, commit on a branch, open a PR**, and let
-the operator review and approve it. There is deliberately no second,
-mount-shaped path that reaches the same file without the review.
+the operator review and approve it. By design, no second, mount-shaped
+path reaches the same file without the review.
 
 Agents holding the `can_manage_top_level_agents` topology role (see
 `hive-c0re/src/agent_config/topology.rs`) get additional host-side
@@ -593,8 +593,8 @@ updates the root agent itself.
 The system prompt (`hive-agent/prompts/system.md`, rendered by
 `hive-agent/src/prompt.rs`) is the **same for every agent**; what
 varies is which MCP tools are surfaced (gated by tool groups and
-capabilities in `agent.nix`). There is no `role:manager` block that
-renders only for the root agent. The root agent's approval-gating
+capabilities in `agent.nix`). No `role:manager` block renders only
+for the root agent. The root agent's approval-gating
 behaviour comes from its CLAUDE.md / agent-specific instructions, not
 the system prompt template.
 

docs/agent-lifecycle/persistence.md

@@ -72,7 +72,7 @@ power-intent registry:
   last_fired_at_unix / last_result`. `ON DELETE CASCADE` from
   `scheduled_prompts(id)` — requires `PRAGMA foreign_keys = ON`
   per connection (set at open).
-- `agent_power` — one tiny row per agent: `agent PK / wanted (up |
+- `agent_power` — one row per agent: `agent PK / wanted (up |
   offline) / updated_at`, owned by `hive-c0re/src/stores/power.rs`.
   This is the durable power *intent* the job queue reconciles the
   observed container state against; intent survives hive-c0re
@@ -158,7 +158,7 @@ host-side). Best-effort and created on first write
 (`CREATE TABLE IF NOT EXISTS`), so it's absent until a bash
 task runs.
 
-turn-stats.sqlite has **no vacuum** — it's one tiny row per turn
+turn-stats.sqlite has **no vacuum** — it's one small row per turn
 (~hundreds of KB even over months), read directly by the `/stats` page
 and the hive-wide stats view, so pruning it would only lose trend
 history for no space gain.
@@ -409,7 +409,7 @@ Contents:
 
 The root agent has the meta dir RO-mounted at `/meta/`.
 
-There is no longer a `.meta-migration-done` marker: the
+The `.meta-migration-done` marker no longer exists: the
 one-shot container repoint it guarded has been removed, since
 containers are rendered onto `meta#<n>` at creation. A stale
 marker file left over from an older hive is inert and can be
@@ -516,7 +516,7 @@ marker-guarded so the substantive moves only happen once per
 container lifetime:
 
 1. **`${homeDir}` exists with the right ownership** — covers the
-   very first boot before `useradd`'s `createHome` has had a
+   the first boot before `useradd`'s `createHome` has had a
    chance to chown. Also re-applies on every rebuild in case the
    meta-flake's per-agent name evolves (rare).
 2. **Migrate any leftover `/root/.claude` content into