---
name: Feature request
about: Propose a change to scope, surface, or capability.
title: '[feature] '
labels: enhancement
assignees: ''
---

## Problem

<!--
What pain point or gap motivates this? A specific scenario that fails
today, a workflow that's awkward, a capability that's missing.
-->

## Proposed change

<!--
Concrete description of what you'd like to see. If you're proposing a new
slice, the BACKLOG.md format is preferred (id, title, deps, acceptance).
-->

## Why this over the alternatives

<!--
Did you consider doing it differently? What rules-out the alternative?
"It would be nice to have X" is rarely strong enough — be explicit about
the user/scenario/test that needs X to land.
-->

## Open questions

<!--
- API/CLI surface changes? Breaking?
- Cross-cloud or single-cloud?
- ADR-worthy? (See CONTRIBUTING.md § ADR policy.)
- Any reasonable rejection (e.g., the design rule that killed S49 — "mocks
  optimize for fast feedback, not real-cloud fidelity") that applies here?
-->
