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

[READY][Gameplay] #311-G Extract answer mixing and scoring engine out of lobby #323

New Issue
Open
opened 2026-03-17 07:37:28 +01:00 by manager-bot · 0 comments
manager-bot commented 2026-03-17 07:37:28 +01:00
Member
Copy Link

Parent: #311
Related: #312, #318

Problem

Svarblanding og score resolution ligger stadig tæt på lobby/-flowet, selv om begge dele er rene FupOgFakta-regler.

Goal

Udskil answer-mixing og scoring til cartridge-owned services, så bluff/correct/fooling-regler ikke længere lever i platformlaget.

Scope

In scope:

  • answer dedupe/shuffle/mix
  • score resolution for correct guesses og bluffs
  • event/record creation der direkte følger af scoring

Out of scope:

  • større session-detail refactor
  • routing-cutover
  • realtime transport-kontrakter i sig selv

Acceptance criteria

  • _prepare_mixed_answers(...) er flyttet ud af lobby/ til cartridge-owned service
  • _resolve_scores(...) er flyttet ud af lobby/ til cartridge-owned service
  • services kan testes isoleret uden fuldt endpoint-flow
  • tests dækker mindst: korrekt gæt, bluff-point, fooled-player edge cases og idempotens-forventning hvor relevant
  • lobby/ indeholder ikke længere FupOgFakta-specifik scorelogik som primær owner

Why this is a good fast-lane issue

Det er en relativt lille men højværdi-extraction, som reducerer kompleksiteten i flere efterfølgende route- og phase-issues.

Parent: #311 Related: #312, #318 ## Problem Svarblanding og score resolution ligger stadig tæt på `lobby/`-flowet, selv om begge dele er rene FupOgFakta-regler. ## Goal Udskil answer-mixing og scoring til cartridge-owned services, så bluff/correct/fooling-regler ikke længere lever i platformlaget. ## Scope In scope: - answer dedupe/shuffle/mix - score resolution for correct guesses og bluffs - event/record creation der direkte følger af scoring Out of scope: - større session-detail refactor - routing-cutover - realtime transport-kontrakter i sig selv ## Acceptance criteria - `_prepare_mixed_answers(...)` er flyttet ud af `lobby/` til cartridge-owned service - `_resolve_scores(...)` er flyttet ud af `lobby/` til cartridge-owned service - services kan testes isoleret uden fuldt endpoint-flow - tests dækker mindst: korrekt gæt, bluff-point, fooled-player edge cases og idempotens-forventning hvor relevant - `lobby/` indeholder ikke længere FupOgFakta-specifik scorelogik som primær owner ## Why this is a good fast-lane issue Det er en relativt lille men højværdi-extraction, som reducerer kompleksiteten i flere efterfølgende route- og phase-issues.
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
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#323
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?