The judge's chip says 'fail · 1 of 8' and only the transcript says which: a judge panel like Review findings #315

Closed
opened 2026-10-29 19:23:05 -04:00 by cmoriarty · 1 comment
Owner

What happens
Run 147's judge step reads fail · 1 of 8. Which criterion failed, and why, is only in its transcript (B6: on a 390×844 phone the canvas stretches 2.89× vertically). The review steps have the Review findings panel (#288); the judge has nothing like it, though its report is already structured. .osf/fix/r<N>/judge.json holds the verdict and summary, how it played (play), the pages it opened with their console errors, and each criterion's verdict, evidence and screenshots.

Fix
A judge panel under the judge's transcript, opened from its chip as a review chip opens its findings:

  • the round's verdict and summary;
  • the play-through: the hook, its verdict, what it did;
  • failed and unclear criteria first, each with its text, evidence and screenshots; the passed ones folded;
  • the pages it opened, with their console errors.

Served like GET /api/runs/{id}/review/{round}, from the round's report. With several rounds, a failed criterion says whether the next round passed it.

Done when
From the judge's chip, run 147's panel shows B6 failed, with its evidence and screenshot, without opening the transcript; a browser spec covers the panel.

**What happens** Run 147's judge step reads `fail · 1 of 8`. Which criterion failed, and why, is only in its transcript (B6: on a 390×844 phone the canvas stretches 2.89× vertically). The review steps have the Review findings panel (#288); the judge has nothing like it, though its report is already structured. `.osf/fix/r<N>/judge.json` holds the verdict and summary, how it played (`play`), the pages it opened with their console errors, and each criterion's verdict, evidence and screenshots. **Fix** A judge panel under the judge's transcript, opened from its chip as a review chip opens its findings: - the round's verdict and summary; - the play-through: the hook, its verdict, what it did; - failed and unclear criteria first, each with its text, evidence and screenshots; the passed ones folded; - the pages it opened, with their console errors. Served like `GET /api/runs/{id}/review/{round}`, from the round's report. With several rounds, a failed criterion says whether the next round passed it. **Done when** From the judge's chip, run 147's panel shows B6 failed, with its evidence and screenshot, without opening the transcript; a browser spec covers the panel.
Author
Owner

Confirmed on production (1fc0f22, PR #319); closing.

  • Run 153 (the mirrored-keys fault for #269): the chip fail · 2 of 6 failed opens the panel, which reads 2 failed · 0 unclear · 4 passed. It shows the play-through through window.__app. The failed criterion A4 is open with its evidence (ArrowLeft held 0.5s: paddle.x 390.0 -> 660.0), next round: pass, and its screenshots as thumbnails.
  • Run 152 (the Breakout project's first item): pass · 18 of 18, with the play-through, the game over at 690, and a bot that cleared all 50 bricks.
**Confirmed on production (1fc0f22, PR #319); closing.** - **Run 153** (the mirrored-keys fault for #269): the chip `fail · 2 of 6 failed` opens the panel, which reads `2 failed · 0 unclear · 4 passed`. It shows the play-through through `window.__app`. The failed criterion A4 is open with its evidence (`ArrowLeft held 0.5s: paddle.x 390.0 -> 660.0`), `next round: pass`, and its screenshots as thumbnails. - **Run 152** (the Breakout project's first item): `pass · 18 of 18`, with the play-through, the game over at 690, and a bot that cleared all 50 bricks.
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#315
No description provided.