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

[READY][SPA] Error boundary + recover actions on top-level app shell #151

New Issue
Closed
opened 2026-03-01 08:42:12 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-01 08:42:12 +01:00
Owner
Copy Link

Problem

SPA-målarkitekturen for host/player kræver robust klientadfærd i dette område, men der mangler en afgrænset leverance.

Værdi

Forhindrer total hvid skærm ved runtime-fejl og giver hurtig recovery uden fuld hard reload mid-game.

Hvorfor nu

PO-direktiv er SPA for både host og player, og vi skal holde execution i gang uden at vente på integration.

Acceptance criteria

  • Implementering kan leveres i én lille PR uden afhængighed til andre READY-opgaver
  • Dækker scope i titel for host/player-flow
  • Ingen regression i eksisterende kerneflow (join lobby -> start -> gameplay)
  • Kort testnotat i PR (hvad er verificeret manuelt/automatisk)

Afgrænsning

  • Ingen backend- eller database-migrationer
  • Ingen release/deploy-arbejde i denne opgave
  • Ingen redesign af hele UI; kun målrettet scope jf. titel
## Problem SPA-målarkitekturen for host/player kræver robust klientadfærd i dette område, men der mangler en afgrænset leverance. ## Værdi Forhindrer total hvid skærm ved runtime-fejl og giver hurtig recovery uden fuld hard reload mid-game. ## Hvorfor nu PO-direktiv er SPA for både host og player, og vi skal holde execution i gang uden at vente på integration. ## Acceptance criteria - [ ] Implementering kan leveres i én lille PR uden afhængighed til andre READY-opgaver - [ ] Dækker scope i titel for host/player-flow - [ ] Ingen regression i eksisterende kerneflow (join lobby -> start -> gameplay) - [ ] Kort testnotat i PR (hvad er verificeret manuelt/automatisk) ## Afgrænsning - Ingen backend- eller database-migrationer - Ingen release/deploy-arbejde i denne opgave - Ingen redesign af hele UI; kun målrettet scope jf. titel
architecture-bot added the bot-taskneed-to-have labels 2026-03-01 08:42:12 +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
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#151
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?