test-discipline

To keep tests in sync when API changes break CI, update stale assertions and expected counts in the same commit as the modified public interfaces or exported functions. This ensures test validation aligns with the new contracts before CI runs.

Syncing filesystem assertions with actual disk state requires validating that expected arrays and file counts match the real contents on disk. This prevents stale test expectations from failing after documents or features are added or removed.

Expected file count arrays fail after adding new scenarios because the hardcoded assertions no longer match the actual disk state. You must update the expected lists in the same commit to reflect the newly added or removed inventory items.

Yes, you need to update assertions in the same commit as API changes. Same-commit synchronization ensures that exported function signatures, public contracts, and their associated tests are validated together before CI runs.

To triage CI failures caused by stale test assertions, check the assertion arrays first when failures appear after document, feature, or scenario inventories are modified. Update the expected counts to match the actual disk state.

You should update tests for modified public interfaces whenever a function signature, export, or public contract changes. This prevents stale tests from breaking CI by keeping validation aligned with the code it checks.