fix(admin): rebuild match-report review layout, and show completed reports honestly

[diese-tech]

Two related fixes to the admin Match Report screen.

---

1. The review layout was unusable

The review step put two min-w-[480px] stat tables into a 2xl:grid-cols-2 split of a column that was itself roughly one third of a max-w-7xl page. Each table was therefore rendered narrower than its own minimum width, so correcting a game meant driving two independently side-scrolling panes with the IGN column pushed off the left edge — while typing into inputs 40–64px wide and text-xs/py-0.5 tall.

The Tailwind breakpoints made it worse rather than better: 2xl: is a viewport query, so on a wide monitor it split an already-narrow fixed-width container into two even narrower halves.

Layout

• New TeamStatEditor replaces both <table>s. It lays the same nine fields out on a container-query grid, so it responds to the card's own width rather than the viewport: one line per player at ≥56rem, a two-line wrap at ≥36rem, three lines below that. Nothing scrolls sideways at any width.
• The two team cards stack full width instead of splitting the column in half — splitting it was what forced the tables to scroll.
• The score bar, game tabs and winner picker collapse into one sticky control bar. Setting the winner now happens on the team card it applies to, instead of a third row repeating both team names.
• Page widened to 1680px; the select/upload/done steps are capped at max-w-3xl so they don't stretch across it.
• The report list can fold away, so it stops competing with the editor for width once a report is open.

Inputs (shared with the host review screen via stat-inputs.tsx)

• Sized as real form controls: 36px tall, 14px text, visible focus rings.
• Number spinners suppressed — they consumed roughly a third of each box and misfire on scroll.
• Accept className and disabled so callers can size and lock them from their own layout.
• Every field carries an aria-label, and the unlinked-IGN count is named on the team card header instead of only being an amber row tint.

---

2. A completed report was a dead end — and a resubmit could lie

Opening a completed report showed a bare score card with no way to see the stats behind it. Underneath that was a real correctness bug.

resolve_match_report_review returns early for a report already in done: it responds already_processed / applied: false with the original scores and writes nothing. The submit route discarded both fields and always answered ok: true with whatever scores came back — so a resubmit of a published report rendered "Result Submitted" while the corrections were silently dropped.

• Pass applied and code through the submit route; the client now says the report was already published and nothing changed, rather than showing the success screen.
• Open completed reports onto the published stats read-only, with game tabs and the screenshots — rebuilt from player_match_stats rather than extracted_data, which holds the AI/host extraction and never receives the admin's review corrections.
• TeamStatEditor gains readOnly, so the published view reuses the same responsive grid with its fields disabled and edit affordances gone.
• The UI states plainly that published stats cannot be edited here and what the actual path is, instead of presenting a dead end.

Known limitation

Editing stats or adding screenshots to a completed report is refused by the database, not by this UI. resolve_match_report_review short-circuits on status = 'done', and resolve_match_report_review_unpublished additionally requires the match to still be scheduled/live. The upload route's existing 409 on done is consistent with that. Lifting the restriction needs a change to resolve_match_report_review in diese-tech/sal-database — out of scope for this repo. This PR makes the limit visible and honest rather than silently lossy.

---

Verification

• npx tsc --noEmit clean; npm run lint reports no new warnings.
• npm run test — 781 passed, 26 skipped, 0 failed (up from 775; new coverage for groupPublishedStats/groupRowsByReport and for the not-applied submit path).
• Driven with Playwright against the real review screen at 1680 / 1200 / 820 / 430px: no horizontal overflow on the document or on any element, and no console errors at any width.
• Completed-report view verified at 1500px: 70 inputs rendered, all disabled, none editable.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sal-draft-league	Ready	Preview	Sep 1, 2026 7:09am UTC