Fix two flaky CI test failures

[theoephraim]

Two unrelated tests flaked in CI on 2026-08-07, both test-only fixes:

• nextjs fifo-sources: "never reads or watches FIFO sources..." hit vitest's default 5s timeout (5083ms) on a slow runner; the first import of next-env-compat pays the transform cost. Both tests in the suite now have an explicit 30s timeout.
• varlock cache-lock-crossproc: the SIGINT test asserted the lock dir was gone immediately after observing the child's exit. bun run can interpose a wrapper process, so the observed exit can race the actual holder's cleanup. The assertion now polls for up to 5s before failing.

[github-actions]

The changes in this PR will be included in the next version bump.

Bump files in this PR

• flaky-test-timeouts.md (view diff) (edit)

Click here if you want to add another bump file to this PR

---

This comment is maintained by bumpy.

[github-actions]

📦 Bundle size

no change to bundle size

Metric	main	This PR	Δ
Total dist	5010.6 KB	5010.6 KB	—
JS	1717.9 KB	1717.9 KB	—
Sourcemaps	3216.2 KB	3216.2 KB	—
Type defs	76.6 KB	76.6 KB	—

dist/ only; native binaries are versioned separately and not counted here.

[pullfrog]

✅ No new issues found.

Reviewed changes covering the test stabilization updates for the Next.js FIFO suite and Varlock cross-process cache-lock suite.

• FIFO test timeouts: Gives both FIFO source tests a 30 second budget for slow initial transforms while preserving their existing behavioral assertions.
• SIGINT cleanup polling: Waits for the process holder's lock cleanup after wrapper exit while retaining the exact final assertion that the lock directory is gone.
• Release metadata: Records test-only changes with no package version bumps.

  ^{｜ View workflow run ｜ Using azure/gpt-5.6-sol ｜ 𝕏}