Review Checklist

Use this checklist for package-facing changes.

Checklist

• does the change keep collection, reporting, and maintenance boundaries clear
• are tracked data/ or docs/report/ diffs intentional and explained
• do docs reflect any renamed paths, commands, or output contracts
• is the narrowest useful test layer updated
• if defaults changed, was the public contract impact reviewed explicitly

Purpose

This page records the minimum review questions for runtime changes.