diff --git a/docs/turn-loop.md b/docs/turn-loop.md
index d5d12d41..52b32eb9 100644
--- a/docs/turn-loop.md
+++ b/docs/turn-loop.md
@@ -347,6 +347,11 @@ meta's.
   to cancel just those recipients (auto-cancels when every target
   is removed). Authorization: manager can cancel schedules it owns
   or any owned by a sub-agent in its topology subtree.
+- `fire_schedule_now(id)` — fire a scheduled prompt out of band.
+  Runs the per-target fan-out once immediately. Recurring schedules
+  keep their cadence (the manual fire is additive); one-shot
+  schedules are consumed by the fire and cancelled afterwards. Same
+  authorization rules as `cancel_schedule`.
 - `list_schedules()` — snapshot every schedule (active +
   cancelled-but-not-reaped): id, owner, body, per-target
   `last_fired_at` + `last_result`, `next_fire_at_unix`,
diff --git a/docs/web-ui.md b/docs/web-ui.md
index dd681aca..cb52dcf1 100644
--- a/docs/web-ui.md
+++ b/docs/web-ui.md
@@ -447,6 +447,11 @@ not ours.
   the sentinel `[cancelled]`. Same code path as a real answer.
 - `POST /request-spawn` — queue a Spawn approval.
 - `POST /update-all` — rebuild every stale container.
+- `POST /api/rebuild-queue/{id}/cancel` — drop a `Queued` entry
+  (#447). Refuses `Running` / terminal-state entries (in-flight
+  rebuilds can't be safely interrupted). Always 200; body is
+  `{"cancelled": true}` on a successful flip or
+  `{"cancelled": false}` when the entry was not in `Queued` state.
 - `POST /op-send` (`to=<name>`, `body=<text>`) — drop an
   operator-authored message into `<name>`'s inbox. `to=*` fans
   out to every registered agent. Returns 200; the broker
@@ -500,6 +505,11 @@ not ours.
   is sent as `null`). Targets stay immutable — cancel + new
   schedule is the retarget workaround. Refuses cancelled rows;
   returns the updated `WireSchedule` on success.
+- `POST /api/schedules/{id}/fire-now` — operator-initiated manual
+  fire (#467). Runs the per-target fan-out once immediately.
+  Recurring schedules keep their cadence (manual fire is additive);
+  one-shot schedules are consumed (cancelled afterwards). Manager
+  surface: `fire_schedule_now(id)` MCP tool.
 - `POST /api/schedules/{id}/cancel` — cancel a schedule. Body
   `{ targets?: ["name", …] }` cancels just those recipients;
   absent or empty body cancels the whole schedule.