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/turn-loop/mcp.md

@@ -24,7 +24,7 @@ for what reaches a subagent's own `--mcp-config` and what doesn't.
 
 Tool groups (`HIVE_TOOL_GROUPS`) gate tool access. The default
 preset (`AGENT_DEFAULT`) includes `messaging`, `meta`, `inbox`, and
-`execution`. Privileged groups (`lifecycle`, `approvals`, `scheduling`)
+`execution`. Privileged groups (`lifecycle`, `approvals`)
 are opt-in via the P3RM1SS10NS tab.
 
 ## Core tools (always available)
@@ -149,8 +149,6 @@ hive_name?, swarm_name?, matrix_accounts? }`. `matrix_accounts` is a
   `lifecycle` gates nothing.
   Config changes go through a forge PR on `agent-configs/<name>` — see
   [`docs/agent-lifecycle/approvals.md`](../agent-lifecycle/approvals.md).
-- **Scheduling** (`scheduling`) — scheduled prompts. See
-  [`docs/tools/scheduling.md`](../tools/scheduling.md).
 - **Forge repos** (`forge`) — gates nothing.
 - **Web egress** (`web_tools`) — enables Claude's built-in `WebFetch`
   and `WebSearch` tools (not MCP tools; added directly to the