wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[READY][Gameplay] #287-F Host transition idempotency and error catalog for scoreboard -> next round / finish #310

New Issue
Closed
opened 2026-03-16 19:33:45 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-16 19:33:45 +01:00
Owner
Copy Link

Parent epic: #287

Problem statement

The host transition endpoints now exist, but the remaining high-value risk is inconsistent or weakly defined behaviour around repeated clicks, stale phase state, and client-visible errors when moving from scoreboard to next round or finish.

Expected value / why now

This hardens the final host-controlled edges of the canonical loop and makes the game feel robust rather than fragile under refreshes, retries, or slightly stale UI state.

Acceptance criteria

  • Verify and harden idempotent behaviour for scoreboard-only host transitions (next round, finish game).
  • Add targeted tests for repeated host actions, wrong-phase requests, and client-visible error codes/messages.
  • Ensure the API returns predictable error codes for invalid phase / repeated action paths instead of inconsistent fallthrough behaviour.
  • Confirm the resulting session-detail state remains coherent after retry/reload patterns.
  • PR references #287 and documents the intended retry behaviour for host clients.

Scope boundary

  • Not scoring-rule redesign.
  • Not lobby/category UX polish.
  • Not release/deploy work.
Parent epic: #287 ## Problem statement The host transition endpoints now exist, but the remaining high-value risk is inconsistent or weakly defined behaviour around repeated clicks, stale phase state, and client-visible errors when moving from scoreboard to next round or finish. ## Expected value / why now This hardens the final host-controlled edges of the canonical loop and makes the game feel robust rather than fragile under refreshes, retries, or slightly stale UI state. ## Acceptance criteria - Verify and harden idempotent behaviour for scoreboard-only host transitions (`next round`, `finish game`). - Add targeted tests for repeated host actions, wrong-phase requests, and client-visible error codes/messages. - Ensure the API returns predictable error codes for invalid phase / repeated action paths instead of inconsistent fallthrough behaviour. - Confirm the resulting session-detail state remains coherent after retry/reload patterns. - PR references #287 and documents the intended retry behaviour for host clients. ## Scope boundary - Not scoring-rule redesign. - Not lobby/category UX polish. - Not release/deploy work.
agw closed this issue 2026-03-18 06:52:04 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#310
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?