issuelisted

# GitHub Issue Creation Create well-structured GitHub issues following repository conventions. ## Issue Title Format Use semantic prefixes matching conventional commits: ```text feat(scope): short description # New feature fix(scope): short description # Bug fix docs(scope): short description # Documentation chore(scope): short description # Maintenance refactor(scope): short description # Code refactoring perf(scope): short description # Performance improvement ``` ## Issue Body Structure ### For Feature Requests ```markdown ## Summary One paragraph describing the feature and its value. ## Problem What problem does this solve? What's the current limitation? ## Proposed Solution Detailed description with: - Code examples showing desired behavior - ASCII diagrams or mockups if applicable - Configuration examples ## Implementation Notes - Key files to modify - Dependencies or prerequisites - Potential challenges ## Benefits - Bullet points of user/developer benefits ``` ### For Bug Reports ```markdown ## Summary One paragraph describing the bug. ## Problem What's happening vs what should happen? Include: - Steps to reproduce - Error messages or screenshots - Environment details if relevant ## Proposed Solution How to fix it (if known). ## References - Links to related issues, docs, or resources ``` ## Labels Apply appropriate labels based on issue type: | Issue Type | Labels | | ----------------- | ---------