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

[READY][SPA][P7] Gameplay MVP-del 2: Lie -> guess -> reveal -> scoreboard wired i Angular-flow #172

New Issue
Closed
opened 2026-03-01 13:36:09 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-01 13:36:09 +01:00
Owner
Copy Link

Problem
Efter lobby/join/start mangler den faktiske rundeafvikling i SPA, så MVP kan ikke verificeres ende-til-ende uden legacy-hop.

Værdi
Giver første komplette gameplay-runde i Angular UI og reducerer risikoen før cutover ved at validere kerne-loopet på eksisterende API-kontrakter.

Hvorfor nu
PO-direktivet kræver fremdrift i SPA-migrationen (foundation -> gameplay MVP -> cutover). Denne opgave er næste uafhængige bid efter P4/P5 og er nødvendig for release-nær spilbarhed.

Acceptance

  • Host/player kan gennemføre lie -> guess -> reveal -> scoreboard i SPA uden page reload.
  • Samme Django-endpoints og payload-kontrakter som legacy bruges (ingen kontraktændringer).
  • Loading/error/retry state findes for mindst én fejlvej i hver af submit/reveal/scoreboard overgange.
  • Evidens i PR-beskrivelse: kort flow-log + screenshots eller test-output.

Afgrænsning

  • Ingen visuel polish ud over funktionsnødvendigt UI.
  • Ingen nye backend-features/endpoints.
  • Ingen final leaderboard/cutover-aktivering i denne opgave.

Labels

  • bot-task
  • need-to-have
  • architect
  • ui
Problem Efter lobby/join/start mangler den faktiske rundeafvikling i SPA, så MVP kan ikke verificeres ende-til-ende uden legacy-hop. Værdi Giver første komplette gameplay-runde i Angular UI og reducerer risikoen før cutover ved at validere kerne-loopet på eksisterende API-kontrakter. Hvorfor nu PO-direktivet kræver fremdrift i SPA-migrationen (foundation -> gameplay MVP -> cutover). Denne opgave er næste uafhængige bid efter P4/P5 og er nødvendig for release-nær spilbarhed. Acceptance - Host/player kan gennemføre lie -> guess -> reveal -> scoreboard i SPA uden page reload. - Samme Django-endpoints og payload-kontrakter som legacy bruges (ingen kontraktændringer). - Loading/error/retry state findes for mindst én fejlvej i hver af submit/reveal/scoreboard overgange. - Evidens i PR-beskrivelse: kort flow-log + screenshots eller test-output. Afgrænsning - Ingen visuel polish ud over funktionsnødvendigt UI. - Ingen nye backend-features/endpoints. - Ingen final leaderboard/cutover-aktivering i denne opgave. Labels - bot-task - need-to-have - architect - ui
architecture-bot added the bot-taskneed-to-havearchitectui labels 2026-03-01 13:36:09 +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 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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