Verifies that a PaperMiner change is ready to hand over by checking tests, lints, ripple effects, and documentation sync. Use before declaring a feature, refactor, or bug fix complete.
Do not say a PaperMiner change is done until there is evidence.
State exactly what changed:
Run the smallest sufficient validation:
python -m pytest -q if core, contracts, shared schemas, or multiple plugins changedReadLints on edited files after substantive editsConfirm whether the change also required updates to:
docs/ai-context/ and logs/Explicitly confirm:
Use this before closing the task:
## Change Readiness
- Scope:
- Verified by:
- Remaining unverified items:
- Known risks:
- Ready to hand over: yes / no
If anything is unverified, say it directly instead of implying the module is fully safe.