chore: remove stale standalone-zccache references (#855)

[zackees]

Four mechanical sites cleaned up per #855:

1. ci/docker-mac-cross/Dockerfile — for-loop dropped zccache zccache-daemon zccache-fp. soldr 1.12.11+ doesn't ship them; the loop would silently no-op past SOLDR_VERSION=0.7.59.
2. .github/workflows/template_build.yml — removed Reset zccache daemon after cache warm step. No standalone zccache-daemon process exists post-embedded-zccache; the daemon lifecycle is owned by soldr.
3. setup.py docstring — updated to describe the embedded-zccache architecture (RUSTC_WRAPPER = soldr / zccache-soldr shim, which talks to soldr-daemon's embedded zccache).
4. crates/fbuild-build/src/compile_database/tests/cache_wrapper.rs — added a doc comment to test_strip_zccache_wrap_mode marking it as a backward-compat parse assertion for legacy command-line shapes (test still passes; the shape just shouldn't show up in new code paths).

References

• soldr embedded-zccache transition: soldr#977, soldr#980 L1, soldr#1081
• Audit issue: Stale standalone-zccache references in CI / Docker / docs / tests (post-embedded-zccache transition) #855 (no-op-today smoking guns enumerated there)

Verification

• grep -rE 'zccache-daemon|zccache\.exe|zccache-fp' --include='*.yml' --include='*.py' --include='Dockerfile*' ci/ .github/ — only matches are the new explanatory comments documenting the deprecation (intent matches Stale standalone-zccache references in CI / Docker / docs / tests (post-embedded-zccache transition) #855's acceptance criterion).
• soldr cargo check -p fbuild-build clean.
• Legacy parse test (test_strip_zccache_wrap_mode) still asserts the same invariant — just labeled as backward-compat.

Closes #855

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 38 seconds

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: 524047d4-a3ec-42d8-bd02-0dfe01c5bac1

📥 Commits

Reviewing files that changed from the base of the PR and between 9e52375 and ce5cdf9.

📒 Files selected for processing (4)

• .github/workflows/template_build.yml
• ci/docker-mac-cross/Dockerfile
• crates/fbuild-build/src/compile_database/tests/cache_wrapper.rs
• setup.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/855-stale-zccache-refs

---

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