PRD 25.38: Board rematch and disconnect lifecycle

[Anuraj-dev]

Parent

#90

What to build

Add explicit server-authoritative rematch and visible disconnect/grace/recovery state shared by both board games.

Acceptance criteria

• Both players can request/accept rematch without standing/reseating.
• Disconnect grace, reconnect, forfeit, waiting, and spectator states are explicit.
• Shared wire contracts and backend match machine remain the only authority.
• Transition matrices, manager/socket integration, analytics, and two-browser E2E pass.
• Behaviour is built in vertical red → green cycles through public interfaces where implementation changes are required.
• An independent reviewer gives READY and all required GitHub CI is green.
• Deployment-sensitive behavior is verified on production after merge.

Blocked by

• PRD 25.9: Analytics contract and ingestion foundation #99 — PRD 25.9
• PRD 25.24: Board-seat proximity validation #114 — PRD 25.24

Specification

PRD 25