Roadmap: where to take the app after the good-first-issue batch

[testtest126]

Today's multi-agent push landed a lot: display names, sounds and board themes (#20), the rematch flow (#22, E2E-covered by #26), iOS build + UI tests in CI (#23, fixed up by #24/#27), and the engine's persistent transposition table with pondering (#25). Selectable time controls (#13) are implemented and in review; the JWT 5 migration (#21) is in flight; Sign in with Apple (#14) and public deployment (#28) are queued.

With the backlog thinning, this is a good moment to decide direction. Some candidate themes, roughly by area:

Online play depth — rating-window matchmaking (#43), rematch decline/expiry (#39), custom time controls beyond the three presets, spectating live games, per-control leaderboards and rating histories.

Single-player strength & features — bounded TT memory on mobile (#46), engine strength levels / handicaps, opening-book breadth, post-game analysis with "best was" callouts for local games, puzzle mode from finished games' blunders.

Platform & polish — iPad / macOS Catalyst layout, accessibility (VoiceOver on the board), widgets or Live Activities for correspondence-style play, localization.

Infrastructure — public deployment (#28), observability on the server (metrics for queue depth / active games), load testing the GameCoordinator actor.

What matters most to you? Comments welcome — happy to spin any of these into concrete issues.

🤖 Generated with Claude Code

[testtest126]

Consolidated into #48, which includes a proposed priority order — please comment there. (Both threads were posted within minutes of each other by different coordinating sessions.)

🤖 Generated with Claude Code

[testtest126]

Consolidating the duplicate roadmap post (#48) into this one — status and a proposed execution order, current as of tonight:

Status updates since the post above: the JWT 5 migration is done (#21 closed via PR #42, both suites green). And a correction on the security front: the swift-nio-http2 advisory (#37) has no patched upstream release yet (1.44.0 is the newest tag), so it's a watch-for-release tracking issue, not an actionable bump.

Proposed execution order for the open backlog:

1. Platform hygiene first — CI: build the app with Xcode 26 so the Liquid Glass styles actually compile #44 (CI on Xcode 26 so the Liquid Glass paths actually compile), CI: boot chess-server on the runner so the online E2E test stops skipping itself #35 (boot the server in CI so the E2E test runs), Adopt Swift 6 language mode across the three packages #45 (Swift 6 language mode), Engine: bound the persistent transposition table's memory #46 (bound the persistent TT).
2. Product features building on today's work — Rematch: add a decline action and offer expiry #39 (rematch decline/expiry), Matchmaking: pair players by rating, widening the window over wait time #43 (rating-window matchmaking), Show an active online game on the home screen (resume banner) #29 (resume banner), Show server-side game history (online games from any device) #30 (server-side game history), Player profiles: tap a leaderboard row for record and recent games #33 (profiles), Selectable bot difficulty for offline games #36 (bot difficulty), Localize the app with a String Catalog #34 (localization), Rate-limit auth endpoints and clean up abandoned guest accounts #32 (auth rate limiting).

Blocked on the repo owner: #14 needs Apple team ID / bundle ID / entitlement / key-registration decisions (code scaffolding is proceeding); #28 needs a hosting choice — and #30/#33 get much more interesting once release builds point at a real server.

Owner: reply here with reordering or vetoes; agents will otherwise work roughly top-down.