chore: migrate CI to BuildPulse runners

[mhodzic93]

Summary

• Migrate all GitHub Actions workflows from public GitHub-hosted runners to BuildPulse runners
• Runner: bp-ubuntu-latest-x64-2x (2 vCPU, 8 GB RAM, 75 GB SSD)
• No functional changes — same Ubuntu environment, faster execution

What changed

All runs-on: ubuntu-latest (and ubuntu-22.04/ubuntu-24.04) replaced with runs-on: bp-ubuntu-latest-x64-2x

Prerequisites

• BuildPulse GitHub App must be installed on this org
• Runner tenant must be activated in BuildPulse
• bp-ubuntu-latest-x64-2x runner config must be added

[loera140]

Agent code review

Walkthrough

Swaps the ci-gate workflow's runner from GitHub-hosted ubuntu-latest to the BuildPulse-hosted label bp-ubuntu-latest-x64-2x. One-line change; no steps, permissions, or triggers modified. This is the only workflow in the repo, so the PR body's "all workflows" claim is consistent with the diff.

Findings

• No issues found.

Verdict

APPROVE. Pure infra runner-label swap with no functional changes to checkout/setup-node/npm ci/jest steps. No scope drift, no hallucinated APIs (custom runner labels are provisioned out-of-band), no test weakening, no prompt-injection content. If the BuildPulse runner pool is misconfigured the job will simply queue and fail to pick up — a reversible, observable failure mode, not a correctness risk.

Confidence

HIGH — full file read; only one workflow exists in the repo so cross-file impact is bounded.