jhalitaksoy/mancala
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
94fc7fcbc7
mancala/docs/specs/rematch/tasks.md

19 lines
1.4 KiB
Markdown
Raw Normal View History

docs(rematch): add the spec Rematch from the game over card, alternating first moves and a series strip with the score of the games the same two players played in a row.
2026-10-17 01:58:58 +03:00
# Rematch and series: tasks
Work through the tasks in order; each ends with its tests passing and a commit. Tick a task when it is committed.
- [x] 1. **Spec**: requirements, design and tasks.
feat(backend): keep the series a live game belongs to Every game starts a series; a game created in a series gets its seat to move first. Clients get the series and the first seat with the game, the end message the series with the ended game; snapshots keep the series.
2026-10-17 02:00:44 +03:00
- [x] 2. **Series in live games**: `Series`, `SeriesGame`, `BackendGame.series` and `firstSeat()`, the first seat in
docs(rematch): add the spec Rematch from the game over card, alternating first moves and a series strip with the score of the games the same two players played in a row.
2026-10-17 01:58:58 +03:00
`createMancalaGame`; `series` and `firstSeat` in `ClientGame` and `GameEndMessage`, `series` in snapshots (with
the restore of old snapshots); unit and serialisation tests.
feat(backend): let players ask for a rematch RematchOffers keeps an offer open for ten minutes after a game nobody left. A request goes to the opponent; when both have asked the next game of the series starts with the other player moving first. Requests end on no, withdrawal, a minute without answer, going offline or looking for another game. The bot accepts at once.
2026-10-17 02:03:16 +03:00
- [x] 3. **Rematch requests**: `RematchOffers`, the four channels, the timers on the `Scheduler`, ending requests on
docs(rematch): add the spec Rematch from the game over card, alternating first moves and a series strip with the score of the games the same two players played in a row.
2026-10-17 01:58:58 +03:00
`new_game`, `new_bot_game` and going offline, the bot accepting at once; unit tests.
feat(backend): save the series of each game Migration 004_series adds games.series_id with an index, so the history can group a series later. Games saved before have none.
2026-10-17 02:04:24 +03:00
- [x] 4. **Saving**: `seriesId` in `GameRecord`, migration `004_series`, the repository; integration tests.
feat(core): add rematch channels, series types and texts The four rematch channels, Series and SeriesGame, the series and first seat of a game, getSeriesScore and the texts in English and Turkish.
2026-10-17 02:05:12 +03:00
- [x] 5. **Core**: channel names, types, `getSeriesScore`, texts in English and Turkish; unit tests.
docs(rematch): add the spec Rematch from the game over card, alternating first moves and a series strip with the score of the games the same two players played in a row.
2026-10-17 01:58:58 +03:00
- [ ] 6. **Web app, rematch**: the game page following `on_game_start` (`key={gameId}`), the game over card's rematch
states, "Play again" as a rematch, the score in two columns.
- [ ] 7. **Web app, series strip**: `SeriesStrip`, the series score on the game over card, spectators.
- [ ] 8. **End to end and docs**: the Chrome tests from `design.md`; `AGENTS.md` (the specs list, rematch notes),
`TODO.md` (the out of scope items; remove "A rematch button" from Web redesign), the web redesign design's note
on the rematch button.
Reference in New Issue Copy Permalink