## Summary

<!-- One-sentence summary of the change -->

## Why

<!-- What problem does this solve? Link related issues: Fixes #N -->

## Type

- [ ] New provider
- [ ] New feature
- [ ] Bug fix
- [ ] Refactor
- [ ] Documentation
- [ ] Tests

## Surface area

- [ ] Workspace/package boundaries
- [ ] Provider interface / adapter contract
- [ ] YAML schema / config types
- [ ] CLI commands
- [ ] WebUI
- [ ] State management
- [ ] Execution / planning logic
- [ ] Tests / fixtures
- [ ] None of the above

## Checklist

- [ ] `bun run verify:full` passes
- [ ] New provider follows the six-file structure, if applicable
- [ ] No new runtime dependencies added without justification

## Behavior / risk

<!-- Required only when changing provider contracts, config/schema parsing, release/package files, or GitHub workflows.
State the user-visible behavior or compatibility/security risk. “No user-visible behavior change” is valid for an internal refactor.
No special commit-message marker or history rewrite is required. -->

## Validation

<!-- Commands, automated test cases, or manual reproduction used to verify this change.
For high-risk changes, this must be non-empty. -->