ask-feather

Enqueue a turn (Phase 3 split contract): run the same fast pre-flight gates as before, commit a durable queued turn row, drop a job on the ask_feather worker queue, and return {turn_id}. The client then opens a separate …/turns/{turn_id}/stream request to watch it. The web process holds no DB connection and does no AI work past this point.

post/v1/ask-feather/sessions/{session_id}/messages

Request

Path parameters

session_idstring uuid required

Request body

contentstring required
workflowstring nullable

Response

Successful Response

turn_idstring uuid required
statusstring required

Changes

    • breaking

      removed the success response with the status

    • warning

      the request property's maxLength was set to 20000

    • info

      added the success response with the status