A change is complete only when its intended behavior, risk boundary, and evidence are clear to a future maintainer.
- Requirements and non-goals are documented; legal-sufficiency claims are not made.
- Tests cover changed behavior and
make verifypasses locally and in CI. - Source-cited rule changes include current official sources and qualified review.
- Security, privacy, accessibility, data, and operational implications are assessed.
- User-facing changes update the README, changelog, and applicable guides.
- No real filing package, personal data, secret, or unlicensed material is committed.
- Before a release: review the release checklist, create SBOM/provenance, publish release notes, and record required accessibility and responsible-tech evidence.