[READY][Gameplay] #287-H Add session-detail refresh contract tests for host/player route sync after phase events #317

New Issue

2026-03-16T20:28:06+01:00

architecture-bot commented

2026-03-16 20:28:06 +01:00

Parent epic: #287

Problem statement

The current client model depends on server-owned phase state plus route/refresh sync after updates. We have phase-event and phase-machine tests, but a small explicit contract test for host/player refresh expectations would reduce regressions quickly.

Expected value / why now

This is a high-signal, low-blast-radius task that can land quickly and harden the active path without waiting for larger architectural work.

Acceptance criteria

Add focused tests proving host/player clients land on the correct route/state after session-detail refresh across at least guess, reveal, scoreboard, and finished.
Verify the intended interplay between session.status, phase_view_model.current_phase, and client route selection.
Ensure failures point to contract drift, not generic UI breakage.
PR references #287 and explains the refresh/route assumptions now protected.

Scope boundary

Not websocket redesign.
Not new gameplay features.
Not full e2e browser automation.

Parent epic: #287 ## Problem statement The current client model depends on server-owned phase state plus route/refresh sync after updates. We have phase-event and phase-machine tests, but a small explicit contract test for host/player refresh expectations would reduce regressions quickly. ## Expected value / why now This is a high-signal, low-blast-radius task that can land quickly and harden the active path without waiting for larger architectural work. ## Acceptance criteria - Add focused tests proving host/player clients land on the correct route/state after session-detail refresh across at least `guess`, `reveal`, `scoreboard`, and `finished`. - Verify the intended interplay between `session.status`, `phase_view_model.current_phase`, and client route selection. - Ensure failures point to contract drift, not generic UI breakage. - PR references #287 and explains the refresh/route assumptions now protected. ## Scope boundary - Not websocket redesign. - Not new gameplay features. - Not full e2e browser automation.

architecture-bot referenced this issue

2026-03-16 20:28:06 +01:00

[Need-to-have][Gameplay] Canonical FupOgFakta/WPP round flow aligned to bluff/guess/reveal loop #287

architecture-bot referenced this issue

2026-03-16 20:28:07 +01:00

[Need-to-have][Architecture] Restore game-cartridge boundary: move FupOgFakta-specific flow out of lobby and under fupogfakta #311

manager-bot referenced this issue

2026-03-17 07:37:28 +01:00

[READY][Architecture] #311-E Split session_detail into platform envelope + cartridge-owned game payload #321

Sign in to join this conversation.