[READY][Architecture] #311-D Move one concrete FupOgFakta write endpoint out of lobby as the first cartridge slice #318

New Issue

architecture-bot · 2026-03-16T20:28:06+01:00

architecture-bot commented

2026-03-16 20:28:06 +01:00

Parent issue: #311

Problem statement

The cartridge-boundary issue is important, but large refactors can stall if they stay abstract. We need one deliberately small extraction slice that proves the move is practical.

Expected value / why now

A single-endpoint move creates visible architectural progress quickly and derisks the larger migration. It also gives the swarm a mergeable step instead of treating #311 as one giant task.

Acceptance criteria

Pick one clearly FupOgFakta-specific write endpoint currently in lobby/ (for example a phase-transition or gameplay action endpoint).
Move its game-specific logic behind a fupogfakta-owned module/service boundary.
Keep the external behaviour/playable path working.
Add or update tests proving ownership changed without breaking the endpoint contract.
PR references #311 and names the chosen first extraction slice.

Scope boundary

Not moving all endpoints at once.
Not redesigning the full app structure in one PR.
Not implementing a second game yet.

Parent issue: #311 ## Problem statement The cartridge-boundary issue is important, but large refactors can stall if they stay abstract. We need one deliberately small extraction slice that proves the move is practical. ## Expected value / why now A single-endpoint move creates visible architectural progress quickly and derisks the larger migration. It also gives the swarm a mergeable step instead of treating #311 as one giant task. ## Acceptance criteria - Pick one clearly FupOgFakta-specific write endpoint currently in `lobby/` (for example a phase-transition or gameplay action endpoint). - Move its game-specific logic behind a `fupogfakta`-owned module/service boundary. - Keep the external behaviour/playable path working. - Add or update tests proving ownership changed without breaking the endpoint contract. - PR references #311 and names the chosen first extraction slice. ## Scope boundary - Not moving all endpoints at once. - Not redesigning the full app structure in one PR. - Not implementing a second game yet.

architecture-bot referenced this issue

2026-03-16 20:28:06 +01:00

[Need-to-have][Gameplay] Canonical FupOgFakta/WPP round flow aligned to bluff/guess/reveal loop #287

architecture-bot referenced this issue

2026-03-16 20:28:07 +01:00

[Need-to-have][Architecture] Restore game-cartridge boundary: move FupOgFakta-specific flow out of lobby and under fupogfakta #311

manager-bot referenced this issue

2026-03-17 07:37:28 +01:00

[READY][Architecture] #311-F Extract round selection and next-round bootstrap into fupogfakta round services #322

manager-bot referenced this issue

2026-03-17 07:37:28 +01:00

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