test(cli): give the in-process serve ordering case a 60s timeout (#5359)

The merge queue took PR #5381 out on `Test timed out in 5000ms` at
serve-tenancy-posture-gate.test.ts (queue run 30971902650, Test Core 3/3) — a
timeout, not a failed assertion.

Ten of the eleven cases in that file only inspect the refusal string and run in
0-3ms. The eleventh imports and runs the real `serve` command in-process: the
whole serve module graph plus a port-availability probe. It measures 2535ms on
an idle runner; on the queue's full-suite shard, sharing with the serve e2e
tests (that shard reported import 94.8s / tests 282s), it exceeded the 5s
default. The PR shards are lighter, so PR CI stayed green throughout.

Same posture as the existing `}, 60_000)` cases in this package
(utils/sqlite-occupancy.test.ts, utils/schema-migrate.deferred-ddl.integration
.test.ts) and as #4856's package-level testTimeout. Superficially the #4796
5000ms signature but a different cause: that family was the spec template suite,
already fixed by #4856.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VkPSGsX9o17MsGv3Lbxu2w

Author: claude

packages/cli/src/commands/serve-tenancy-posture-gate.test.ts

@@ -254,5 +254,17 @@ describe('the gate runs before serve does ANY boot work', () => {
     // The misattribution that made this issue expensive to diagnose is gone:
     // no warning blames a plugin for an environment-variable typo.
     expect(stderr).not.toContain('AuthPlugin failed to load');
-  });
+    // 60s, not the 5s default: unlike the ten message-only cases above, this one
+    // imports and runs the REAL serve command in-process — the whole serve
+    // module graph plus a port-availability probe. On a lightly-loaded PR shard
+    // that costs a moment; on the merge queue's full-suite runner, sharing a
+    // shard with the serve e2e tests (vitest reported import 94.8s / tests 282s
+    // for that shard), it blew the 5s default and this case timed out — queue
+    // run 30971902650, which is what took the PR out of the queue. Same posture
+    // as the existing `}, 60_000)` cases in this package
+    // (`utils/sqlite-occupancy.test.ts`, `utils/schema-migrate.deferred-ddl.
+    // integration.test.ts`) and as #4856's package-level `testTimeout`.
+    // Superficially the #4796 5000ms signature, but a different cause: that
+    // family was the spec template suite, already fixed.
+  }, 60_000);
 });