ci: stop pinning remote-daemon macOS tests to the macOS 26 pool

[teamleaderleo]

Summary

remote-daemon-macos-tests runs go -C daemon/remote test ./... twice, once with -race. It uses no Xcode and no GUI, so any Mac can run it. It was pinned to MACOS_RUNNER_26 (Blacksmith 26), the pool that pull-request app-host work queues on. At 03:37Z it was one of the jobs waiting on that pool; on #14107 it had been queued since 02:29Z.

It now uses the same routing as the other pull-request macOS jobs, such as cli-pipe-regressions:

• pull requests: MACOS_RUNNER_PR (fallback blacksmith-6vcpu-macos-15)
• every other event: MACOS_RUNNER_15 under paid overflow, otherwise blacksmith-6vcpu-macos-15
• workflows running in a fork's own repository: hosted macos-15, as before (ci: run fork pull-request workflows on GitHub-hosted runners #14023)

The background lane (MACOS_RUNNER_BACKGROUND) would fit this job better, but check_background_macos_lane does not allow it in a workflow_call workflow that pull requests reach.

Testing

• tests/test_ci_self_hosted_guard.sh, tests/test_ci_fork_runner_routing.py, tests/test_ci_change_areas.py, tests/test_runner_label_policy.py and tests/test_ci_linux_guard_routing.py pass.
• actionlint is clean on remote-daemon.yml.

Checklist

• I added or updated tests for behavior changes (routing only; the existing guards cover it)
• I updated docs/changelog if needed (none needed)

🤖 Generated with Claude Code

https://claude.ai/code/session_01EduXdN9PKnGsMQztJK7WeE

---

Generated by Claude Code

---

Summary by cubic

Stops routing remote-daemon-macos-tests to the contended macOS 26 pool, which was causing long queue times on pull requests.

The job runs plain go test with no Xcode or GUI, so it now follows the same routing as the other pull-request macOS jobs: MACOS_RUNNER_PR (fallback blacksmith-6vcpu-macos-15) on pull requests, blacksmith-6vcpu-macos-15 on other events, and hosted macos-15 on forks.

^{Written for commit 38f1868. Summary will update on new commits.}

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Repository: manaflow-ai/cmux/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: d08a51f4-1efd-476a-b9f7-cab37d4e4630

📥 Commits

Reviewing files that changed from the base of the PR and between 1ba6d77 and 38f1868.

📒 Files selected for processing (1)

• .github/workflows/remote-daemon.yml

 ______________________________
< Blink twice if you're a bug. >
 ------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}