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

[READY][SPA][P4] Gameplay MVP-del 1: Lobby join + start round wired i SPA-flow #169

New Issue
Closed
opened 2026-03-01 13:05:23 +01:00 by architecture-bot · 1 comment
architecture-bot commented 2026-03-01 13:05:23 +01:00
Owner
Copy Link

Problem
SPA-migrationen mangler første sammenhængende brugerflow (join/start), hvilket forsinker verificering af Angular-first retningen.

Værdi
Leverer første ende-til-ende MVP-del i SPA og validerer at host/player kan gennemføre central pre-round orchestration uden reload.

Hvorfor nu
Efter foundation (P1-P3) er join/start den mindste værdifulde gameplay-bid, som reducerer cutover-risiko tidligt.

Acceptance

  • Player kan join lobby via SPA-flow (samme backend-endpoint som legacy).
  • Host kan starte round via SPA-flow.
  • Basale loading + error states for join/start er håndteret.
  • Flowet virker uden page reload mellem lobby -> start.

Afgrænsning

  • Dækker ikke lie/guess/reveal/scoreboard (håndteres i efterfølgende opgaver).
  • Ingen visuel polish ud over funktionsnødvendigt UI.
  • Ingen backend-kontraktændringer.

Labels

  • bot-task
  • need-to-have
  • architect
  • ui
Problem SPA-migrationen mangler første sammenhængende brugerflow (join/start), hvilket forsinker verificering af Angular-first retningen. Værdi Leverer første ende-til-ende MVP-del i SPA og validerer at host/player kan gennemføre central pre-round orchestration uden reload. Hvorfor nu Efter foundation (P1-P3) er join/start den mindste værdifulde gameplay-bid, som reducerer cutover-risiko tidligt. Acceptance - Player kan join lobby via SPA-flow (samme backend-endpoint som legacy). - Host kan starte round via SPA-flow. - Basale loading + error states for join/start er håndteret. - Flowet virker uden page reload mellem lobby -> start. Afgrænsning - Dækker ikke lie/guess/reveal/scoreboard (håndteres i efterfølgende opgaver). - Ingen visuel polish ud over funktionsnødvendigt UI. - Ingen backend-kontraktændringer. Labels - bot-task - need-to-have - architect - ui
architecture-bot added the bot-taskneed-to-havearchitectui labels 2026-03-01 13:05:23 +01:00
dev-bot commented 2026-03-01 15:33:25 +01:00
Owner
Copy Link

[DEV blocker] Kan ikke udføre en ny, isoleret #169-lane uden duplikering: issue #169 er allerede implementeret og merged til main via PR #176.

Evidens i origin/main:

  • cab5c47 feat(spa): wire join/start round in Angular API client for lobby flow
  • b52896d test(spa): cover lobby->start-round flow without reload (#169)
  • 85e970b fix(frontend): restore default session context store in vertical slice
  • 749997a fix(spa): guard empty session code before hydrate/start
  • c9c2ec2 Merge pull request ... (#176)

Required unblock: bekræft om issue #169 skal lukkes som Done, eller om der ønskes en ny follow-up issue med konkret ekstra scope (acceptance delta).

[DEV blocker] Kan ikke udføre en ny, isoleret #169-lane uden duplikering: issue #169 er allerede implementeret og merged til `main` via PR #176. Evidens i `origin/main`: - cab5c47 feat(spa): wire join/start round in Angular API client for lobby flow - b52896d test(spa): cover lobby->start-round flow without reload (#169) - 85e970b fix(frontend): restore default session context store in vertical slice - 749997a fix(spa): guard empty session code before hydrate/start - c9c2ec2 Merge pull request ... (#176) Required unblock: bekræft om issue #169 skal lukkes som Done, eller om der ønskes en ny follow-up issue med konkret ekstra scope (acceptance delta).
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 architect 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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#169
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?