Found while reviewing #789 and #797. docs/API.md documents a fictional PUT /api/job/{name} while the real endpoints are POST /api/jobs/create and POST /api/jobs/update; docs/openapi.yaml's paths stop at /jobs/{jobName}/history and carry none of the mutation API. Both PRs extend the real API surface (#789 maxRuntime, #797 /api/dashboard + recentRuns + 403 semantics) and can only be asked to not widen the gap — closing it needs a dedicated pass: describe the real create/update/delete endpoints in both files, then keep them in sync per PR.
Assisted by claude-code:claude-fable-5 — Session
Found while reviewing #789 and #797.
docs/API.mddocuments a fictionalPUT /api/job/{name}while the real endpoints arePOST /api/jobs/createandPOST /api/jobs/update;docs/openapi.yaml's paths stop at/jobs/{jobName}/historyand carry none of the mutation API. Both PRs extend the real API surface (#789maxRuntime, #797/api/dashboard+recentRuns+ 403 semantics) and can only be asked to not widen the gap — closing it needs a dedicated pass: describe the real create/update/delete endpoints in both files, then keep them in sync per PR.Assisted by claude-code:claude-fable-5 — Session