ci(ecosystem): pin Node 24.15.0 for Playwright-using projects

`npx playwright install chromium` wedges after the chromium zip download
reaches 100% when run under Node 24.16.0+ with Playwright < 1.60.0
(microsoft/playwright#40724, fixed in 1.60.0 via #40747). The hang is
silent and unrecoverable — the runner only knows about it via the 10-min
job timeout. We've been losing every nightly E2E run on the same 4
projects (vibe-dashboard, vitepress, tanstack-start-helloworld,
vitest-playwright-repro) because vp env happens to pick 24.16.0 for them.

Pin those projects to the last known-good Node minor via .node-version
written before `vp install`. This is a workaround; remove it once each
project ships a Playwright >= 1.60 bump.

Author: fengmk2

ecosystem-ci/patch-project.ts

@@ -24,6 +24,20 @@ const cwd = directory ? join(repoRoot, directory) : repoRoot;
 // run vp migrate
 const cli = process.env.VP_CLI_BIN ?? 'vp';
 
+// Playwright < 1.60.0 wedges `npx playwright install chromium` after the
+// download bar reaches 100% when run under Node 24.16.0+ (microsoft/playwright#40724,
+// fixed in 1.60.0 via microsoft/playwright#40747). Pin these projects to the last
+// known-good Node minor until they ship a Playwright >= 1.60 bump.
+const playwrightHangProjects = new Set([
+  'vibe-dashboard',
+  'vitepress',
+  'tanstack-start-helloworld',
+  'vitest-playwright-repro',
+]);
+if (playwrightHangProjects.has(project)) {
+  await writeFile(join(repoRoot, '.node-version'), '24.15.0\n', 'utf-8');
+}
+
 if (project === 'rollipop') {
   const oxfmtrc = await readFile(join(repoRoot, '.oxfmtrc.json'), 'utf-8');
   await writeFile(