devops(ci): fix the upstream report upload and move off Node 20

[b1zya]

The weekly playwright-cli watch failed in run 36435694536 (and the same way in run 35604583489): the pull-request job died on Artifact not found for name: playwright-cli-report.

Cause

actions/upload-artifact@v4 defaults to include-hidden-files: false, and the report lives in .roll/. The track job logged No files were found with the provided path: .roll/. No artifacts will be uploaded. and, because the step had if-no-files-found: ignore, still finished green. The branch track-playwright-cli_74354ec was pushed and the CI matrix passed on it, but no pull request was ever opened.

Fix

• upstream-playwright-cli.yml, upstream-roll.yml: include-hidden-files: true, and if-no-files-found: error so a missing report fails the step that should have produced it instead of the job downstream.
• upstream-roll.yml had the same bug. It never fired because 1.63.0 was rolled by hand (chore: roll patchright-core to 1.63.0 #5) and nothing newer is on npm yet, but it would have failed the first automatic roll the same way.
• stealth-online.yml uploads .patchright-cli/, also a dot directory, so its screenshots were never uploaded either.

What the watch found upstream (655530f -> b85c7a7, playwright-cli 0.1.20-0.1.22)

Verdict review: tests/integration/core.spec.ts is unchanged upstream; only files we rewrote moved (README, release skill, package.json). Every new feature comes from playwright-core 1.64.0-alpha: webmcp-list/webmcp-call, open --idle-timeout with a 1 h default for headless sessions, set-color-scheme/set-media and the other emulation commands, video-start --fps/--cursor, find --filename. None of that reaches us until patchright-core 1.64.0 is out (the latest is 1.63.0), so there is nothing to port now. After merging this, a manual run of the watch opens the bookkeeping PR for b85c7a7.

Verification of the current main (patchright-core 1.63.0)

• npm run check: clean, no drift
• npm run upstream:verify: patchright-core 1.63.0 = Playwright v1.63.0 client, vendor/ pristine
• npm test on Windows with real Chrome: 146 passed (unit, integration, stealth)
• the taskkill call now has windowsHide: true, matching the removal of the console-flash paragraph in chore: roll patchright-core to 1.63.0 #5

Second commit: off Node 20

Node 20 reached end of life in April 2026, and every run warned that the @v4 actions target Node 20 and are forced onto Node 24.

• CI matrix: Node 22 and 24, the two supported LTS lines (macOS keeps skipping the floor version, as it did with 20).
• The floor follows what CI tests: engines >=22, README, the skill and the esbuild target.
• checkout v7, setup-node v7, upload-artifact v7, download-artifact v8, all on Node 24. Their breaking changes do not touch us: checkout keeps the token in a separate file but git push still uses it, setup-node's automatic cache is moot with an explicit cache: npm, and the artifacts are still zipped, so the download digest check and unzip behave as before.

Locally: npm run check clean, 120 unit tests passed on Node 24.

🤖 Generated with Claude Code