feat(analytics): surface Go game stats in admin dashboard + instrument League Lens

[brooksRoley]

Summary

• Go game data (go_players, go_puzzle_attempts) has been dark in /admin/analytics since it shipped — isolated in its own Supabase tables per CLAUDE.md, but that also meant Go engagement had zero visibility. Wires in player count/avg ELO and puzzle attempt totals/solve rate, degrading independently to zero/null if the go_ tables error (never sinks the Pente stats or the request).
• Instruments League Lens (league_lens_view, league_lens_view_switch, league_lens_player_select) — closes the "zero track() instrumentation" ledger item flagged 2026-08-04 by this same Chief Data Scientist role.

Note on scope: an earlier version of this PR also relocated 6 pre-existing test files out of src/pages/api/**/__tests__ (they ship as live public routes under Next's Pages Router). That duplicated PR #23, which already fixed the same 6 files — open since 2026-08-08, CI green, zero conflicts, just waiting on a merge. Reverted that part here to avoid a conflict between the two PRs; this PR's own new test file is placed at src/__apiTests__/admin/analytics.test.ts to match PR #23's convention so it doesn't add another instance once #23 lands. #23 merging is still the actual unblock for the other 6 — flagged 3x in the project ledger already.

Livelihood stream

• Games
• Portfolio signal (hiring)

Go engagement data now informs whether it's worth investing further in the game vs. Pente.

Files changed

• src/pages/api/admin/analytics.ts — Go stats in readSupabaseStats()
• src/pages/admin/analytics.tsx — Go stats dashboard section
• src/components/nba/LeagueLens.tsx — track() instrumentation
• src/__apiTests__/admin/analytics.test.ts — new coverage for the Go wiring

Test steps

1. yarn dev, log in at /login, visit /admin/analytics — confirm the new "Go (Supabase)" card renders (0s if Supabase env vars aren't set locally)
2. Visit /nba, open the League Lens tab, switch views and click a scatter point — events fire to /api/events (check Network tab, or /admin/analytics after deploy)

Agent checklist

• yarn build passes locally
• yarn test passes — 694/694 (up from 691 baseline; pasted output below)
• No TODO, placeholder, or stub code
• No secrets, API keys, or .env values committed
• New pages include og:title, og:description, og:image, twitter:card — N/A, no new pages (dashboard is noindex)
• PreText, Reveal, TiltCard used for any new UI text/cards — N/A, dashboard uses the existing card pattern
• Lighthouse scores not regressed — not run locally; no client-facing page changed (admin dashboard is noindex, League Lens change is instrumentation-only)
• README updated if new pages or components were added — N/A, no new pages/components

yarn test
 Test Files  61 passed (61)
      Tests  694 passed (694)

yarn lint
$ eslint src --max-warnings 0
Done in 18.34s.

yarn build
✓ Compiled successfully

Learn

Next.js Pages Router treats every file under pages/api/** as a route candidate regardless of filename — __tests__ dirs and .test.ts files are not exempt. When adding a new API route test, put it outside pages/ from the start (this repo's convention, per PR #23, is src/__apiTests__/<mirrored-path>/) rather than relying on remembering to move it later.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
zero-next	Ready	Preview	Aug 11, 2026 4:06pm