Document label organization for better visual organization - comprehensive label guide

Problem

Our repository currently lacks comprehensive label documentation. Team members and contributors often struggle to understand when to use specific labels, leading to inconsistent labeling across issues and pull requests. This creates challenges in visual organization, issue triage, and project management. Without clear label documentation, new contributors may apply incorrect labels or miss important categorization nuances.

Proposed Solution

Create a comprehensive label guide that documents all existing labels in the repository, organized by category. This label documentation will provide clear descriptions, usage guidelines, and visual organization patterns for each label. The guide will cover categories including:

• Issue Types: bug, feature, enhancement, documentation, question, duplicate, invalid, regression
• Platform: platform:macos, platform:windows, platform:linux
• Area/Component: area:tui, area:api, area:plugins, area:agent, area:mcp, area:hooks, area:bash, area:desktop, area:web, area:sandbox, area:permissions, area:skills, area:cli
• Status: has repro, performance
• General: feature

This label documentation will serve as the single source of truth for understanding our repository's visual organization and label organization.

Benefits

1. Improved visual organization - Labels provide at-a-glance understanding of issue categories and priorities
2. Easier issue triage - Team members can quickly identify and prioritize issues based on clear label patterns
3. Consistent labeling - Clear guidelines ensure all team members use labels uniformly
4. Better project management - Organized labels enable efficient filtering and reporting
5. Onboarding support - New contributors can quickly understand the label guide and apply correct labels

This label documentation and organization effort will significantly improve our repository's usability and maintainability.