The e2e pins are in the PR (features/the_missing_chords.feature, eight
scenarios, red-first). This gist is the look of it: five screenshots taken by
driver.ts against a dev server reading a copy of the suite's good corpus,
the chords pressed by a headless Chromium rather than narrated. The PNGs
themselves render on the PR — gists are text-only, so they live at
juspay/olai#485 (comment) and are
mirrored below via imgur.
Alt+. with the caret in install → house.olai/#install — breadcrumb house.olai › kitchen remodel #home, the node's own page drawn:
Alt+, with the caret in handles on that page → house.olai/#kitchen — the zoom pops one level, install is a row again:
Ctrl+Space with the caret in install — the gutter triangle turns and the branch folds away:
Ctrl+O on house.olai — the finished rows appear inline, struck through; a second press hides them:
⌘⇧↑, platform pinned to a Mac, caret in pick the knobs — the row moves above pick the hinges, the header's 1 uncommitted counting the write:
The Mac pinning is an init script answering MacIntel for
navigator.platform — the same door the suite's ⌘⇧ scenario walks through,
since every browser the suite runs is on one OS.
# in the PR's worktree:
just build-client
# serve a copy of packages/tests/fixtures/good on port 0 (the suite's own
# support/serve.sh spelling works), then:
nix develop .#e2e -c bun driver.ts "$OLAI_URL"
sha256sum /tmp/opencode/evidence/shots/*.png # matches shots.sha256
(driver.ts writes the five PNGs to /tmp/opencode/evidence/shots/, one per
chord. Adjust the paths at the top of the file if you parked yours elsewhere.)
See shots.sha256. If a frame here and yours differ, what you are looking at
is what a reviewer should also look at.




