Standardize line length requirements for different GitHub issue types

Standardize line length requirements for different GitHub issue types

We need clear guidelines on appropriate line lengths for different issue types:

- Bugs (like #138): Up to 18 lines to include reproduction steps, expected vs actual behavior
- Feature requests: 8-12 lines focusing on core requirements
- Documentation improvements: 5-8 lines with clear scope
- Refactoring: 6-10 lines highlighting benefits

This prevents overly verbose issues for simple features while ensuring bugs have sufficient detail for diagnosis.

No file, test, or entry point is identified in the issue. Start by locating the repository guidance or issue-template configuration that controls GitHub issue types, then document the proposed line-length ranges there and verify that each issue type has clear, consistent guidance.

Written by the indexing model from the issue text.