ci: use smaller runners for control and publishing jobs

Draft
TH
8h ago
+3-3

Summary

Use Blacksmith's two-CPU Ubuntu 24.04 runner for three jobs that run shell, GitHub API requests, or a small Node redirect generator: the Apple status aggregator, closed-PR cancellation, and docs redirect publishing. The image stays the same, and test/build/device jobs keep their current sizes.

Three files, three runner-label changes. Follows Blacksmith's runner-sizing guidance; these jobs' source shows no parallel CPU workload. No broader resizing is proposed without utilization metrics. No linked issue.

Validation

Head: 7fd27eacfe1c4656e070db77fc6def0d96055b22. Base: 880cea7002c3fdb392a2900795ff45f23529aef6.

  • Full-repository pnpm format and git diff --check passed.
  • Independent review: no findings. After rebasing, git range-diff confirms the implementation patch is identical to the reviewed version.
  • Rebased onto #4475, which fixes the daemon-fixture guard timeout found during validation of the companion CI optimization.
  • pnpm check:affected --run --base 880cea7002c3fdb392a2900795ff45f23529aef6 --head 7fd27eacfe1c4656e070db77fc6def0d96055b22 --json: passed, exactCommit: true; 42 checks passed, 25 CI-owned checks skipped.
  • Coverage failed: unchanged coordinate.contract.test.ts error-taxonomy scenario exceeded 5 seconds. Coverage's runner and test sources are unchanged. Base CI passed. Focused instrumented base/head each passed six tests; both commands exited 1 on global coverage floors for the partial suite. Original timeout not reproduced; cause unproven. No CI retry or timeout increase applied.
  • Coverage remains blocked; cause unproven. Next diagnostic: fixture-phase timings under full coverage. Draft: Coverage is unresolved.
  • Apple validation passed: iOS/macOS succeeded, and the aggregator ran successfully on blacksmith-2vcpu-ubuntu-2404. Deployment and close-cancellation jobs await their normal triggers. Runtime/billing effects remain unmeasured.