## Summary

- Problem:
- Change:
- User-visible effect:
- Linked issue: Closes #

## Risk and trust assessment

- Risk surfaces touched:
- Untrusted inputs or external dependencies:
- Remote code, deserialization, credentials, subprocess, network, or filesystem impact:
- Compatibility or migration impact:

## Test evidence

Exact head SHA: `TBD`

Review and acceptance are bound to this SHA. Pushing another commit invalidates the
record below until it is updated and the new head is green.

| Check | Result | Evidence or notes |
|---|---|---|
| Focused regression/contract tests | TBD | |
| Negative and boundary tests | TBD | |
| `python -m ruff check --select F app.py obliteratus tests scripts` | TBD | |
| `uv lock --check` | TBD | |
| Selected PR core/risk tests | TBD | |
| Package build, when package inputs changed | not applicable / TBD | |
| Import and CLI smoke checks | TBD | |
| Applicable risk-surface checks | TBD | |
| Conditional hardware/service gates | not applicable / TBD | |

Coverage or mutation impact:

- Changed-line:
- Additional maintainer coverage or release-depth work needed:

## Research or performance evidence

- Exact model/dataset revisions, configuration, seed, environment, and hardware:
- Raw evidence/artifacts and hashes:
- Baseline, uncertainty, limitations, and independent reproduction status:

Use `Not applicable` when this pull request makes no research or performance claim.

## Checklist

- [ ] I added or updated focused tests for changed behavior, or identified where maintainer help is needed.
- [ ] I covered relevant failure, boundary, and malformed-input paths.
- [ ] The default test path remains deterministic, offline, credential-free, and CPU-safe.
- [ ] I updated `ci/test-risk-map.json` or conditional policy when ownership changed.
- [ ] Documentation and examples match user-visible behavior.
- [ ] No secrets, private keys, credentials, caches, generated provider files, or unrelated changes are included.
- [ ] Remote code and executable deserialization remain disabled by default, or the explicit exception is justified and tested.
- [ ] Dependency, action, or tool changes include the reviewed lock/digest and supply-chain impact.
- [ ] Research and performance claims are traceable to exact-head evidence and scoped to what was tested.
- [ ] Every commit has a verifiable signature from its actual author or approved integration identity.
- [ ] The branch has not been force-pushed and the exact head is ready for review.
- [ ] I understand that green PR checks establish review readiness; maintainer
      acceptance, canonical merge verification, and release certification are
      separate gates.

A green PR gate makes the submission reviewable. Maintainers may add further tests
or hardening in separately attributable commits before merge; behavior changes with
zero relevant coverage remain blocked.

See [`docs/RELEASE_PROCESS.md`](../docs/RELEASE_PROCESS.md) for the exact-head
acceptance, merge, tag, snapshot, and publication process.