OBLITERATUS/.github/pull_request_template.md

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

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
python -m pytest	TBD
python -m build --sdist --wheel	TBD
Import and CLI smoke checks	TBD
Applicable risk-surface checks	TBD
Conditional hardware/service gates	not applicable / TBD

Coverage or mutation impact:

• Repository line/branch:
• Changed-line:
• Touched-module regression:
• Mature CPU scope:
• Mutation score, when applicable:

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 tests for every changed behavior.
• 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.

New changes are expected to include their complete relevant test suite. The one-time maintainer courtesy for already-reviewed legacy pull requests does not apply to new submissions.