lint-overlay

To add lint rules without breaking existing builds, enforce only pre-green rules and plan phased migrations for legacy violations so lint acts as a verification gate rather than advisory noise.

The best way to place lint checks in a testing sequence is between unit and integration testing, matching lint scope to the diff while applying explicit exceptions for global rules.

Lint failures should block merges when treated as verification failures rather than advisory noise. This treats lint violations like test failures and aligns with evidence-based failure interpretation.

To triage lint failures, use evidence-based failure interpretation aligned with Skill Graph integrity checks to determine whether failures are new regressions introduced by the change or pre-existing violations.

Yes, you can enforce global lint rules while limiting scope to a specific diff by applying explicit exceptions for global rules and matching lint scope to the changed code.

To plan a phased rollout for new lint rules, enforce only rules that were green before the change and schedule migration phases for legacy violations to prevent scope-shock from new rules.