- Shipped
- September 9, 2026 at 11:44 PM UTC
- Author
- Kamo
- Commit
- 0a2729d
The docs settings page named its own categories and sent the ordinal it believed each one had. Those ordinals were written when ImageAssocType was six constants long; appending constants and giving them explicit ids moved CALL_RECORDING from ordinal 3 to 7, and the page never noticed. The tab labelled "Call Recordings" had been editing MY_DOCS, "My Documents" had been editing MEET_RECORDING, "Meet Recordings" had been editing SYSTEM_WIDE, "System-Wide" had been editing VM_RECORDING, and CALL_RECORDING was unreachable. Nothing failed, because an ordinal is always a valid category — just not the one you meant. GET **************** answers with the list the enum itself defines, so the ordinal and the name always leave here together and a caller never has to guess either. A category qualifies when folders or doc types are on or organization-settable — precisely "there is something here to set", which drops the associations that exist only as plumbing (a bug screenshot, a picture frame photo, a resume on a job application). Each row also carries the counts the settings table shows: doc types defined and active, stacking orders, and documents stored. Three org-wide reads grouped in memory rather than a query per category, so one request fills the whole table where the page previously needed thirty-nine.