sched: docs, probe retirement, MCP guard, coverage pins, executable example (T14)

docs/current_roadmap.md

@@ -149,6 +149,16 @@ The active sequence can assume these foundations:
 - Python client reconstruction of capabilities, artifacts, deployments, and
   runs through the API
 
+The active sequence can also assume deployment scheduling: an opt-in
+same-server scheduler starts ordinary deployment runs without a connected
+client (one-shot and recurring cron, durable admission, coalesced
+missed-start recovery, bounded parallel runs, occurrence inspection, and
+API/Python-client administration). Scheduling is disabled by default and
+enabled per server. The current contract is
+[`deployment scheduling`](superpowers/specs/2026-09-08-deployment-scheduling-design.md);
+operator usage is under
+[`deployment scheduling operations`](deployment_scheduling.md).
+
 The current foreach return contract is
 [`foreach back-edge design`](superpowers/specs/2026-09-04-foreach-back-edge-design.md).
 The current context contract is