[READY][Architecture] #311-A Map and isolate FupOgFakta-specific logic currently living in lobby/ #312

New Issue

2026-03-16T19:51:08+01:00

architecture-bot commented

2026-03-16 19:51:08 +01:00

Parent issue: #311

Problem statement

Before moving code safely, we need one explicit inventory of which parts of lobby/ are actually FupOgFakta-specific. Right now phase/state helpers, transition endpoints, and response contracts are mixed into the platform layer.

Expected value / why now

This creates a safe extraction map instead of a vague “move stuff later” intention. It reduces the risk of partial refactors that leave hidden game logic behind in lobby/.

Acceptance criteria

Identify the concrete FupOgFakta-specific helpers, endpoints, response builders, and phase-transition logic currently living in lobby/.
Distinguish them from truly generic platform/session concerns.
Produce one documented extraction map that names source files/functions and intended destination/module ownership.
Reference the existing cartridge-plan docs that describe the intended lobby vs fupogfakta boundary.
PR/issue output references #311 and states what is generic platform vs game-specific logic.

Scope boundary

Not the full code move itself.
Not frontend rewrite.
Not support for a second game yet.

Parent issue: #311 ## Problem statement Before moving code safely, we need one explicit inventory of which parts of `lobby/` are actually FupOgFakta-specific. Right now phase/state helpers, transition endpoints, and response contracts are mixed into the platform layer. ## Expected value / why now This creates a safe extraction map instead of a vague “move stuff later” intention. It reduces the risk of partial refactors that leave hidden game logic behind in `lobby/`. ## Acceptance criteria - Identify the concrete FupOgFakta-specific helpers, endpoints, response builders, and phase-transition logic currently living in `lobby/`. - Distinguish them from truly generic platform/session concerns. - Produce one documented extraction map that names source files/functions and intended destination/module ownership. - Reference the existing cartridge-plan docs that describe the intended `lobby` vs `fupogfakta` boundary. - PR/issue output references #311 and states what is generic platform vs game-specific logic. ## Scope boundary - Not the full code move itself. - Not frontend rewrite. - Not support for a second game yet.

architecture-bot referenced this issue

2026-03-16 19:51:08 +01:00

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

dev-bot referenced this issue from a commit

2026-03-17 06:37:40 +01:00

docs(architecture): map lobby vs fupogfakta extraction boundary refs #311 #312

dev-bot referenced this issue from a commit

2026-03-17 06:37:40 +01:00

refactor(fupogfakta): extract first lobby gameplay slice (#312)

dev-bot referenced this issue

2026-03-17 06:38:20 +01:00

refactor(fupogfakta): extract first lobby gameplay slice (#312) #319