chore(docs): sync test-count badges after land-wave

[YosefHayim]

User description

Summary

Post-land pnpm docs:gen badge sync after messy-repo MERGE wave.

Test plan

• pnpm docs:check
• pnpm test / e2e already green on tip

No product code changes.

---

CodeAnt-AI Description

Synchronize test-count badges and command reference documentation

What Changed

• Updated localized README badges and generated command summaries from 2,066 to 2,319 passing tests
• Documented Android release-note file support for builds and deployments
• Documented report schema version selection and Play version code selection

Impact

✅ Accurate test totals across project documentation
✅ Clearer Android release-note configuration
✅ Clearer report and Play release options

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	350676b	Aug 07, 2026 · 10:50	10:50

[changeset-bot]

⚠️ No Changeset found

Latest commit: 350676b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 52 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: f1fd5044-21b0-458a-9067-a6ea1022674a

📥 Commits

Reviewing files that changed from the base of the PR and between 3853412 and 350676b.

📒 Files selected for processing (11)

• README.de.md
• README.es.md
• README.fr.md
• README.ja.md
• README.ko.md
• README.md
• README.pt-BR.md
• README.ru.md
• README.zh-CN.md
• docs/commands.md
• llms.txt

---

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

[qodo-code-review]

PR Summary by Qodo

Sync docs badges and generated command docs after test-count change

📝 Documentation 🕐 10-20 Minutes

AI Description

• Refresh README/docs/llms test-count references to match current suite size
• Regenerate command reference tables to include newly documented CLI options
• Keep pnpm docs:check green after the merge wave

Diagram

graph TD
  Dev([Maintainer]) --> Gen(["pnpm docs:gen"]) --> Cmds["docs/commands.md"] --> Check(["pnpm docs:check"])
  Gen --> Readmes["README*.md"] --> Check
  Gen --> Llms["llms.txt"] --> Check

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Make the test-count badge dynamic (CI-derived)

• ➕ Eliminates manual drift after large merge waves
• ➕ Keeps READMEs accurate without regenerating docs
• ➖ Requires new CI job/artifact publishing and potentially a separate badge endpoint
• ➖ Badge availability may depend on CI reliability and caching

2. Stop publishing exact test counts (use a stable badge label)

• ➕ No churn in docs for routine test additions/removals
• ➕ Avoids frequent regeneration-only PRs
• ➖ Loses a concrete project metric that can be useful to readers
• ➖ Doesn’t prevent docs:check drift if other generated docs still change

Recommendation: For now, this PR’s approach (regenerate and sync derived docs) is the most practical and lowest-risk way to restore docs:check on tip. If badge churn becomes frequent, consider either switching to a CI-derived dynamic badge or removing the exact test-count from public docs to reduce regeneration-only changes.

Files changed (11) +14 / -11

Documentation (11) +14 / -11

README.de.mdUpdate German README test-count badge to 2319 +1/-1

Update German README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.de.md

README.es.mdUpdate Spanish README test-count badge to 2319 +1/-1

Update Spanish README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.es.md

README.fr.mdUpdate French README test-count badge to 2319 +1/-1

Update French README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.fr.md

README.ja.mdUpdate Japanese README test-count badge to 2319 +1/-1

Update Japanese README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.ja.md

README.ko.mdUpdate Korean README test-count badge to 2319 +1/-1

Update Korean README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.ko.md

README.mdUpdate main README test-count badge to 2319 +1/-1

Update main README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.md

README.pt-BR.mdUpdate pt-BR README test-count badge to 2319 +1/-1

Update pt-BR README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.pt-BR.md

README.ru.mdUpdate Russian README test-count badge to 2319 +1/-1

Update Russian README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.ru.md

README.zh-CN.mdUpdate zh-CN README test-count badge to 2319 +1/-1

Update zh-CN README test-count badge to 2319

• Synchronizes the tests-passing badge count from 2066 to 2319 so the README reflects current CI totals.

README.zh-CN.md

commands.mdRegenerate command reference (test count + new flags) +4/-1

Regenerate command reference (test count + new flags)

• Updates the headline test count from 2066 to 2319 and adds newly generated option rows for multiple commands (e.g., Android release notes path, report schema version, and explicit versionCode shipping).

docs/commands.md

llms.txtSync LLM doc command/test-count summary to 2319 +1/-1

Sync LLM doc command/test-count summary to 2319

• Updates the command summary line to reflect the new total tests count (2066 → 2319).

llms.txt

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}