[docs-agent] Update CLI documentation — add cluster/OIDC/login commands, convert ASCII to Mermaid

[redhat-chai-bot]

Automated Documentation Update

Changes Made

12 files changed — CLAUDE.md, README.md, ARCHITECTURE.md, DEVELOPMENT.md, and 8 files with Prettier formatting fixes.

Triggered By

Recent PRs (last 7 days):

• chore(deps): bump ubi9/go-toolset from 1780490457 to 1781070178 #76 - Bump ubi9/go-toolset (dependabot) — No doc impact

Overall Documentation Validation:

• CLAUDE.md: Added 3 missing command groups (cluster, clusteroidc, login) to the commands listing. Added internal/config/ to Key Directories.
• README.md: Documented all 3 undocumented command groups — cluster management (create, list, kubeconfig, get-token), cluster-oidc (create, delete, list), and login. Updated Project Structure tree to include cluster/, clusteroidc/, login/, internal/config/, internal/services/cluster/, internal/services/clusteroidc/. Converted Architecture section ASCII diagram to Mermaid.
• ARCHITECTURE.md: Converted 2 large ASCII diagrams (Direct CloudFormation flow, Lambda mode flow) to Mermaid. Added cluster, clusteroidc, and login to CLI Layer section. Added cluster and clusteroidc services plus config layer to Service Layer section.
• DEVELOPMENT.md: Updated Project Structure tree with new directories.
• Prettier: Fixed formatting across all 12 markdown files.

Undocumented areas noted (for human review):

• README Features section could be expanded to highlight cluster lifecycle and OIDC management as primary features
• docs/guides/DEVELOPMENT.md ASCII art for workflow diagrams could be converted to Mermaid in a follow-up

Supersedes PR #80 (which covered a subset of these changes).

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

---

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

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 59 minutes and 59 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: openshift-online/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f0b68e13-16fc-4481-bdd7-6cea9b324158

📥 Commits

Reviewing files that changed from the base of the PR and between 94e5fc1 and abcccad.

📒 Files selected for processing (12)

• .github/ISSUE_TEMPLATE/bug_report.md
• .github/ISSUE_TEMPLATE/feature_request.md
• 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
• test/localstack/README.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 jmelis 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.

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

[redhat-chai-bot]

Auto-closing: this documentation update was not reviewed within 3 days and has been superseded by newer work. No CLI documentation changes were needed this cycle.

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