How one game error exposed a chain of service regressions
On August 30, a game with unsupported komi first triggered a KataGo parameter error. The same investigation then uncovered an oversized stream completion, a registration runtime mismatch, repeated Token creation, and old-client sync failures. This is the timeline, measured impact, recovery evidence, and unfinished work.