Game UI reshape — Peregrine — Test ChecklistPlan: Game UI reshape — Peregrine (2026-08-08-game-ui-reshape.md)

0 tested
Loading
Sending results back. Click Download results (saves a .md to Downloads) and Download screenshots, then run /cr-testing import — it reads the notes and screenshots and folds them into your plan tasks. Or use Copy for Claude and paste into chat — any screenshots are also saved to ~/Downloads so Claude Code can read them by the filenames in the report. Finished a section but want to keep going? Each section header has its own Copy for Claude button — hand off just that section's results (and its screenshots) so Claude can start fixing while you move on to the next section. Everything you enter is auto-saved in this browser, so you can close and resume anytime. Add a screenshot to any step by dragging an image, clicking the box, or pasting (⌘V) while it is focused. Purple blocks are Claude's responses to an earlier round of results — retest steps for the fixes appear in a follow-up section at the bottom of the page.
Why this page is longer than the plan's two verification tasks. None of Slices 0–3 has been verified on screen — Claude could launch the app and screenshot it, but could not click (no Accessibility permission for osascript), so every behavior below was confirmed by reading code, not by using it. Three bugs were already found that way; this is the pass that catches what reading cannot.

Not built, do not test: list reorder. It has no drag affordance anywhere in the document, and the unused model API that implied otherwise has been removed. Add and remove are wired; reorder is not.

Updated 14 August. Slices 0–3 are committed on master and in sync with origin. Since this page was written, other work landed on top of the same renderer: a schema field can now declare display (headline / chip / note) to draw an object_list as claim rows instead of labelled rows. That is used only by the traveler category (The Travelers guide), never by Peregrine — but both go through the one view, so Phase E checks the two layouts have not broken each other.