docs(kiro): clarify IDE vs CLI setup paths (#0000)

[EffortlessSteven]

Motivation

• The existing Kiro guide mixed IDE and CLI behaviors, incorrectly referenced the VS Code Marketplace instead of OpenVSX, and demanded perllsp on PATH for IDE users.
• The CLI config path and behavior for custom LSPs were asserted too rigidly despite upstream variation and known client-initiated-request limitations for non-built-in languages.

Description

• Rewrote docs/EDITORS/KIRO_SETUP.md to separate Kiro IDE (OpenVSX extension) and Kiro CLI (workspace custom LSP) flows and added explicit IDE settings and optional manual-binary guidance.
• Updated docs/how-to/EDITOR_SETUP.md to prefer OpenVSX EffortlessMetrics.perl-lsp-rs for the IDE and to document the CLI custom-LSP verification expectation.
• Fixed binary naming and added an Amazon Kiro subsection to docs/reference/CONFIG.md that shows perllsp usage and an example lsp.json entry.
• Added a Kiro-specific troubleshooting block to docs/how-to/TROUBLESHOOTING.md that covers IDE auto-download vs manual perllsp, /code init guidance for the CLI, restart/status/log commands, and a caveat that Perl is a custom language in some Kiro CLI builds.

Testing

• Ran git diff --check and it passed.
• Verified repository state with git status --short and committed the four modified files.
• Created PR metadata via the local PR helper (title/body present) for review.

---

Codex Task

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 12 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1d35e566-78e0-4133-a028-deafab717713

📥 Commits

Reviewing files that changed from the base of the PR and between 0c6e164 and bd15e44.

📒 Files selected for processing (4)

• docs/EDITORS/KIRO_SETUP.md
• docs/how-to/EDITOR_SETUP.md
• docs/how-to/TROUBLESHOOTING.md
• docs/reference/CONFIG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/revise-kiro-guide-for-clarity-ymdprz

---

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 and usage tips.}

[EffortlessSteven]

Closing as duplicate of #7070 - consolidating duplicate kiro documentation PRs