ops: verify / restore fix-bounty-amounts-supabase.js (bounty amounts may not match source-of-truth CSV)

[sacha-l]

Goal

Confirm whether `server/scripts/fix-bounty-amounts-supabase.js` (added in commit `5bd0878`, deleted in cleanup commit `62928dd` on branch `feat/agentic-workflow-setup`) had been run against production before deletion. If not, restore and run it.

Observed

• Commit `5bd0878` on `main` was titled fix: add Supabase script to correct bounty prize amounts from CSV. The script read the canonical payouts CSV and patched `bounty_prizes.amount` values in Supabase.
• Commit `62928dd` (on branch `feat/agentic-workflow-setup`) deleted it as part of a one-shot script cleanup pass.
• If the script never ran against prod, some `bounty_prizes.amount` values may still be wrong (e.g., hardcoded to $2500 from migration) rather than reflecting the CSV.

A prod snapshot taken 2026-04-15 shows `bountyPrize.amount` values varying ($500, $1000, $2000, $2500, $3000, $4000, $5000), so SOME correction has happened. But there's no log confirming the full reconciliation was applied.

Acceptance criteria

• Determine (via Railway run history, git log, deploy logs, or checking whether current prod values match the CSV row-by-row) whether the script ran.
• If it did NOT run, restore it from history:
  ```bash
  git show 62928dd^:server/scripts/fix-bounty-amounts-supabase.js > server/scripts/fix-bounty-amounts-supabase.js
  ```
  Then run against prod with appropriate credentials, then delete again.
• If it DID run, close this issue with a note confirming.

Files likely affected

• Possibly `server/scripts/fix-bounty-amounts-supabase.js` (restored temporarily)
• Supabase `bounty_prizes` rows

Out of scope

• Making the fix idempotent or production-safe as a reusable tool.
• Issue data: Plata Mia bountyPrize is three bounties concatenated into one row #27 (Plata Mia concatenation) — related but distinct.

Notes / context

Identified during the same `/ship-issue` workflow test that produced issues #26 and #27.

[sacha-l]

Flagging this as a Block G (alpha rehearsal) pre-condition for the Stadium Phase 1 revamp (see docs/stadium-revamp-phase-1-spec.md).

The 2026-04-22 Vercel preview audit validated alpha-candidate data shape (repo link, live URL, team rosters) across OpenArkiv, Kleo Protocol, ObraClara, and Playnet — but did NOT verify bounty amounts. If the CSV reconciliation never ran against prod, other alpha candidates may have wrong amounts, breaking the same "boutique" feel during rehearsal that #27 addresses.

Can run in parallel with Block A. See docs/stadium-revamp-phase-1-spec.md §5 Issue 13 "Pre-conditions not yet validated" for the full context.