Block a user
refactor(engine): ambiguity burn-down batch 2 — SettingsResource cleared (198 → 171)
test(engine): enable Bevy system-order ambiguity detection in a headless test
Batch 1 merged (PR #146): 302 → 198 pairs (−34%). Fixed structurally: game-state ordering spine (pre-mutation chain + readers after GameMutation) and a self-ambiguous NewGameRequestWriters set.…
funman300
deleted branch refactor/ambiguity-burndown from funman300/Ferrous-Solitaire
2026-07-07 03:37:54 +00:00
refactor(engine): first ambiguity burn-down batch — 302 → 198 pairs
refactor(engine): first ambiguity burn-down batch — 302 → 198 pairs
funman300
created branch refactor/ambiguity-burndown in funman300/Ferrous-Solitaire
2026-07-07 03:37:52 +00:00
funman300
pushed to refactor/ambiguity-burndown at funman300/Ferrous-Solitaire
2026-07-07 03:37:52 +00:00
test(engine): enable Bevy system-order ambiguity detection in a headless test
Resolved as a ratchet (PR #145): first measurement found 302 ambiguous pairs in the headless gameplay cluster — far too many for one-pass triage, most likely benign but unproven. The schedule_chec…
funman300
deleted branch test/schedule-ambiguity from funman300/Ferrous-Solitaire
2026-07-07 03:22:31 +00:00
test(engine): ratchet on Bevy system-order ambiguities
funman300
created branch test/schedule-ambiguity in funman300/Ferrous-Solitaire
2026-07-07 03:22:29 +00:00
funman300
pushed to test/schedule-ambiguity at funman300/Ferrous-Solitaire
2026-07-07 03:22:29 +00:00
test(engine): ratchet on Bevy system-order ambiguities
fix(server): delete analytics_events rows on account deletion
Investigated before fixing: nothing in the workspace reads or writes analytics_events — no server route ingests it and the client ships events to the external Matomo instance (analytics.aleshym.co…
fix(server): delete analytics_events rows on account deletion
funman300
deleted branch fix/server-low-findings from funman300/Ferrous-Solitaire
2026-07-07 03:15:06 +00:00
fix(server): login timing pad, 409 on register race, avatar magic-byte check