[docs] Unbloat common-issues.md troubleshooting documentation

[github-actions]

Summary

Reduced documentation bloat in troubleshooting/common-issues.md by consolidating verbose explanations and eliminating redundant information while preserving all essential technical content.

Changes Made

• Installation Issues: Condensed 4 subsections into 1, removed redundant explanations
• Repository Configuration: Simplified permission layer descriptions from paragraphs to numbered list
• Compilation Issues: Reduced verbose explanations to concise instructions
• Import/Include Issues: Eliminated redundant examples and verbose descriptions
• Tool Configuration: Streamlined toolset guidance
• Playwright Errors: Condensed error messages and removed repetitive explanations
• Permission Issues: Simplified token and safe outputs guidance
• Network Issues: Consolidated firewall and connectivity sections
• GitHub Lockdown Mode: Reduced from long-form explanation to concise guidance
• Debugging Section: Streamlined debugging strategies

Impact

• Lines removed: 60 lines (~13% reduction)
• Word count reduction: ~35%
• Readability: Improved through consistent, concise language
• Information preserved: All critical technical details retained

Types of Bloat Removed

1. Verbose explanations: "The AI agent tried to use require('playwright') or created a standalone Node.js script expecting..." → "The agent tried to require('playwright') but..."
2. Redundant bullet points: Removed duplicate tool lists when documentation link was provided
3. Repetitive patterns: Eliminated excessive "Error Message:", "Cause:", "Solution:" formatting where concise descriptions sufficed
4. Over-explanation: Reduced multi-paragraph explanations to essential guidance

Screenshot Issues

⚠️ Unable to capture screenshots of the rendered documentation page due to network restrictions between Playwright container and the local preview server. The firewall blocks connections from the Playwright MCP server to localhost:4321 or the host IP address.

Blocked Domains: None - the issue is container-to-host networking, not domain blocking.

Verification

File before: 468 lines
File after: 407 lines
Reduction: 60 lines (13%)

Git diff stats:

docs/src/content/docs/troubleshooting/common-issues.md | 192 +++++++--------------
1 file changed, 66 insertions(+), 126 deletions(-)

AI generated by Documentation Unbloat

• expires on Feb 20, 2026, 12:08 AM UTC

[Copilot]

Pull request overview

This pull request reduces documentation bloat in the troubleshooting common-issues guide by condensing verbose explanations while preserving all essential technical content. The changes successfully reduce the file from 468 to 407 lines (13% reduction, ~35% word count reduction) through consolidation of subsections, elimination of redundant bullet points, and streamlining of multi-paragraph explanations into concise guidance.

Changes:

• Consolidated installation issues from 4 subsections into 1 unified section
• Simplified repository configuration descriptions from verbose paragraphs to numbered lists
• Streamlined tool configuration, Playwright errors, permission issues, and network sections by removing redundant examples and verbose explanations
• Condensed GitHub lockdown mode section from detailed long-form content to focused guidance
• Reduced debugging section to essential strategies without repetitive formatting

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The condensed text is less clear about the actual issue. The original stated "GitHub Projects reserves field types like REPOSITORY that cannot be updated via API" and suggested using alternative "field names" instead of "repository". The condensed version says "reserves field names like REPOSITORY" but the code example shows lowercase "repository" as wrong. Consider: "GitHub Projects reserves the field name repository (uses REPOSITORY type). Use alternatives (repo, source_repository, linked_repo):" to better connect the explanation to the code example.

Suggested change

	GitHub Projects reserves field names like `REPOSITORY`. Use alternatives (`repo`, `source_repository`, `linked_repo`):
	GitHub Projects reserves the field name `repository` (it uses the `REPOSITORY` field type). Use alternatives (`repo`, `source_repository`, `linked_repo`):