docs: drop statements about absent things, state current behaviour

docs/tools/bash.md

@@ -129,8 +129,7 @@ loose-end follows.
 controls whether the `bash` MCP server reaches the agent's claude
 config at all, suppressing every `mcp__bash__*` tool
 when absent — not just leaving them unused. Its own `tools()` returns
-`&[]`: `mcp__bash__run`/`status`/`kill` belong to a
-different, out-of-process MCP server (`bash`, not `hyperhive`), so they
-aren't entries in the `mcp__hyperhive__*` allowlist `tools()`
-builds. Removing `execution` from an
-agent's groups **does** remove bash availability.
+`&[]`: `mcp__bash__run`/`status`/`kill` live on the separate `bash` MCP
+server that `extra_server_required_group` gates, not on the
+`mcp__hyperhive__*` allowlist `tools()` builds. Removing `execution`
+from an agent's groups **does** remove bash availability.

docs/tools/forge.md

@@ -281,9 +281,7 @@ to discover valid label names before triaging or to audit the label set.
   falling back. `--job` selects the job (0-based, default 0);
   `--attempt` picks the run attempt for the durable path (default 1;
   re-runs increment it). `--json` wraps the output.
-- `ci-rerun` re-runs CI without pushing an empty commit. Forgejo has no token-usable
-  REST endpoint to re-run an _existing_ run (the run-page rerun buttons
-  are CSRF-gated web routes a token POST 404s), so this dispatches a
+- `ci-rerun` re-runs CI without pushing an empty commit: it dispatches a
   **fresh** run of the workflow via the workflow-dispatch API
   (`POST …/actions/workflows/<workflow>/dispatches {"ref":"<branch>"}`).
   Resolve the branch with `--run <n>` (the same run number `ci-log` /

docs/tools/subagent.md

@@ -101,8 +101,7 @@ there is no such identity to hold a file open for, so the daemon omits
 `--append-system-prompt-file` altogether rather than pointing it at
 anything task-shaped.
 
-⚠️ This applies to every dispatch, not just role-bearing ones — no agent
-ships roles yet, so today it's the only path in real use.
+⚠️ This applies to every dispatch, not just role-bearing ones.
 
 ### A role with no file refuses the call
 
@@ -235,9 +234,8 @@ early exit — and on this box both land inside a second, so a `continue`
 that works answers about as fast as it did before. A five-second cap
 bounds the one case neither covers: a child that neither speaks nor
 exits, reported as started, with the end-of-turn todo left to say how it
-goes. That todo still carries every failure that happens later in the
-turn; it doesn't repeat the miss `continue` already handed the caller
-directly.
+goes. That todo carries every failure that happens later in the turn,
+starting after the miss `continue` already handed the caller directly.
 
 ## A killed turn
 
@@ -353,8 +351,7 @@ Everything else in claude's built-in set is absent, in particular the
 tools that let a session act outside the run for which it began: peer and
 operator messaging, nested agents (including the stop verb, which takes
 an _agent_ id rather than a session), schedule and webhook creation, and
-worktree switching. `--allowedTools` would not achieve this exclusion on
-its own: it approves prompts in advance rather than restricting anything.
+worktree switching.
 
 One rule worth knowing before editing any of this: **the daemon never
 emits an empty `--tools` value**, and asserts rather than doing so. Not