What problem does it solve? Stale tests and out-of-sync assertions break CI for other contributors when APIs change or counted files are added without updating test expectations. ## Core Features & Use Cases - Same-commit test updates: Ensures any change to a function signature, public interface, or exported API is accompanied by corresponding test updates before committing. - Assertion-to-disk synchronization: Keeps expected count arrays (e.g., EXPECTED_FEATURES, EXPECTED_SCENARIOS) aligned with the actual files on disk. - CI triage guidance: Directs checking assertion arrays first when CI fails, before debugging complex failures. - Use Case: After adding a new docs page like distributed-mesh.md to a features directory, update the EXPECTED_FEATURES array in the same commit so the next contributor's CI run passes. ## Quick Start Apply the test-discipline skill to review my pending commit and verify that all API changes and added files have matching test updates.