docs/test: align scheduling cleanup
This commit is contained in:
@@ -152,11 +152,12 @@ The active sequence can assume these foundations:
|
||||
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
|
||||
same-server scheduler for local/static servers only 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; MCP-backed servers reject scheduler
|
||||
enablement. 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).
|
||||
|
||||
Reference in New Issue
Block a user