solo never asks a new web project for window.__app, and an unclear play-through passes #272

Closed
opened 2026-10-28 11:54:57 -04:00 by cmoriarty · 1 comment
Owner

What happens
Run 122 (solo, a new project) built a game with no window.__app. Its build brief never asked for it: on an empty repository Braid can't yet tell it's a web project, and solo's proposal records no stack. The judge then marked the whole-session play-through unclear ("The page has no window.__app hook"), and the run passed anyway. That's how a table with no drain got through.

Fix

  • Ask for window.__app when the brief or the proposal describes an interactive web app, not only once files exist.
  • An interactive app's play-through that comes back unclear fails the round, saying what was missing.

Done when
A solo run on a new game exposes window.__app, and a judge that cannot play the game fails it.

From the #260 re-run's transcripts.

**What happens** Run 122 (`solo`, a new project) built a game with no `window.__app`. Its build brief never asked for it: on an empty repository Braid can't yet tell it's a web project, and `solo`'s proposal records no stack. The judge then marked the whole-session play-through **unclear** ("The page has no `window.__app` hook"), and the run passed anyway. That's how a table with no drain got through. **Fix** - Ask for `window.__app` when the brief or the proposal describes an interactive web app, not only once files exist. - An interactive app's play-through that comes back unclear fails the round, saying what was missing. **Done when** A `solo` run on a new game exposes `window.__app`, and a judge that cannot play the game fails it. _From the #260 re-run's transcripts._
Author
Owner

Shipped in #301 (5355515, deployed). It's part of planned-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):

  • The hook: the apply brief asked for window.__app, and the game exposes state(), start(), launch(), press(key) and paddleTo(x).
  • The judge's report now has the required play record: {"hook": true, "verdict": "pass", ...}. Its evidence is a whole session played through the hook, quoting state() at each move: start, launch, a brick broken (score 10, bricksLeft 47), three balls lost to game-over, and start() back to a fresh game. Round 1 passed.

A play-through that is unclear or fail failing 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.

Shipped in #301 (5355515, deployed). It's part of `planned-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): - **The hook:** the apply brief asked for `window.__app`, and the game exposes `state()`, `start()`, `launch()`, `press(key)` and `paddleTo(x)`. - **The judge's report** now has the required `play` record: `{"hook": true, "verdict": "pass", ...}`. Its evidence is a whole session played through the hook, quoting `state()` at each move: start, launch, a brick broken (`score 10`, `bricksLeft 47`), three balls lost to `game-over`, and `start()` back to a fresh game. Round 1 passed. A play-through that is `unclear` or `fail` failing 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.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#272
No description provided.