docs(agents): drop change-log section and temporal wording

docs/turn-loop/mcp.md

@@ -14,7 +14,7 @@ entry (`type = "stdio" | "http"`, default `"stdio"`): `matrix` and
 (`hive-matrix-daemon`, `hive-subagent-daemon`), same reasoning as the
 built-in surface and `bash`'s `hive-bash-daemon`. The GUI bridge
 (`screen`, gated on `services.hyperhive.agent.gui.enable`) is the one
-entry that still takes the schema's stdio default — it spawns
+entry on the schema's stdio default — it spawns
 `hive-screen-mcp` fresh each turn. The server name is `hyperhive`, so
 the tools land in claude as
 `mcp__hyperhive__<tool>`. Each entry also has an `availableToSubagents`
@@ -62,8 +62,8 @@ are opt-in via the P3RM1SS10NS tab.
 
 **System messages** (from sender `system`): the broker delivers
 `hive_sh4re::manager::HelperEvent` (three variants: `ApprovalResolved`,
-`ContainerCrash`, `NeedsUpdate` — the last declared but constructed by
-no call site today) as regular inbox messages (same `recv`
+`ContainerCrash`, `NeedsUpdate` — declared, but no call site
+constructs it) as regular inbox messages (same `recv`
 path; body is a JSON object with an `event` discriminant field).
 `ApprovalResolved` goes to whichever agent actually submitted the
 approval (`Coordinator::notify_submitter`, looked up from the
@@ -73,7 +73,7 @@ recorded submitter falls back to the manager, `ruth`).
 hardcoded — `hive-c0re/src/workers/crash_watch.rs`). A `MergeConfigPr`
 approval's rebuild additionally pushes a `rebuilt:<agent>` todo to that
 same submitter (`Coordinator::push_todo_submitter`, `subsystem =
-"core"`), which still wakes a turn (the todo-wake path — see [Turn
+"core"`), which wakes a turn (the todo-wake path — see [Turn
 outcomes](README.md#turn-outcomes)) via a generic "call
 `get_loose_ends`" prompt rather than the event body itself. Lifecycle
 transitions the job-queue scheduler or crash watcher drive directly —
@@ -91,8 +91,7 @@ at_unix_timestamp?)`.
   bash, forge, or any user-configured MCP server), an undelivered-inbox
   count, and unread matrix notifications; `approval` rows only appear
   when the caller is the manager (`ruth`) — sub-agents don't submit
-  approvals. Always the caller's own rows — there is no way to target
-  another agent. Full per-variant wire shape in
+  approvals. Always the caller's own rows. Full per-variant wire shape in
   [`docs/process/conventions.md` § Loose-ends wire
   shape](../process/conventions.md#loose-ends-wire-shape).
 - `cancel_loose_end` — hard-delete a `reminder`, cancel a pending
@@ -138,8 +137,7 @@ hive_name?, swarm_name?, matrix_accounts? }`. `matrix_accounts` is a
   broker — see `hive-agent/src/todo_server.rs`.
 - `mark_todos_done(ids)` — bulk-clear specific loose-ends-v2 todo rows
   by id in one call, instead of `cancel_loose_end`ing each one.
-  List-based, not range-based (no `ack_until`-style "clear below id
-  N"): pass the ids `get_loose_ends` actually showed you reviewed;
+  List-based: pass the ids `get_loose_ends` actually showed you reviewed;
   unknown or already-done ids are silently skipped. Dials the same
   in-agent todo socket as `cancel_loose_end`'s `todo` kind.
 
@@ -149,16 +147,16 @@ hive_name?, swarm_name?, matrix_accounts? }`. `matrix_accounts` is a
   [`docs/tools/bash.md`](../tools/bash.md).
 - **Subagent spawning** — nested sessions on the agent's own runtime
   (claude or ACP, via `hive-runtime`) as background tasks, shipped
-  default-on like bash execution (no tool group gates it yet). See
+  default-on like bash execution; no tool group gates it. See
   [`docs/tools/subagent.md`](../tools/subagent.md).
-- **Lifecycle + config** (`lifecycle`, `approvals`) — neither group
-  carries an MCP tool. `approvals` survives as a server-side gate on
-  `cancel_loose_end`'s approval-cancel arm; `lifecycle` gates nothing.
+- **Lifecycle + config** (`lifecycle`, `approvals`) — `approvals`
+  gates `cancel_loose_end`'s approval-cancel arm server-side;
+  `lifecycle` gates nothing.
   Config changes go through a forge PR on `agent-configs/<name>` — see
   [`docs/agent-lifecycle/approvals.md`](../agent-lifecycle/approvals.md).
 - **Scheduling** (`scheduling`) — scheduled prompts. See
   [`docs/tools/scheduling.md`](../tools/scheduling.md).
-- **Forge repos** (`forge`) — carries no MCP tool; `forge` gates nothing.
+- **Forge repos** (`forge`) — gates nothing.
 - **Web egress** (`web_tools`) — enables Claude's built-in `WebFetch`
   and `WebSearch` tools (not MCP tools; added directly to the
   `--allowedTools` list). Off by default; add the group in the
@@ -177,20 +175,17 @@ The built-in producers (matrix, bash, forge) upsert a todo on the
 harness's in-agent socket (`HIVE_AGENT_SOCKET`, `UpsertTodo` — see
 [`docs/tools/bash.md` § Completion as a todo
 (loose-ends v2)](../tools/bash.md#completion-as-a-todo-loose-ends-v2)
-for the full upsert/signal/clear mechanism); none dials a direct
-wake: a new or changed summary
+for the full upsert/signal/clear mechanism): a new or changed summary
 makes the harness signal its own turn loop, with no hive-c0re
 round-trip. An external MCP server (or any other in-container process)
-can push its own todo the same way — `subsystem` is a plain string,
-not a closed set.
+can push its own todo the same way — `subsystem` is any string.
 
-The host-served per-agent socket at `/run/hive/mcp.sock` still carries
-a lower-level `Wake` request (`hive_core_agent_sock::Request::Wake {
+The host-served per-agent socket at `/run/hive/mcp.sock` carries a
+lower-level `Wake` request (`hive_core_agent_sock::Request::Wake {
 from, body }` — JSON-line, `{"cmd":"wake","from":"matrix","body":"new dm
 from @alice"}\n`) that drops the body straight into the broker inbox as
 `{from:<label>, to:<agent>, body}`, bypassing the todo layer entirely.
-`hive-c0re` still handles it, but no built-in producer
-calls it today. Identity = socket: anything that can connect to
+`hive-c0re` handles it; matrix, bash and forge don't call it. Identity = socket: anything that can connect to
 `/run/hive/mcp.sock` is implicitly trusted to inject one — the
 bind-mount is the agent's own container only.