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

[EffortlessSteven]

Motivation

• Kiro IDE and Kiro CLI use different extension/config mechanisms and the previous guide conflated them, causing incorrect setup advice.
• The docs incorrectly referenced the VS Code Marketplace and required perllsp on PATH for IDE users, which contradicts the extension's auto-download behavior.
• The CLI config path wording was brittle because different Kiro builds/examples create either a project-root lsp.json or .kiro/settings/lsp.json.
• Kiro CLI does not list Perl as a built-in tree-sitter language so custom-LSP behavior for Perl must be caveated and verified per-installation.

Description

• Split the Kiro guide into explicit IDE vs CLI flows and rewrote docs/EDITORS/KIRO_SETUP.md to document the two distinct setup paths.
• Updated docs/how-to/EDITOR_SETUP.md to change the Amazon Kiro table and minimal guidance to prefer the OpenVSX EffortlessMetrics.perl-lsp-rs extension for Kiro IDE and note CLI custom-LSP configuration for perllsp --stdio.
• Fixed naming and added an Amazon Kiro subsection in docs/reference/CONFIG.md to use the canonical perllsp binary name and show IDE/CLI configuration examples and the safer /code init wording.
• Added Kiro-specific troubleshooting guidance and a Kiro CLI caveat to docs/how-to/TROUBLESHOOTING.md explaining verification commands, logs, and that some client-initiated requests for custom non-built-in languages may not be forwarded.

Testing

• Ran cargo xtask fmt to format the repo and the task completed successfully.

---

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 20 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: b6fd6188-eb23-447d-a154-f59a7c032753

📥 Commits

Reviewing files that changed from the base of the PR and between 3900d44 and 6b103c2.

📒 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-u736di

---

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