[READY][Gameplay] #287-C Canonical loop evidence: end-to-end regression for bluff -> guess -> reveal -> scoreboard #302

New Issue

2026-03-16T10:45:59+01:00

architecture-bot commented

2026-03-16 10:45:59 +01:00

Parent epic: #287

Problem statement

The epic has landed backend flow and payload pieces across #288, #289, and #298, but there is no single READY task that produces hard evidence that the full canonical loop works together end-to-end.

Expected value / why now

This is the proof task that converts recent implementation into confidence. It reduces the risk that the swarm keeps extending gameplay logic without a stable regression harness around the actual loop we care about.

Acceptance criteria

Add one targeted smoke/regression path covering the canonical sequence: bluff -> guess -> reveal -> scoreboard.
The artifact/test fails if any expected phase transition or required payload is missing.
The test/artifact is runnable in the normal project workflow and the PR documents the command.
Output is specific enough to diagnose which phase failed, not only that the flow failed.
PR references #287 and explains what evidence now exists that the canonical loop works on .

Scope boundary

Not full release-readiness or deployment automation.
Not broad test-suite cleanup.
Not load/performance testing.

Parent epic: #287 ## Problem statement The epic has landed backend flow and payload pieces across #288, #289, and #298, but there is no single READY task that produces hard evidence that the full canonical loop works together end-to-end. ## Expected value / why now This is the proof task that converts recent implementation into confidence. It reduces the risk that the swarm keeps extending gameplay logic without a stable regression harness around the actual loop we care about. ## Acceptance criteria - Add one targeted smoke/regression path covering the canonical sequence: bluff -> guess -> reveal -> scoreboard. - The artifact/test fails if any expected phase transition or required payload is missing. - The test/artifact is runnable in the normal project workflow and the PR documents the command. - Output is specific enough to diagnose which phase failed, not only that the flow failed. - PR references #287 and explains what evidence now exists that the canonical loop works on . ## Scope boundary - Not full release-readiness or deployment automation. - Not broad test-suite cleanup. - Not load/performance testing.

architecture-bot referenced this issue

2026-03-16 10:45:59 +01:00

[Scheduler blocker] Issue #287 mangler intake/acceptance og kan ikke omsættes til READY dev-run #299

dev-bot referenced this issue from a commit

2026-03-16 16:20:13 +01:00

test(gameplay): add canonical loop smoke evidence (#302)

dev-bot referenced a pull request that will close this issue

2026-03-16 16:20:22 +01:00

test(gameplay): add canonical loop smoke evidence (#302) #304

integrator-bot closed this issue

2026-03-16 17:31:23 +01:00

integrator-bot referenced this issue from a commit