ci: locate where the e2e account var is stripped (step shell vs vitest main)

test.env forwarding did not help, so the account var is likely lost before the
vitest main process. Log the var lengths in the CI step shell and at vite config
load to pinpoint where it disappears. Temporary.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019wnwcxjavdb2xys8XGZora

Author: Brooooooklyn

.github/workflows/ci.yml

@@ -54,6 +54,10 @@ jobs:
       - run: vp exec playwright install chromium
         if: ${{ contains(matrix.os, 'windows') }}
 
+      # TEMP diagnostic (remove after): confirm the step shell has all three vars before `vp run`.
+      - name: e2e env in step shell (debug)
+        run: node -e "console.log('[[STEP]] token', (process.env.VOID_E2E_CF_TOKEN||'').length, 'account', (process.env.VOID_E2E_CF_ACCOUNT_ID||'').length, 'runid', (process.env.VOID_E2E_RUN_ID||'').length)"
+
       - run: vp run test:all
 
   done:

vite.config.ts

@@ -13,6 +13,12 @@ const e2eWorkerEnv = {
   VOID_E2E_CF_ACCOUNT_ID: process.env.VOID_E2E_CF_ACCOUNT_ID ?? '',
   VOID_E2E_RUN_ID: process.env.VOID_E2E_RUN_ID ?? '',
 };
+// TEMP diagnostic (remove after): does the vitest MAIN config process have the vars? If account is 0
+// here while the CI step shell had 32, the env is filtered before vitest (in `vp run`), so test.env
+// cannot recover it.
+console.error(
+  `[[CFG]] token=${(process.env.VOID_E2E_CF_TOKEN ?? '').length} account=${(process.env.VOID_E2E_CF_ACCOUNT_ID ?? '').length} runid=${(process.env.VOID_E2E_RUN_ID ?? '').length}`,
+);
 
 // Windows CI runners are 2-3x slower for builds and server startup.
 const ciTimeoutScale = process.platform === 'win32' ? 3 : 1;