solo never asks a new web project for window.__app, and an unclear play-through passes #272
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 122 (
solo, a new project) built a game with nowindow.__app. Its build brief never asked for it: on an empty repository Braid can't yet tell it's a web project, andsolo's proposal records no stack. The judge then marked the whole-session play-through unclear ("The page has nowindow.__apphook"), and the run passed anyway. That's how a table with no drain got through.Fix
window.__appwhen the brief or the proposal describes an interactive web app, not only once files exist.Done when
A
solorun on a new game exposeswindow.__app, and a judge that cannot play the game fails it.From the #260 re-run's transcripts.
Shipped in #301 (
5355515, deployed). It's part ofplanned-projects-finish-right, archived once the change's other issues are verified.Seen on production in run 139 (cmoriarty/breakout-planned, a new Vite Breakout game on vLLM):
window.__app, and the game exposesstate(),start(),launch(),press(key)andpaddleTo(x).playrecord:{"hook": true, "verdict": "pass", ...}. Its evidence is a whole session played through the hook, quotingstate()at each move: start, launch, a brick broken (score 10,bricksLeft 47), three balls lost togame-over, andstart()back to a fresh game. Round 1 passed.A play-through that is
unclearorfailfailing the round is covered by tests (tests/engine/test_state_hook.py). This run's game was playable, so production didn't exercise that path.