feat: Phase 10 multi-cluster / GitOps

[vrabbi]

Summary

• 10.4 — Explicit non-goal: state cross-cluster failover is out of scope #85 / 10.4 — Document that cross-cluster webhook failover is out of scope; each cluster is an independent install.
• 10.1 — Document CI pattern: convctl test+diff across many kubecontexts #82 / 10.1 — Copy-pasteable fleet CI: shell loop + GitHub Actions matrix for convctl diff --live and test --live per kubecontext.
• 10.2 — convctl multi-kubeconfig batch mode #83 / 10.2 — convctl test --live --contexts / --kubeconfig-dir aggregates one JUnit report (one suite per cluster); a single target keeps the existing report shape.
• 10.3 — GitOps examples (Flux/Argo) #84 / 10.3 — Flux and Argo examples for CRDs → ConversionWebhookServer → config, with KeepServingStale as the CD driftPolicy.

Closes #81
Closes #82
Closes #83
Closes #84
Closes #85

Test plan

• go test ./internal/cli/
• CI unit/lint/docs/e2e green
• CodeRabbit comments triaged

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 20 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

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 Plus

Run ID: 8c984e56-6810-480f-ad84-9acb347fdadb

📥 Commits

Reviewing files that changed from the base of the PR and between 3fea1ed and 03b8604.

📒 Files selected for processing (31)

• docs/architecture.md
• docs/cli.md
• docs/examples/index.md
• docs/faq.md
• docs/gitops/convctl-fleet.gha.yml
• docs/gitops/convctl-fleet.sh
• docs/gitops/fleet-ci.md
• docs/gitops/operator-sync.md
• docs/installation.md
• docs/limitations.md
• docs/operations/upgrade-runbook.md
• docs/roadmap.md
• examples/README.md
• examples/gitops/README.md
• examples/gitops/argo/README.md
• examples/gitops/argo/configs-application.yaml
• examples/gitops/argo/operator-application.yaml
• examples/gitops/configs/kustomization.yaml
• examples/gitops/configs/xrd.yaml
• examples/gitops/configs/xrdconversionconfig.yaml
• examples/gitops/flux/README.md
• examples/gitops/flux/clusters/kustomizations.yaml
• examples/gitops/flux/operator/helmrelease.yaml
• examples/gitops/flux/operator/helmrepository.yaml
• examples/gitops/flux/operator/kustomization.yaml
• internal/cli/fleet.go
• internal/cli/fleet_test.go
• internal/cli/report.go
• internal/cli/root.go
• internal/cli/test.go
• mkdocs.yml

---

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