scheduled prompts: fire-now operator + manager surfaces (closes #467)

hive-ag3nt/prompts/manager.md

@@ -13,6 +13,7 @@ Tools (hyperhive surface):
 - `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__request_schedule_prompt(targets, body, first_fire_at_unix, interval_seconds?, description?)` — queue an approval for the operator to add a scheduled prompt. On approve hive-c0re inserts a schedule row and the worker fans `body` out to each agent in `targets` at `first_fire_at_unix` (recurring every `interval_seconds` if set, one-shot when absent). Even self-targeted schedules go through approval — the existing `remind` tool stays the quick no-approval self-wake path. Catch-up clamp: long downtime fires ONCE per recurring row on resume (skipped count surfaces in per-target `last_result`), not N stacked pulses.
 - `mcp__hyperhive__cancel_schedule(id, targets?)` — cancel a schedule. Omit `targets` / pass empty to cancel the whole schedule; pass a list to cancel just those recipients (the schedule keeps firing for any remaining active targets, auto-cancels when every target is gone). Authorization: you can cancel schedules you own OR any owned by a sub-agent in your subtree per topology.json.
+- `mcp__hyperhive__fire_schedule_now(id)` — fire a scheduled prompt out of band. Runs the per-target fan-out once immediately. Recurring schedules keep their cadence intact (the manual fire is additive); one-shot schedules are CONSUMED by the manual fire (cancelled afterwards). Same authorization as `cancel_schedule`.
 - `mcp__hyperhive__list_schedules()` — snapshot every schedule in the queue (active + cancelled-but-not-reaped). Returns id, owner, body, target set with per-target `last_fired_at` + `last_result`, `next_fire_at_unix`, recurring `interval_seconds`. Use to look up an id before cancelling, or to audit upcoming wake-ups across the swarm.
 - `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__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

@@ -959,6 +959,14 @@ pub struct RequestSchedulePromptArgs {
     pub description: Option<String>,
 }
 
+#[derive(Debug, serde::Deserialize, schemars::JsonSchema)]
+pub struct FireScheduleNowArgs {
+    /// Schedule id to fire out of band. Get this from a prior
+    /// `list_schedules` call or the approval-resolved event for
+    /// the originating `request_schedule_prompt`.
+    pub id: i64,
+}
+
 #[derive(Debug, serde::Deserialize, schemars::JsonSchema)]
 pub struct CancelScheduleArgs {
     /// Schedule id from a prior `list_schedules` call or the
@@ -1269,6 +1277,33 @@ impl ManagerServer {
         .await
     }
 
+    #[tool(
+        description = "Fire a scheduled prompt out of band — runs the per-target fan-out \
+        once immediately without disturbing the schedule's cadence. Recurring schedules \
+        keep their next_fire_at unchanged (the manual fire is additive). One-shot \
+        schedules are CONSUMED by the manual fire (cancelled afterwards): the operator's \
+        intent on a one-shot is 'send this now, the scheduled time was wrong'. \n\n\
+        Authorization mirrors `cancel_schedule`: you can fire your own schedules + any \
+        owned by a sub-agent in your subtree per topology.json."
+    )]
+    async fn fire_schedule_now(
+        &self,
+        Parameters(args): Parameters<FireScheduleNowArgs>,
+    ) -> String {
+        let log = format!("{args:?}");
+        run_tool_envelope("fire_schedule_now", log, async move {
+            let id = args.id;
+            let (resp, retries) = self
+                .dispatch(hive_sh4re::ManagerRequest::FireScheduleNow { id })
+                .await;
+            annotate_retries(
+                format_ack(resp, "fire_schedule_now", format!("fired #{id} now")),
+                retries,
+            )
+        })
+        .await
+    }
+
     #[tool(
         description = "Cancel a scheduled prompt. With no `targets` field, cancels the \
         whole schedule (all recipients flipped). With a non-empty `targets` list, cancels \