List Organization Names

Every organisation's id and name, unpaged. The one job is resolving an org_id a wire shape carries into something a person can read.

NOT GET /organizations?limit=200, which is what the web app used and which cannot do this: MAX_PAGE_LIMIT = 200 clamps that endpoint server-side, there are 1,507 organisations, and useOrgNameLookup fell back to printing the raw UUID for every one past the first page. The Leads board showed cb4932c7-874e-459b-89e5-0ddb1ca6e04b where it meant "California Department of Corrections and Rehabilitation"; Adams County resolved only because it sorts early. Frederick, 2026-08-04: "It looks like you're not holding true names."

Paging is the wrong shape for this question, so this endpoint has none. Two columns over 1,507 rows is a small response, it is requested once per screen, and it can never silently truncate -- which is the entire failure being fixed. Third occurrence of this defect class (PR #205 for fulfillment/SlaPage.tsx, then tickets' own org_name JOIN); doing it in one place this time fixes all 32 call sites at once.

⛔state TRAVELS WITH THE NAME, BECAUSE THE NAME IS NOT UNIQUE. 210 names cover 675 organisations: there are eight Adams Counties, thirteen Madison Counties and twelve Washington Counties, in different states, and they are different agencies rather than duplicate rows. A picker showing bare names offers the same word eight times and no way to tell which one is meant. Frederick, 2026-08-31: "adams has more than one on the list. The list should match the organization list."

Declared BEFORE GET /organizations/{org_id} for the same routing reason /organizations/states is -- otherwise "names" is parsed as a UUID.