The code review re-does the judge's playtest #307
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
Run 139's
agent.code-reviewspent most of its hour on a desktop and phone playtest it handed to thebrowsersubagent throughwindow.__app; its own scripted player could not reach a win or a loss, it was cut at its 1 h limit (#303), and the judge then played the game again for 29 min. After apply, the review was the largest cost in the item.Fix
The code review reads the code and runs the lanes; playing the app is the judge's, and the review brief says so.
Done when
A code review on a web game finishes without a browser playtest, and the judge still plays it.
From run 139.
Confirmed on production (
6f440e5, PR #310); closing.Run 147 (thorough, the Breakout project's item, vLLM) ran its
agent.code-reviewas the newreviewagent, which has no browser:appcalls and no subagents. Nothing served or played the game.openspec validate --strict, a grep for leftover logging, a lockfile check, a speed calculation innode -e, and two unit-test files). It made 2 small fixes, the starting keypress insrc/main.jsand a test's speed cap, then wrote its report.The judge plays the game after it, in a session of its own.