From QA repro to agent-ready repair: the combo that died on pause

A combo meter in a small toy game reset whenever the player paused. QA could see it, but the clip alone didn't say why: the combo window was timed with the wall clock, so pausing for longer than two seconds quietly ended the combo.

This deck walks through turning that report into repair work a coding agent can run. It covers the repro steps and environment, a fix scope with a stop rule, a test that fails before the fix, and regression proof afterwards, including the case the fix must not break. It also shows who prepares each part, who runs the agent with their own tools, and who accepts the result.

It's a cross functional AI workflow at the size of one bug. For the wider studio picture, see Wagglet's write-up on an AI-native mobile game studio stack.

All numbers come from a toy build, not a shipped game.

Transcript