[SID-6921]

What this changes

print.mjs's chromePath() now also looks for a browser under %LOCALAPPDATA%\ms-playwright (the directory npx playwright install writes to on Windows), the same way capture.mjs, drive.mjs and turn-check.mjs already do.

Why

All four scripts carry their own copy of chromePath(). Three of them (capture.mjs, drive.mjs, turn-check.mjs) were given a Windows Playwright fallback in #75. print.mjs was added later in #126 from an older copy of the function and never got that block, so on a Windows machine that only has Playwright's Chromium (no system Chrome or Edge installed), every other script finds a browser and print.mjs alone fails with No Chrome found. Set CHROME_PATH to a Chrome or Chromium binary.

Confirmed with a repro that extracts each file's chromePath() and runs it against a fake home directory containing only a Playwright Chromium cache (no system Chrome/Edge):

scripts/capture.mjs    -> .../AppData/Local/ms-playwright/chromium-1234/chrome-win/chrome.exe
scripts/drive.mjs      -> .../AppData/Local/ms-playwright/chromium-1234/chrome-win/chrome.exe
scripts/print.mjs      -> undefined (no Chrome found)        # before this fix
scripts/turn-check.mjs -> .../AppData/Local/ms-playwright/chromium-1234/chrome-win/chrome.exe

After the fix, print.mjs matches the other three.

Tests

scripts/chrome-path-parity.test.mjs asserts every chromePath() in the four files contains the Windows Playwright lookup. It fails on main (only print.mjs is missing it) and passes with this change:

# before: # tests 1 # pass 0 # fail 1
# after:  # tests 1 # pass 1 # fail 0

I also ran the full suite (node --test scripts/*.test.mjs) before and after on a Linux machine: the same 6 pre-existing failures (the react-* tests, which need the test_deps npm install from CI, and one drive test that needs a real Chrome binary) appear on a clean checkout and with this change; nothing new fails.

Checks

• Every example rebuilds, and git status --short shows only the changes I meant. (No example or kit change.)
• No comments in code.
• Kit changes are opt-in. Not applicable: no kit/ change.
• I built and looked at both themes. Not applicable: no visual change.
• Figures with pipes, cables or round parts. Not applicable: no figure change.
• node scripts/lines.mjs. Not applicable: no figure change.
• Shaders: not touched.
• 3D: not touched.
• Every number in the figure, the readout, the caption and the docs is true.
• A line under Unreleased in CHANGELOG.md.

Screenshots

No visual change.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.