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

docs/wf_cli.md

@@ -109,6 +109,17 @@ small and avoids dumping arbitrary MCP resource payloads.
 registry. `--store-root` is for the local/static server path and cannot be
 combined with `--mcp-config`.
 
+Opt in to deployment scheduling on a local/static server (MCP-backed
+servers reject it for now):
+
+```bash
+wf-rpc-server --store-root .wf_store --enable-scheduler
+```
+
+or set `server.scheduler.enabled` (plus optional `poll_interval_s`,
+`max_concurrent_runs`, `drain_grace_s`) in the neutral config. See
+[`deployment scheduling operations`](deployment_scheduling.md).
+
 `admin registry` shows desired persisted source entries. It is separate from
 workflow artifacts and deployments, so it can be empty even when the server has
 runtime sources and saved workflows.