Set Review Response Draft Status Route
Record Copy or Dismiss against an existing draft.
Separate from the edit route because the request vocabularies are
disjoint: that one carries user-authored text and always lands on
edited; this one carries no text and may only reach the two statuses
a user ACTION produces. Folding them into one optional-everything body
would let a client rewind an edited draft to draft.
Copy and Dismiss are persistent per Design §4.4 — the card is purely
presentational and calls back to its container, which reaches this route
through the shared useReviewResponseDraft hook, so every mounted
surface sees the same status without a refetch.
No entitlement gate: neither transition generates anything, so metering them would charge a user for clicking Copy.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
PATCH body — record Copy or Dismiss against an existing draft.
Both are informational markers, never gates (Design §4.4): a copied
draft can be copied again, and a dismissed one returns to draft
when the user regenerates it.
copied, dismissed Response
Successful Response
One AI-drafted reply, as served to every consuming surface.
draft, edited, copied, dismissed