# DX Task Folder

## Purpose

Use `docs/tasks/features/dx/` for developer and operator experience work that needs a stable home instead of being scattered across runners, agents, and stability.

Examples:

- machine-readable control surfaces
- CLI compatibility contracts
- fake CLI regression harness work
- upstream-canary validation work
- capability matrices and drift classification

## Folder Rules

- keep task docs focused on DX-facing surfaces
- keep end-user feature delivery under the canonical product area instead
- use `dx` when the primary customer is the operator, developer, or automation layer
