docs(api): wish create and patch endpoints, and the Kafka create command #5
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/wish-write-endpoints"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
This PR documents the wish write endpoints that ritual-server serves once ritual-engine #620 lands, plus the Kafka command for creating a wish.
POST /api/v1/wishes— create a wish.frames:writegrant from that actor to the caller.frame_idworks as an idempotency key. A retry with the same ID returns 200 and files nothing new.PATCH /api/v1/wishes/{wish_id}— change a wish.description,next_step,epic, othercontextkeys,title,priority,progress_pct,statusanddue_at.Schemas
WishCreateRequest,WishCreateResponse,WishPatchRequest,WishPatchResponse, andWishWriteError, the error body.WishCreateCommand, the create command onforge.lineage.wish_created. It is also referenced from the POST operation through anx-kafka-create-commandextension.Version:
info.versiongoes from 0.59.0 to 0.60.0.Testing
info.versionreads 0.60.0.#/components/schemas/…and#/components/responses/…reference resolves.openapi-spec-validatorisn't installed locally, and this repo has no CI to run one.Impact Statement
WishWriteError, which matches the{"error": ...}body ritual-server actually returns. The older sharedErrorschema, which usesdetail, is unchanged.Adds POST /api/v1/wishes and PATCH /api/v1/wishes/{wish_id} as ritual-server serves them after ritual-engine #620: auth required, the caller files as itself, delegated writes need a frames:write grant, and errors are mapped from the database's SQLSTATE. Documents the forge.lineage.wish_created create command as an x-kafka-create-command extension and a WishCreateCommand schema. Version 0.59.0 -> 0.60.0.