docs: compact version support matrix with single-row 'All platforms' format

[shenxianpeng]

Problem

The version support matrix had 31 rows: each of the 5 original tools was expanded into 6 individual platform rows (Linux x86-64, Linux ARM64, macOS x86_64, macOS ARM64, Windows x86-64, Windows ARM64), even though coverage was identical across all platforms. Newly added tools (llvm-cov, llvm-profdata, llvm-symbolizer, clang-scan-deps) followed a compact single-row format, creating inconsistency.

Solution

Unified the entire table into a compact single-row-per-tool format using All platforms¹, with a footnote explaining the six platforms. This is possible because every tool has identical coverage across all supported platforms.

Before: 31 rows (5 tools × 6 platforms + 1 extra for header)
After: 10 rows (9 tools + 1 header)

Changes

• Collapsed clang-format, clang-tidy, clang-query, clang-apply-replacements, clang-include-cleaner from 6 platform rows each → single row
• Added 4 new rows for llvm-cov, llvm-profdata, llvm-symbolizer, clang-scan-deps (already in build.py TOOLS, missing from docs)
• Added footnote ¹ defining the six supported platforms
• Used bold text + 🆕 badge for the newly listed tools

Note

clang-include-cleaner retains its ❌ markers for LLVM ≤17 — this version constraint is visible directly in the row without needing extra notes.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 37 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 88596522-c318-41dd-8f58-7f8f7342cfd5

📥 Commits

Reviewing files that changed from the base of the PR and between e6fa8f6 and fd7f18d.

📒 Files selected for processing (1)

• README.md

---

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