galaxy-game

T

Ilia Denisov 82c4f70156 local-dev: stop spawned engine containers in down/clean

Backend's runtime spawns the engine container outside the compose
project, so `docker compose down` left a `galaxy-game-…` container
running. Add a `stop-engines` target that finds them by their OCI
image-title label (set in game/Dockerfile) and remove forcibly;
make `down` and `clean` depend on it. `clean` additionally wipes
the per-game state directory under /tmp/galaxy-game-state.

Add a troubleshooting note for the related symptom: when the
browser holds a keypair from a previous DB and `make clean`
recreates everything, the lobby renders "no games yet" until the
user clears site data or opens an incognito window. The dev user
keeps the same email but receives a fresh user_id, which the old
keypair cannot authenticate against.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-08 19:04:05 +02:00

.claude

phase 4: drop stale gRPC nomenclature from integration tests

2026-05-07 11:52:17 +02:00

.gitea/workflows

ci: skip docs-only triggers; document per-stage local-ci gate

2026-05-07 09:47:27 +02:00

backend

local-dev: log memberships-ensured count in dev_sandbox bootstrap

2026-05-08 16:18:38 +02:00

client

ui/phase-9: PixiJS map renderer with torus and no-wrap modes