## Summary
Describe the problem and fix in 2-5 bullets:
- Problem:
- Why it matters:
- What changed:
- What did not change (scope boundary):
## Change Type (select all)
- [ ] Bug fix
- [ ] Feature
- [ ] Refactor
- [ ] Docs
- [ ] Security hardening
- [ ] Chore/infra
## Scope (select all touched areas)
- [ ] Tool handlers/formatting
- [ ] Attio API integration
- [ ] Tests/mocks/fixtures
- [ ] Issue/PR templates or community files
- [ ] CI/workflows
- [ ] Other
## Linked Issue/PR
- Closes #
- Related #
## User-visible / Behavior Changes
List user-visible changes (including defaults/config). If none, write `None`.
## Security Impact (required)
- New permissions/capabilities? (`Yes/No`)
- Secrets/tokens handling changed? (`Yes/No`)
- New/changed network calls? (`Yes/No`)
- Tool execution surface changed? (`Yes/No`)
- If any `Yes`, explain risk and mitigation:
## Repro + Verification
### Environment
- OS:
- Shell/runtime:
- Relevant tool versions:
### Steps
1.
2.
3.
### Expected
-
### Actual
-
## Evidence
Attach at least one:
- [ ] Failing output before and passing output after
- [ ] Log snippets
- [ ] Screenshot/recording
- [ ] N/A (docs-only or template-only change)
## Human Verification (required)
What you personally verified (not just CI), and how:
- Verified scenarios:
- Edge cases checked:
- What you did not verify:
## Compatibility / Migration
- Backward compatible? (`Yes/No`)
- Config/env changes? (`Yes/No`)
- Migration needed? (`Yes/No`)
- If yes, exact upgrade steps:
## Failure Recovery
- How to disable/revert this change quickly:
- Files/config to restore:
- Known bad symptoms reviewers should watch for:
## Risks and Mitigations
- Risk:
- Mitigation:
## AI Assistance
- AI-assisted: yes/no
- Tools/agents/models used:
- Testing level: untested/lightly tested/fully tested
- Human understanding confirmation: yes/no
