update_meta_inputs: require operator approval, rename to request_update_meta_inputs

hive-ag3nt/prompts/manager.md

@@ -10,7 +10,7 @@ Tools (hyperhive surface):
 - `mcp__hyperhive__start(name)` — start a stopped sub-agent. No approval required.
 - `mcp__hyperhive__restart(name)` — stop + start a sub-agent. No approval required.
 - `mcp__hyperhive__update(name)` — rebuild a sub-agent (re-applies the current hyperhive flake + agent.nix, restarts the container). No approval required — idempotent. Use when you receive a `needs_update` system event.
-- `mcp__hyperhive__update_meta_inputs(inputs?)` — run `nix flake update [inputs...]` on the meta flake and commit the lock changes. Pass specific input names (e.g. `["bitburner-agent"]`) to update just those, or omit / pass `[]` to update everything. Blocks until complete. Does NOT trigger rebuilds — call `update(name)` on affected agents afterward.
+- `mcp__hyperhive__request_update_meta_inputs(inputs?, description?)` — queue an approval for the operator to run `nix flake update [inputs...]` on the meta flake. Pass specific input names (e.g. `["bitburner-agent"]`) or omit / pass `[]` for all inputs. Returns immediately; lock update runs on operator approval. Does NOT trigger rebuilds — call `update(name)` on affected agents after approval resolves.
 - `mcp__hyperhive__get_logs(agent, lines?)` — fetch recent journal lines for a sub-agent container. Use to diagnose MCP-server registration failures, startup crashes, or harness issues you can't see from inside. Pass the plain logical agent name; `lines` defaults to 50 (capped at 500).
 - `mcp__hyperhive__request_apply_commit(agent, commit_ref, description?)` — submit a config change for any agent (`hm1nd` for self) for operator approval. Pass an optional `description` and it appears on the dashboard approval card so the operator knows what changed without opening the diff. At submit time hive-c0re fetches your commit into the agent's applied repo and pins it as `proposal/<id>`; from that moment your proposed-side commit can be amended or force-pushed freely without changing what the operator will build.
 - `mcp__hyperhive__ask(question, options?, multi?, ttl_seconds?, to?)` — surface a structured question to the operator (default, or `to: "operator"`) OR a sub-agent (`to: "<agent-name>"`). Returns immediately with a question id; the answer arrives later as a system `question_answered { id, question, answer, answerer }` event in your inbox. Options are advisory: the dashboard always lets the operator type a free-text answer in addition. Set `multi: true` to render options as checkboxes (operator can pick multiple); the answer comes back as `, `-separated. Set `ttl_seconds` to auto-cancel after a deadline (capped at 6h server-side) — on expiry the answer is `[expired]` and `answerer` is `"ttl-watchdog"`. Do not poll inside the same turn — finish the current work and react when the event lands.

hive-ag3nt/src/mcp.rs

@@ -813,6 +813,9 @@ pub struct UpdateMetaInputsArgs {
     /// Pass an empty list to update ALL inputs.
     #[serde(default)]
     pub inputs: Vec<String>,
+    /// Optional description shown on the dashboard approval card.
+    #[serde(default)]
+    pub description: Option<String>,
 }
 
 #[derive(Debug, serde::Deserialize, schemars::JsonSchema)]
@@ -1031,31 +1034,36 @@ impl ManagerServer {
     }
 
     #[tool(
-        description = "Run `nix flake update` on the meta flake and commit the resulting \
-        `flake.lock` changes. Pass specific input names to update only those inputs \
-        (e.g. `[\"bitburner-agent\"]`), or pass an empty list to update ALL inputs. \
-        Blocks until the lock step completes (~30-120s depending on download size). \
+        description = "Queue an approval for the operator to run `nix flake update` on the \
+        meta flake and commit the resulting lock changes. Pass specific input names to update \
+        only those inputs (e.g. `[\"bitburner-agent\"]`), or pass an empty list to update ALL \
+        inputs. Returns immediately — the lock update runs when the operator approves. \
         Does NOT trigger container rebuilds — call `update` on each affected agent \
-        separately after the lock settles."
+        separately after the approval resolves."
     )]
-    async fn update_meta_inputs(
+    async fn request_update_meta_inputs(
         &self,
         Parameters(args): Parameters<UpdateMetaInputsArgs>,
     ) -> String {
         let log = format!("{args:?}");
-        run_tool_envelope("update_meta_inputs", log, async move {
+        run_tool_envelope("request_update_meta_inputs", log, async move {
             let label = if args.inputs.is_empty() {
                 "all inputs".to_string()
             } else {
                 args.inputs.join(", ")
             };
             let (resp, retries) = self
-                .dispatch(hive_sh4re::ManagerRequest::UpdateMetaInputs {
+                .dispatch(hive_sh4re::ManagerRequest::RequestUpdateMetaInputs {
                     inputs: args.inputs,
+                    description: args.description,
                 })
                 .await;
             annotate_retries(
-                format_ack(resp, "update_meta_inputs", format!("lock updated: {label}")),
+                format_ack(
+                    resp,
+                    "request_update_meta_inputs",
+                    format!("approval queued: {label}"),
+                ),
                 retries,
             )
         })