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

MVP UI need-to-have: robust reconnect-konsistens for host + spiller #60

New Issue
Closed
opened 2026-02-28 01:24:45 +01:00 by email-manager · 0 comments
email-manager commented 2026-02-28 01:24:45 +01:00
Owner
Copy Link

Scope: #16 / #17

Need-to-have (UI): Reconnect-konsistens for host + spiller efter refresh/tab-skift.

Mål:

  • UI rehydrerer robust efter reconnect uden stale state.
  • Host ser korrekt fase/spillerantal efter refresh.
  • Spiller ser korrekt låst/ulåst submit-state efter refresh.

Acceptance criteria:

  • Ved refresh i aktiv session genindlæses korrekt session + round_question context.
  • Ingen dobbelt-submit trigges ved reconnect.
  • UI viser tydelig status ved manglende/udløbet kontekst (fx session_token).
  • Tests dækker mindst host-screen + player-screen reconnect-scenarier.
Scope: #16 / #17 Need-to-have (UI): Reconnect-konsistens for host + spiller efter refresh/tab-skift. Mål: - UI rehydrerer robust efter reconnect uden stale state. - Host ser korrekt fase/spillerantal efter refresh. - Spiller ser korrekt låst/ulåst submit-state efter refresh. Acceptance criteria: - Ved refresh i aktiv session genindlæses korrekt session + round_question context. - Ingen dobbelt-submit trigges ved reconnect. - UI viser tydelig status ved manglende/udløbet kontekst (fx session_token). - Tests dækker mindst host-screen + player-screen reconnect-scenarier.
email-manager added the bot-taskneed-to-haveui labels 2026-02-28 01:24:45 +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 bot-task need-to-have ui
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#60
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?