remove the list_containers and request_update_meta_inputs MCP tools

Both agent-facing tools go away end to end, with no replacement. This is
an intentional capability removal: agents can no longer enumerate their
own subtree, and can no longer queue a meta-flake input bump.

The system prompt and docs/tools/lifecycle.md land in this same commit
on purpose. A tool named in the prompt but absent from the server makes
agents confidently call something that doesn't exist, and the failure
then surfaces far from its cause.

Removed:

- MCP registrations and bodies (hive-agent-mcp), plus the now-unused
  UpdateMetaInputsArgs.
- Wire variants Request::ListDescendants,
  Request::RequestUpdateMetaInputs and Response::Containers, plus
  ContainerInfo, whose only consumer was that response.
- hive-c0re's handle_list_descendants (its whole module) and
  handle_request_update_meta_inputs, the two dispatch arms, and the
  require_group(agent, "approvals", ...) gate on the meta-inputs verb.
- The stream_enrich emoji entry and argument formatter.
- docs/tools/lifecycle.md (both tools it documented are gone), its two
  referrers, the tool-group tables and the agent-hierarchy prose.

Tool groups are kept, deliberately. ToolGroup::Lifecycle listed exactly
one tool and now lists none — it is vestigial, but the variant stays so
existing meta/capabilities.json grants still parse; retiring it is a
separate decision. ToolGroup::Approvals also listed exactly one tool,
but the group is NOT dead: check_can_cancel_approval still gates
cancel_loose_end's approval-cancel arm on it server-side.

ApprovalKind::UpdateMetaInputs stays too. Nothing in production code
produces it any more, but pre-existing approval rows may still carry it,
and the operator's own path to a meta update is unaffected — the
dashboard's POST /api/meta-update inserts the meta_update job directly,
bypassing approvals entirely.

The two format_ack tests in hive-agent-mcp that named
request_update_meta_inputs were only using it as a label string while
exercising the generic OkWarn/Ok renderer, so they are retargeted to a
surviving tool rather than deleted.

Note hive-c0re's priv_client::list_containers is a different thing (the
host-side privileged container listing behind hive-priv) and is
untouched.

Closes #4591

hive-agent/prompts/system.md

@@ -4,8 +4,6 @@ Tools (hyperhive surface). Full signature + behavior for each comes from the too
 
 - **Inbox / messaging** (always available): `mcp__hyperhive__recv`, `mcp__hyperhive__ack_until`, `mcp__hyperhive__send`, `mcp__hyperhive__get_loose_ends`, `mcp__hyperhive__cancel_loose_end`, `mcp__hyperhive__mark_todos_done`, `mcp__hyperhive__remind`, `mcp__hyperhive__set_status`, `mcp__hyperhive__get_agent_meta`. One habit worth internalizing beyond the tool descriptions themselves: prefer ending the turn over repeatedly polling `recv` when idle (only turn-boundaries observe in-container todo wakes — bash-task completions, matrix unread, forge activity — and ending the turn is also your checkpoint). For a large todo backlog (`get_loose_ends` caps at 40 rows), clear reviewed ids in bulk with `mark_todos_done` rather than cancelling one at a time — there's no blind range-clear, only ids you've actually looked at.
 - **Extra MCP tools** (some agents only): `mcp__<server>__<tool>` — agent-specific (matrix client, scraper, db connector, etc.) declared in your `agent.nix` under `hyperhive.extraMcpServers`. First-class tools, already operator-approved at deploy time.
-- **Lifecycle** (_requires `lifecycle` tool group_, your own subtree — children, their children, and so on down, no approval needed): `list_containers`.
-- **Approvals** (_requires `approvals` tool group_, queues an operator approval): `request_update_meta_inputs`.
 - **Scheduling** (_requires `scheduling` tool group_): `request_schedule_prompt` (queues an approval), `cancel_schedule`, `fire_schedule_now`, `edit_schedule`, `list_schedules` (these four don't need approval — you can manage schedules you own or that a sub-agent in your subtree owns).
 - **Diagnostics**: `get_host_journal` (_requires `read_host_journal` capability_).
 
@@ -19,7 +17,7 @@ Messages from sender `system` are hyperhive helper events (JSON body, `event` fi
 
 - `needs_update` — agent's flake rev is stale. Ask the operator to rebuild it.
 - `container_crash` — ask the operator to start it again; if it keeps crashing, say so with what you saw.
-- `approval_resolved` — one of your own submitted approvals (`request_update_meta_inputs`, a scheduled prompt, a config PR, …) was approved, denied, or failed; the body carries the resolution.
+- `approval_resolved` — one of your own submitted approvals (a scheduled prompt, a config PR, …) was approved, denied, or failed; the body carries the resolution.
 
 Lifecycle notices that don't need an immediate turn — a new agent spawned, a container rebuilt/killed/destroyed, or its login state changing — surface as todos instead of messages now. Call `get_loose_ends` to see them.
 

hive-agent/src/stream_enrich.rs

@@ -498,8 +498,7 @@ fn tool_icon(name: &str) -> &'static str {
         "mcp__hyperhive__cancel_loose_end" => "✂️",
         "mcp__hyperhive__ack_until" => "✅",
         "mcp__hyperhive__get_agent_meta" => "ℹ️",
-        "mcp__hyperhive__list_containers"
-        | "mcp__matrix__list_rooms"
+        "mcp__matrix__list_rooms"
         | "mcp__matrix__list_room_members"
         | "mcp__matrix__list_invites" => "📋",
         "mcp__hyperhive__get_host_journal" => "📜",
@@ -666,8 +665,7 @@ fn fmt_hyperhive_tool(name: &str, short: &str, input: &Value) -> String {
             }
         }
         "mcp__hyperhive__remind" => fmt_hyperhive_remind(short, input),
-        "mcp__hyperhive__request_update_meta_inputs"
-        | "mcp__hyperhive__list_schedules"
+        "mcp__hyperhive__list_schedules"
         | "mcp__hyperhive__cancel_schedule"
         | "mcp__hyperhive__fire_schedule_now"
         | "mcp__hyperhive__edit_schedule"
@@ -792,17 +790,6 @@ fn fmt_hyperhive_edit_schedule(short: &str, input: &Value) -> String {
 /// Schedule-management hyperhive tools (list/cancel/fire/edit/request).
 fn fmt_hyperhive_schedule_tool(name: &str, short: &str, input: &Value) -> String {
     match name {
-        "mcp__hyperhive__request_update_meta_inputs" => {
-            let ins = match input.get("inputs").and_then(Value::as_array) {
-                Some(arr) if !arr.is_empty() => {
-                    let names: Vec<&str> = arr.iter().filter_map(Value::as_str).take(4).collect();
-                    let tail = if arr.len() > 4 { ", …" } else { "" };
-                    format!("[{}{}]", names.join(", "), tail)
-                }
-                _ => "all".to_owned(),
-            };
-            format!("{short} {ins}")
-        }
         "mcp__hyperhive__list_schedules" => format!("{short}()"),
         "mcp__hyperhive__cancel_schedule" => {
             let id = input