v0.0.54

• Issue #104 (harvest half only): rdm_requests.ds now carries reviewers and reviewer_names on every request. The reviewer field turned out to be real, first-class RDM data (request.reviewers, gated by REQUESTS_REVIEWERS_ENABLED) rather than something derived from community membership, and it was simply never selected before. Four scoping decisions in DR-0025: users only this cut (zero production requests carry a group-type reviewer, so there was nothing to resolve against), reviewer_names joined with "; " matching the existing groups column's convention, username rather than full_name matching submitted_by's convention, and it ships alone rather than bundled with #104's later UI comments
• No incremental-harvest code change was needed: the incremental shares emit_harvest_sql with the full harvest (DR-0014 decision 8), so both fields arrived automatically on its next scheduled tick -- verified against live production counts rather than assumed
• This is the data foundation only. cold_api.yaml has no review_queue_by_reviewer query and rdm_review_queue.ts has no Reviewer column, CSV field, or search-dropdown option yet -- #104 stays open for that UI cycle, plus Tom's later asks (title/publisher search, a client-side sortable-table rearchitecture, splitting the live queue into its own URL path, matching irdm-queue-portal's sort/order UI)

Full Changelog: v0.0.53...v0.0.54