[docs-agent] Update CLI documentation — rename Regional Platform to HyperFleet in docs

[redhat-chai-bot]

Automated Documentation Update

Changes Made

Renamed "ROSA Regional Platform" to "ROSA HyperFleet" in documentation prose and URLs across 5 files:

• README.md — project description, clone URL, cd command, directory tree
• docs/README.md — table description, GitHub links, reference implementation link
• docs/specs/references.md — API repo link updated
• docs/architecture/ARCHITECTURE.md — overview prose, cross-repo reference link
• docs/guides/DEVELOPMENT.md — clone URL, cd command, directory tree

Triggered By

Recent PRs (last 7 days):

• No code PRs merged in the CLI repo in the last 7 days

Platform repo #665 renamed all references from "ROSA Regional Platform" to "ROSA HyperFleet", but this CLI repo still had 20+ stale references in documentation.

Overall Documentation Validation:

• 12 prose/URL references to old project name fixed across 5 files
• Formatting standardized with prettier

Deliberately left unfixed:

• go.mod module path — changing would break all imports
• CloudFormation template descriptions in internal/cloudformation/templates/ — code, not docs
• Example output in docs/guides/DOCUMENTATION.md that matches actual CFN template defaults

Undocumented areas noted (for human review):

• docs/architecture/ARCHITECTURE.md uses 82 lines of ASCII box-drawing art instead of Mermaid diagrams — contradicts the project's Mermaid-only convention but converting is a larger task

/cc @ravitri @jmelis — please review these updates.

---

Generated by Chai Bot documentation update task (weekly validation).

[coderabbitai]

Warning

Review limit reached

@redhat-chai-bot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

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: Repository: openshift-online/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ab1a7d8c-f634-4876-9f73-a1a657a725b4

📥 Commits

Reviewing files that changed from the base of the PR and between 00c3e2a and 392043b.

📒 Files selected for processing (5)

• README.md
• docs/README.md
• docs/architecture/ARCHITECTURE.md
• docs/guides/DEVELOPMENT.md
• docs/specs/references.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign slopezz for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @redhat-chai-bot. Thanks for your PR.

I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.