mcp: remove the restart/kill/start/update/get_logs agent verbs

Container lifecycle from inside an agent goes away: an agent no longer
starts, stops, restarts or rebuilds a container in its subtree, and no
longer reads another container's journal. Those are operator actions —
the dashboard and hivectl keep their own paths to the same job-queue
and hive-priv plumbing, which is why none of that machinery is removed
here, only the five MCP verbs and what they alone reached.

What went with them: the `Request` variants and `Response::Logs` on the
agent socket, the five tool definitions and their arg structs, the four
lifecycle handlers plus `handle_get_logs`, and `require_descendant` —
the topology guard those five were the only remaining callers of.
`ToolGroup::Diagnostics` goes too: `get_logs` was its only tool, so it
would otherwise be a grantable group that grants nothing. `lifecycle`
stays, now carrying `list_containers` alone.

An agent that gets a `needs_update` or `container_crash` helper event
has no remedy of its own left, so the system prompt and the docs now
send it to the operator instead of to a tool that no longer exists.

Refs #4480

docs/tools/README.md

@@ -40,12 +40,10 @@ debug agent behavior.
 - **[forge-cli](forge-cli.md)** — the exhaustive, autogenerated
   flag-by-flag reference for `hive-forge`, kept in lockstep with the
   binary by CI the same way `hivectl-cli.md` is.
-- **[lifecycle](lifecycle.md)** — kill/start/restart/update for the
-  agents in a caller's own subtree, plus the approval-gated
-  config-change tools.
+- **[lifecycle](lifecycle.md)** — listing the agents in a caller's own
+  subtree, plus the approval-gated config-change tools.
 - **[matrix](matrix.md)** — the matrix MCP tool surface
   (`mcp__matrix__*`) for agents with a matrix account, multiple
   accounts per agent, and declaring extra MCP servers generally.
 - **[scheduling](scheduling.md)** — scheduled prompts (operator
-  approval required) and the diagnostics tools (`get_logs`,
-  `get_host_journal`).
+  approval required) and the `get_host_journal` diagnostics tool.

docs/tools/lifecycle.md

@@ -11,25 +11,6 @@ everything sits under it.
 
 No operator approval required. The caller's own subtree.
 
-### `kill(name)`
-
-Graceful stop. Container state is preserved; recreating the agent
-reuses prior config and credentials.
-
-### `start(name)`
-
-Start a stopped sub-agent.
-
-### `restart(name)`
-
-Stop + start in one call.
-
-### `update(name)`
-
-Rebuild: re-applies the current hyperhive flake + `agent.nix`,
-then restarts. Idempotent — safe to call repeatedly. Used in response
-to `needs_update` system events.
-
 ### `list_containers()`
 
 List the caller's whole **subtree** with running status — children,
@@ -60,16 +41,15 @@ flake. Pass specific input names (for example `["bitburner-agent"]`) or omit
 / pass `[]` for all inputs. Returns immediately; the lock update runs
 on operator approval.
 
-**Doesn't** trigger container rebuilds — call `update(name)` on affected
+**Doesn't** trigger container rebuilds — the operator rebuilds affected
 agents after the approval resolves.
 
 ## Boundary summary
 
-| Operation                               | Requires approval? | Scope                        |
-| --------------------------------------- | ------------------ | ---------------------------- |
-| `kill` / `start` / `restart` / `update` | No                 | Own subtree                  |
-| `list_containers`                       | No                 | Own subtree, caller included |
-| `request_update_meta_inputs`            | Yes (MetaUpdate)   | Meta flake (global)          |
+| Operation                    | Requires approval? | Scope                        |
+| ---------------------------- | ------------------ | ---------------------------- |
+| `list_containers`            | No                 | Own subtree, caller included |
+| `request_update_meta_inputs` | Yes (MetaUpdate)   | Meta flake (global)          |
 
 ## See also
 

docs/tools/scheduling.md

@@ -61,17 +61,6 @@ and `last_result`, `next_fire_at_unix`, `interval_seconds`. Use to
 look up an id before cancelling, or to audit upcoming wake-ups in
 your subtree.
 
-## `diagnostics` tool group
-
-### `get_logs(agent, lines?)`
-
-Fetch recent journal lines for a sub-agent container. Useful for
-diagnosing MCP-registration failures, startup crashes, plugin install
-errors, or any harness issue you can't see from inside the container.
-
-Pass the plain logical agent name (for example `"gui"`) — hive-c0re resolves
-the machine name (`h-<name>`). `lines` defaults to 50, host-capped at 500.
-
 ## `read_host_journal` capability
 
 Capability-gated (not a tool group) — the operator enables it in the