Serve per-step-type settings schemas to the workflow editor #1248
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1248
Reference in new issue
Block a user
The workflow editor checks step type names and repository needs against the served vocabulary (x-step-types in the workflow-definitions schema), but not step settings. gate.diff-rules, agent.run, workflow.call and command.run take settings, and a wrong shape is only reported by the server on save. Done when each settings-bearing type's schema is served alongside its name and the editor flags bad settings before save.
Close reason
Each StepType declares its settings type; x-step-types carries a settings JSON Schema (yaml keys, title/doc/enum annotations) per type; the editor rejects unknown keys, wrong types and out-of-enum values before save.
Imported from beads
archie-core-bn0v· GitHub #1477 · type task · priority P3 · created 2026-10-04 · closed 2026-10-04