---
name: Feature request
about: Suggest a change or new capability
labels: Feature request
---
<!--
Writing rules (for the author, AI or human; comments are not rendered):
- Two audiences: Summary + Acceptance criteria are for the human approver. The collapsed section is for the implementer (usually an AI).
- State each fact once. Do not restate the problem in the solution, or repeat code references in prose.
- Summary: max 5 sentences, plain language, no file paths or type names.
- Technical section: one bullet per fact, terse, `path/File.cs:line` references, no narrative.
- Omit any section or field with nothing to say. Never write "N/A".
- No greetings or sign-off.
-->

## Summary
<!-- What is wrong or missing, who is affected, what should happen instead. -->

## Acceptance criteria
<!-- 2–5 observable checks in user terms. This is the definition of done. -->
- [ ]

## Scope
<!-- Optional. Out of scope, or which option was chosen. One line each. -->

<details>
<summary>Technical details</summary>

**Validated against:**
**Feature flag / config:**

**Root causes**
<!-- One bullet per cause: `file:line` — what it does, why that breaks it. One sentence. -->
1.

**Proposed changes**
<!-- Numbered to match the causes where possible. Name the type/method to change. -->
1.

**Existing code to reuse**
-

**Alternatives rejected**
<!-- option — reason, one line each -->
-

</details>