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

[EffortlessSteven]

Motivation

• Clarify Amazon Kiro guidance by splitting IDE (OpenVSX extension) and CLI (workspace custom-LSP) workflows.
• Avoid requiring perllsp on PATH for IDE users because the VS Code/OpenVSX extension can auto-download the binary.
• Surface ambiguity around the Kiro CLI LSP config path and warn that Perl is not a built-in tree-sitter language in some Kiro CLI builds.
• Provide concrete verification and troubleshooting steps for both IDE and CLI users.

Description

• Rewrote docs/EDITORS/KIRO_SETUP.md to split Kiro IDE vs Kiro CLI, document installing EffortlessMetrics.perl-lsp-rs from OpenVSX, document optional manual perllsp binary settings, and include a recommended CLI lsp.json example with initialization_options and common extensions/project patterns.
• Updated docs/how-to/EDITOR_SETUP.md to prefer the OpenVSX extension for Kiro IDE in the editor matrix and to add an IDE-first + CLI custom-LSP quick-start.
• Added an Amazon Kiro troubleshooting subsection to docs/how-to/TROUBLESHOOTING.md covering IDE auto-download, manual perllsp checks, /code init guidance, /code status and /code logs commands, and the custom-LSP capability caveat.
• Fixed wording in docs/reference/CONFIG.md to use the canonical executable name perllsp and added an Amazon Kiro-specific config snippet and guidance for manual binary management.

Testing

• Ran cargo xtask fmt to format the repository and the command completed successfully.
• Manual inspection and local grep checks were used to verify the updated Kiro references and the editor matrix entries.

---

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 27 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: 345dad0d-f11f-4b3a-be2b-9b48b3ed2ac2

📥 Commits

Reviewing files that changed from the base of the PR and between 6099f6b and ed1aa81.

📒 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

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ed1aa81f5e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use where.exe in PowerShell verification commands

This PowerShell snippet will fail for many Windows users because where is a built-in alias for Where-Object, and PowerShell resolves aliases before external executables; as written, where perllsp invokes the cmdlet instead of where.exe, so the binary-path verification step does not work. Replace it with where.exe perllsp (or Get-Command perllsp) to keep the troubleshooting flow functional on PowerShell.

Useful? React with 👍 / 👎.

[EffortlessSteven]

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