[FEATURE] Known Issues page in documentation

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When users encounter issues with Claude Code, they often:

1. Assume it's their own setup/environment
2. Spend time troubleshooting
3. Search GitHub issues to find others with the same problem
4. Only then realize it's a known issue

There's no single place to quickly check "is this a known problem?" before investing time in debugging.

As described in #15692:

An official place where users can quickly check if something is a known problem before spending time troubleshooting. This is standard practice for developer tools at this level.

Proposed Solution

Add a "Known Issues" page to the official documentation that lists:

• Currently known issues/bugs
• Affected versions
• Workarounds (if available)
• Status (investigating / fix planned / etc.)

This serves as a quick reference before users dive into GitHub issues search.

Alternative Solutions

• Existing Troubleshooting page: The current Troubleshooting page covers installation, configuration, and permanent setup issues—but it's not designed for tracking current bugs in specific versions (e.g., "LSP broken in v2.0.67+")
• GitHub Issues only: Current state; requires users to search and filter
• Pinned issues: Limited visibility, mixed with other content
• Release notes "known issues" section: Tied to specific releases, harder to find current state

Priority

Medium - Would be very helpful

Feature Category

Documentation

Use Case Example

1. User updates to latest version
2. LSP features stop working
3. User checks "Known Issues" page → sees "LSP regression in v2.0.67+, fix in progress"
4. User knows to wait or downgrade, instead of spending hours debugging

Additional Context

Prior art:

• JetBrains Known Issues
• VS Code Known Issues
• Many developer tools maintain similar pages

Benefit:

• Reduces time wasted on known problems
• Reduces duplicate "is anyone else seeing this?" issues
• Shows users their problems are acknowledged

Related: #15692 (original request by DKMaker)

---

✍️ Author: Claude Code (Dev Container) with @carrotRakko

Note: This issue was written and submitted by an AI agent (Claude Code), with human review and approval.