From d6c828aac0255382af642546e0eabb2ae436b6f2 Mon Sep 17 00:00:00 2001 From: lda Date: Thu, 10 Sep 2026 05:27:33 +0700 Subject: [PATCH] docs: name schedule client facade methods --- .../specs/2026-09-08-deployment-scheduling-design.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md b/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md index c088e7f1..f7e36245 100644 --- a/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md +++ b/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md @@ -293,10 +293,13 @@ schedules at `/schedules`, one lock at `/scheduler.lock`). ## Lifecycle, administration, and resource bounds Expose create/get/list/update/pause/resume/delete and paginated occurrence -inspection through the workflow API and Python client. The implemented names -are `create_schedule`, `get_schedule`, `list_schedules`, `update_schedule`, +inspection through the workflow API and Python client. The workflow API and +transport names are `create_schedule`, `get_schedule`, `list_schedules`, +`update_schedule`, `pause_schedule`, `resume_schedule`, `delete_schedule`, +and `list_schedule_occurrences`; the Python client facade exposes the same +operations as `create_schedule`, `schedule`, `schedules`, `update_schedule`, `pause_schedule`, `resume_schedule`, `delete_schedule`, and -`list_schedule_occurrences`. +`schedule_occurrences`. Reject stale schedule edits using revisions within the owning process. Occurrence inspection distinguishes pending, coalesced/superseded,