chore(tooling): port upstream infra/tooling audit fixes

Ports the kept-file portions of the upstream infra audit-fix subset onto
the clean-slate template branch (auth-only shape; workspaces feature never
existed here, so its package.json edit is skipped):

- resolve the root playwright config in pnpm test:visual (S8)
- prune dead VERCEL_ENV from turbo.json globalEnv (S9)
- drop the duplicate chromium install in the storybook CI job (S10)
- wire scripts/**/*.test.mjs under a dedicated vitest runner
  (vitest.scripts.config.mjs + pnpm test:scripts + CI validate step);
  convert node:test imports to vitest keeping node:assert
- ignore *.tsbuildinfo repo-wide and untrack the committed build state
- align every @trpc/* range on ^11.18.0 so the workspace resolves to a
  single version (peer-warning-free install)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK

scripts/work/state-sync-guard.test.mjs

@@ -8,9 +8,10 @@ const GUARD = path.join(__dirname, "state-sync-guard.mjs");
 
 describe("state-sync-guard smoke", () => {
   it("exits 0 when run against the repo's current state (since main is in sync)", () => {
-    // Run the guard; if main's _state.json drifts, this test will fail and tell us.
-    execSync(`node "${GUARD}"`, { encoding: "utf8" });
-    // No assertion on output; the exit code is 0 if we got here without throwing.
-    expect(true).toBe(true);
+    // Run the guard; if main's _state.json drifts, execSync throws (non-zero
+    // exit) and this test fails with the guard's output.
+    expect(() =>
+      execSync(`node "${GUARD}"`, { encoding: "utf8" }),
+    ).not.toThrow();
   });
 });