Remove the runner's openssl@1.1 link before the Homebrew canary install

[ben-dev-au]

Why

• The Homebrew canary has failed since 28 Sep: `brew install` pours the fnd bottle, then exits 1 on `Could not symlink bin/openssl`.
• The macos runner images hand-link the disabled `openssl@1.1` over `bin/openssl`.
• Same image, different result: on 21 Sep brew overwrote that link with a warning; newer brew (`setup-homebrew@main`) fails the link step instead.
• Not user-facing: a user's Homebrew has no `openssl@1.1`.

Change

• New step deletes `bin/openssl` only when it points at `openssl@1.1`. `brew unlink` does not own the link (0 symlinks removed).
• Homebrew job moves to `macos-15`: Homebrew treats macOS 14 as Tier 3 and no longer builds bottles for it. macos-15 pours the same `arm64_sonoma` bottle a Sequoia user gets.

Verified

• Dispatched canary on this branch: all channels green, Homebrew reports exactly `1.0.1` (run).
• Negative control: macos-15 without the step still failed on the same link (run).
• The 5 Oct scheduled failure was runner capacity (no job acquired), not this.

Fixes #163

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 8bbd0b35-b228-4b2b-aed9-5d86cb149593

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}