docs(cli): document bundle upload --auto-bump ai

[riderx]

Summary (AI generated)

• Document --auto-bump ai for bundle upload across CLI reference, commands, CI/CD, and channels docs
• Describe Workers AI delta-manifest classification, CLI reason log, and patch fallback when no previous Capgo version exists
• Keep existing major/minor/patch|fix/metadata levels and the --bundle incompatibility note

Motivation (AI generated)

Follow-up to #932 after the CLI gained Workers AI auto-bump. Customers need the ai level documented next to the other --auto-bump options.

Business Impact (AI generated)

Makes the new AI versioning path discoverable in docs and CI examples, reducing support friction for automated Capgo uploads.

Test Plan (AI generated)

• Confirm bundle.mdx shows --auto-bump ai example and option table text
• Confirm commands.mdx lists ai among levels
• Confirm CI/CD section includes the ai command and behavior note
• Confirm channels.mdx mentions ai and the patch fallback
• Spot-check customer-facing commands use npx @capgo/cli@latest

Generated with AI

Made with Cursor

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 5 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: ASSERTIVE

Plan: Pro

Run ID: 7d1fd4f3-13e3-4147-bed8-2f1141061f96

📥 Commits

Reviewing files that changed from the base of the PR and between 896b6ec and 9151892.

📒 Files selected for processing (4)

• apps/docs/src/content/docs/docs/cli/commands.mdx
• apps/docs/src/content/docs/docs/cli/reference/bundle.mdx
• apps/docs/src/content/docs/docs/getting-started/cicd-integration.mdx
• apps/docs/src/content/docs/docs/live-updates/channels.mdx

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_961acba2-33da-42b5-9dcf-58276a7329db)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cubic-dev-ai]

No issues found across 4 files

_{Re-trigger cubic}