[docs-agent] Fix stale naming, missing entries, and ASCII diagrams

[redhat-chai-bot]

Automated Documentation Update

Changes Made (12 files, +300/−213)

High-priority fixes:

• CLAUDE.md: Added 3 missing command directories (cluster, clusteroidc, login) and their service layers
• README.md: Renamed "ROSA Regional Platform" → "ROSA HyperFleet" and fixed clone URL
• docs/architecture/ARCHITECTURE.md: Updated naming ("ROSA Regional HCP" → "ROSA HyperFleet HCP"), converted ASCII art diagrams to Mermaid (project convention), added missing CLI commands (cluster, clusteroidc, login) to Components section
• Removed reference to non-existent make test-localstack-verbose target

Medium-priority fixes:

• docs/guides/DEVELOPMENT.md: Fixed build path (./rosactl → ./bin/rosactl), updated naming
• docs/README.md: Updated stale GitHub URLs from rosa-regional-platform-* → rosa-hyperfleet-*
• docs/guides/DOCUMENTATION.md: Fixed stale example output naming
• docs/specs/references.md: Fixed naming and typos ("compoent" → "component", "deployes" → "deploys")
• Applied Prettier formatting to all markdown files

Triggered By

Recent PRs (last 7 days): None in this repo.

Overall Documentation Validation:

• CLAUDE.md: Added 3 missing command directories
• ARCHITECTURE.md: Converted ASCII diagrams to Mermaid, added missing commands
• README.md: Fixed stale naming and broken references
• Multiple docs: Fixed stale "Regional Platform" naming across 8 files

---

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: 25580ae2-8ded-4c73-8c2a-6c42ae754018

📥 Commits

Reviewing files that changed from the base of the PR and between 00c3e2a and 048c1f3.

📒 Files selected for processing (9)

• CLAUDE.md
• README.md
• docs/README.md
• docs/architecture/ARCHITECTURE.md
• docs/guides/DEVELOPMENT.md
• docs/guides/DOCUMENTATION.md
• docs/guides/VERSIONING.md
• docs/specs/reference-gist-1.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 theautoroboto 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.

[redhat-chai-bot]

Auto-closing: this documentation update was not reviewed within 3 days. If the changes are still relevant, a new PR will be opened in a future run.