| 1 | ## Summary |
| 2 | |
| 3 | <!-- What does this PR do? 1-3 sentences. --> |
| 4 | |
| 5 | ## Testing |
| 6 | |
| 7 | - [ ] `uv run pytest` |
| 8 | - [ ] Added or updated tests that would catch a regression, or explained why not below |
| 9 | |
| 10 | ## Changelog |
| 11 | |
| 12 | If this change should appear in the next release notes, add a fragment under `changelog.d/` (see `changelog.d/README.md` and [CONTRIBUTING.md](../CONTRIBUTING.md)). Do **not** edit `CHANGELOG.md` or bump version/manifest files in this PR. |
| 13 | |
| 14 | - [ ] Added `changelog.d/<pr-or-issue>.<type>.md` (types: `added`, `changed`, `fixed`, `removed`, `deprecated`, `security`) |
| 15 | - [ ] Skip changelog — chore/internal only (also add the `skip-changelog` label) |
| 16 | |
| 17 | ## Agent disclosure |
| 18 | |
| 19 | ### AI review |
| 20 | |
| 21 | Summarize the review your coding agent ran: main risks checked, what it flagged, and what you changed or verified as a result. |
| 22 | |
| 23 | ### Security |
| 24 | |
| 25 | Note any input handling, command execution, path handling, auth, secrets, or dependency risks reviewed, plus follow-up needed. Write `N/A` if none apply. |
| 26 | |
| 27 | ## Notes |
| 28 | |
| 29 | Call out follow-up work, host-specific behavior, or risks. |
| 30 | |
| 31 | ### Relationship to this change |
| 32 | |
| 33 | Disclose employment, contracting, equity, or other paid ties to a company/product/service this PR adds or meaningfully promotes (example: you work at the API vendor being integrated). |
| 34 | |
| 35 | - [ ] None |
| 36 | - [ ] Yes — disclosure: <!-- who / what relationship --> |
| 37 | |
| 38 | ## Related issues |
| 39 | |
| 40 | <!-- Fixes #123 / Relates to #456 — or N/A --> |
| 41 |