lda.chat/lda-wf
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: make client schedule mapping explicit

Browse Source
This commit is contained in:
lda
2026-09-10 05:38:44 +07:00 Verified
parent cced1b4c2d
commit 72d9ac3e2a
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md
+5 -3
View File
@@ -355,9 +355,11 @@ Administration is available through the `WorkflowApi` schedule methods,
`workflow.schedules.*` RPC, and Python client. The API/transport operations
are `create_schedule`, `get_schedule`, `list_schedules`, `update_schedule`,
`pause_schedule`, `resume_schedule`, `delete_schedule`, and paginated
`list_schedule_occurrences`; the Python facade maps them to the names listed
above. Creation validates the trigger, the deployment, the binding shapes, and
a sample-occurrence
`list_schedule_occurrences`; the Python facade names these operations
`create_schedule`, `schedule`, `schedules`, `update_schedule`,
`pause_schedule`, `resume_schedule`, `delete_schedule`, and
`schedule_occurrences`. Creation validates the trigger, the deployment, the
binding shapes, and a sample-occurrence
resolution against the pinned root schema, and starts the consumed
watermark at creation (no pre-creation backfill). Updates are
revision-checked; pause/resume/delete mirror the poll-loop transitions;