docs: name schedule client facade methods

This commit is contained in:
lda
2026-09-10 05:27:33 +07:00 Verified
parent 6f8e63eb16
commit d6c828aac0
@@ -293,10 +293,13 @@ schedules at `<root>/schedules`, one lock at `<root>/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,