test(ci): count the windows runner-selector job in the bounded-jobs gate

The self-hosted-runner selector landed with its own 2-minute bound, so
the hardening test now asserts all three bounded jobs instead of failing
on the third timeout-minutes entry.

Author: lidge-jun

tests/ci-workflows.test.ts

@@ -34,11 +34,13 @@ describe("GitHub Actions hardening", () => {
     // The cross-platform `test` job sits at 20 minutes: a green Windows run measured
     // 11.8 min against 4.6 on Linux, and the previous 12-minute ceiling left ~12s of
     // margin, so runner variance rather than the code decided the verdict (#717).
-    // `npm-global-smoke` stays at 8; it finishes in 1-2 minutes.
+    // `npm-global-smoke` stays at 8; it finishes in 1-2 minutes. The windows-runner
+    // selector job is bounded at 2 minutes — it only picks a label.
     expect(count(workflow, "timeout-minutes: 20")).toBe(1);
     expect(count(workflow, "timeout-minutes: 8")).toBe(1);
-    // Both jobs must stay bounded — an unbounded job can hang a queue for hours.
-    expect(count(workflow, "timeout-minutes:")).toBe(2);
+    expect(count(workflow, "timeout-minutes: 2\n")).toBe(1);
+    // Every job must stay bounded — an unbounded job can hang a queue for hours.
+    expect(count(workflow, "timeout-minutes:")).toBe(3);
     expect(workflow).toContain("actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0");
     expect(workflow).toContain("oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6");
     expect(workflow).toContain("actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e");