chore(docs): Update docs to reflect support for macOS

[ekiefl]

I was expecting installation for macOS development to fail based on this note in the README:

Note: pixi install -a resolves all environments. This (currently) requires CUDA 12 and will fail on machines without it.

Instead pixi install -a succeeded, skipping the CUDA-only environments:

WARN Skipping environment(s) that do not support the current platform: boltz, boltz-analysis, boltz-dev, protenix, protenix-dev
✔ The following environments have been installed: default, analysis, analysis-dev, boltz-osx, protpardelle, protpardelle-dev, rf3, rf3-dev.

I see that macOS (arm64) landed in #255, so this PR updates the README to reflect that. I'm reading between the lines, but from what I gather macOS isn't supported as a first-class platform (no CUDA), just as a convenience for local development. I've tailored the language according to that assumption.

Relatedly, I noticed AGENTS.md is stale because it lists all the pixi environments but doesn't mention boltz-osx. I considered adding it but I think the proper solution is to avoid this "agentic doc debt" altogether (protpardelle is also missing) by pointing agents to the cmd pixi workspace environment list. Can file an issue / submit PR for this if requested.

[coderabbitai]

Warning

Review limit reached

@ekiefl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: f5c9b39a-6131-4ccb-bf8f-5a37ba81dc1b

📥 Commits

Reviewing files that changed from the base of the PR and between 62a226c and 4f0a73d.

📒 Files selected for processing (1)

• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[k-chrispens]

Thanks for this! The AGENTS.md update would also be much appreciated - it is probably due for a more comprehensive update, there are a few parts of the codebase that aren't referenced in it currently that ought to be. Pointing agents towards programmatic interactions with the code base is a perfect way to make sure it stays updated for the pixi envs!