docs: scheduled prompts are swarm-level; the hive page is a read-only list

Drops docs/tools/scheduling.md and every description of hive-level
schedule creation, the worker, the removed MCP tools, the scheduling tool
group and the removed endpoints/events, pointing at docs/swarm/schedules.md.

docs/agent-lifecycle/agent-roster.md

@@ -94,12 +94,8 @@ apply.
   approval step — every other agent is created at swarm level
   (`swarmctl agent create`).
   Roster-wise, `ruth` is just another entry.
-- **Wire-protocol** — the `*(privileged)*` `Request` variants in
-  `hive-core-agent-sock`'s unified enum are the scheduling ops
-  (`RequestSchedulePrompt`, `CancelSchedule`, `FireScheduleNow`,
-  `EditSchedule`), reachable only from the manager's socket flavour,
-  matching the `scheduling` tool group
-  ([`docs/turn-loop/mcp.md`](../turn-loop/mcp.md)). Container lifecycle
+- **Wire-protocol** — `hive-core-agent-sock`'s unified `Request` enum
+  is the same on both socket flavours. Container lifecycle
   ops (kill/start/restart/rebuild) go through the separate host-admin
   socket `hivectl` speaks. `Wake` (inject a `from: <X>` message straight
   into the caller's own inbox) is on this socket too, unprivileged on