Warn on daemon identity mismatches

[zackees]

Summary

• query /api/daemon/info before daemon-backed build/deploy/monitor/test-emu requests
• warn when the serving daemon has a different fbuild version, a different checkout/spawner scope, or a different cache identity/schema
• log the serving daemon identity at debug level for matched daemons

Closes #940

Scope note

This intentionally avoids changing default daemon port derivation. The low-risk slice makes cross-checkout collisions visible before the request is served by the wrong daemon; per-checkout endpoint isolation remains a broader behavior change.

Local validation

• soldr cargo fmt --all --check
• soldr --no-cache cargo test -p fbuild-cli daemon_identity_warning -> 5 passed
• soldr --no-cache cargo check -p fbuild-cli --all-targets
• soldr --no-cache cargo clippy -p fbuild-cli --all-targets -- -D warnings -> exit 0; repo still emits the existing clippy/Cargo MSRV config warning
• git diff --check

Normal soldr cargo test -p fbuild-cli daemon_identity_warning failed before running tests in soldr's embedded compile dispatch (early eof), so the validation used soldr --no-cache to bypass that local cache layer.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0f9e435a-feea-4920-8461-f01672ca1a16

📥 Commits

Reviewing files that changed from the base of the PR and between 7098660 and 67dd30a.

📒 Files selected for processing (4)

• crates/fbuild-cli/src/cli/build.rs
• crates/fbuild-cli/src/cli/deploy.rs
• crates/fbuild-cli/src/daemon_client.rs
• crates/fbuild-cli/src/daemon_client/identity.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/940-daemon-identity-warning

---

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