Submit Run Feedback

POST /runs/{run_id}/feedback

Upsert per user. 200 rather than 201: the second call updates a row it did not create, and answering 201 both times would tell a client it made two ratings.

Role floor

Requires viewer or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
run_id	path	string (uuid)	required	—

Request body — FeedbackWrite

Field	Type		Notes
rating	up | down	required	—
categories	string[]	optional	—
comment	string | null	optional	max length 4000

Responses

Status	Description	Body
200	Successful Response	FeedbackView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/runs/{run_id}/feedback \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "rating": "up"
     }'

Response — FeedbackView

Field	Type		Notes
id	string (uuid)	required	—
run_id	string (uuid)	required	—
agent_id	string (uuid)	required	—
session_id	string (uuid) | null	optional	—
user_id	string (uuid) | null	optional	—
rating	up | down	required	—
categories	object[]	optional	—
comment	string | null	optional	—
source	string	required	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—