docs: improve shell integration troubleshooting guidance

[KJ7LNW]

Context

Updates shell integration documentation with comprehensive troubleshooting guidance based on recent user feedback and investigations.

Implementation

• Added detailed instructions for checking debug logs and interpreting preOutput
• Documented VSCode version-specific issues and workarounds (particularly v1.98+)
• Added guidance for using the terminal integration test extension
• Clarified terminal command delay impact and recommended values
• Improved WSL integration method documentation with clearer distinctions
• Added environment-specific considerations for troubleshooting

How to Test

1. Review the updated shell-integration.md documentation
2. Verify technical accuracy of troubleshooting steps
3. Check formatting and link validity
4. Ensure all recent troubleshooting findings are accurately captured

Get in Touch

Discord: KJ7LNW

---

Important

Updates shell integration documentation with detailed troubleshooting guidance, addressing VSCode version issues, WSL integration, and environment-specific considerations.

• Documentation Updates:
  • Added detailed troubleshooting guidance in shell-integration.md.
  • Documented VSCode version-specific issues and workarounds, especially for v1.98+.
  • Improved WSL integration method documentation with clearer distinctions.
  • Added environment-specific considerations for troubleshooting.
• Troubleshooting Tools:
  • Added instructions for checking debug logs and interpreting preOutput.
  • Added guidance for using the VSCode Terminal Integration Test Extension.
  • Clarified terminal command delay impact and recommended values.

^{This description was created by for 446ec5a. It will automatically update as commits are pushed.}

[vercel]

Someone is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 446ec5a in 1 minute and 59 seconds

More details

• Looked at 125 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 7 drafted comments based on config settings.

1. docs/features/shell-integration.md:60

• Draft comment:
  Check markdown syntax for the info block; "::::info Important" (4 colons) may be a typo. Standard syntax is typically ":::info Important".
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

2. docs/features/shell-integration.md:253

• Draft comment:
  Duplicate section header "## Known Issues and Workarounds" found; consider consolidating with the previous similar section (starting at line 229) to improve clarity.
• Reason this comment was not posted:
  Comment was on unchanged code.

3. docs/features/shell-integration.md:113

• Draft comment:
  There are two 'Troubleshooting Shell Integration' sections (one at line 18 and another here). Consider consolidating them into a single comprehensive troubleshooting section to avoid confusion.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

4. docs/features/shell-integration.md:35

• Draft comment:
  The 'Terminal Output Limit' description appears duplicated (lines 35 and 36). Consider merging them into one clear and concise description.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. docs/features/shell-integration.md:139

• Draft comment:
  For the Zsh integration installation snippet, consider using 'zsh' as the code fence language instead of 'bash' to provide more appropriate syntax highlighting.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

6. docs/features/shell-integration.md:35

• Draft comment:
  The description for Terminal Output Limit is duplicated on lines 35-36. Consider merging them into a single, clear explanation.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

7. docs/features/shell-integration.md:253

• Draft comment:
  The header 'Known Issues and Workarounds' appears at both line 229 and line 253. Please consider consolidating these sections or renaming one to avoid duplication.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_8MExp7IQ7DMwkLA8

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

Duplicate header 'Known Issues and Workarounds' detected. It appears twice (at line 229 and again here). Consider merging these sections to improve structure and avoid redundancy.