Issue

Create a GitHub issue from a short description.

Conventions

• Title: Conventional Commit format (type(scope): description), under 60 chars, no trailing period
• Label: enhancement for features, bug for bugs
• Body sections (in order): What would you like?, Motivation, Proposed approach, Scope
• Each section is a ## heading followed by 1-3 short paragraphs; a single sentence is fine
• Write plainly — no code blocks, no bullet-heavy lists, no implementation detail
• Focus on what and why, not how — leave implementation to the branch
• Scope section uses a flat bullet list of affected areas
• Self-contained: the issue must stand alone for anyone reading the repo. No links to private or local docs (e.g. a planning file) and no internal shorthand (P1, RC4, C2) — spell the point out or drop it

Workflow