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

docs: clarify schedule administration names

Browse Source
This commit is contained in:
lda
2026-09-10 05:36:58 +07:00 Verified
parent a11a7745c9
commit cced1b4c2d
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md
+7 -4
View File
@@ -351,10 +351,13 @@ its executing mark and ACTIVE attempt for startup recovery to abandon
truthfully), and releases ownership last.
A failed startup releases the lock and raises.
Administration (`WorkflowApi` schedules methods, `workflow.schedules.*`
RPC, Python client): `create/get/list/update/pause/resume/delete_schedule`
plus paginated `list_schedule_occurrences`. Creation validates the
trigger, the deployment, the binding shapes, and a sample-occurrence
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
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;