test-discipline

You keep tests aligned with API changes by enforcing test-assertion synchronization within the same commit as the API update. This prevents stale tests from passing and reduces flaky CI failures caused by mismatched outputs.

False positives after a public API update happen when tests are not synchronized with the API changes, allowing stale assertions to pass. Enforcing test updates in the same commit validates changes against disk reality and prevents mismatched outputs.

You need to update test assertions for contract changes across modules whenever APIs evolve, refactors occur, or public outputs change. Validating these updates in the same commit ensures tests reflect the current disk reality of EXPECTED_FEATURES and EXPECTED_SCENARIOS.

The best way to synchronize test outputs during a refactor is to update the corresponding tests to reflect new API signatures and run the full test suite. This validates synchronization and prevents stale or mismatched assertions from causing CI failures.

Yes, test synchronization requires updating tests in the same commit as API changes. This in-flight commit discipline ensures test assertions reflect current disk reality and prevents flaky test suites caused by stale or mismatched outputs.

Without test-assertion synchronization during API refactors, stale tests pass with mismatched assertions, leading to CI false positives and flaky test suites. Failing to validate against disk reality allows outdated public API outputs to go undetected.