test-discipline

Update test assertions by identifying modified public interfaces and synchronizing test files and assertion arrays in the same commit. This keeps CI builds green by preventing regressions caused by mismatched expectations.

CI regressions occur because test assertions and expected data no longer match the modified API. Synchronizing test files, disk counts, and documentation pages within the same commit prevents these failures.

Keep documentation and tests in sync by updating relevant test files, assertion arrays, and build checks alongside code changes. This ensures alignment between disk reality and expected data.

The best way to prevent failures is enforcing alignment by updating test assertions and relevant test files immediately after modifying an API. This maintains green CI by catching regressions in the same commit.

Yes, aligning disk counts and expected data is handled by updating assertion arrays to reflect the repository's actual state. This ensures test expectations match disk reality during build checks.

You should never delay, as separating API changes from test updates causes CI regressions and misaligned expectations. Tests must be updated in the same commit to maintain green CI.