Different checks land violations for the same file in their own pass order (colours before shadows before media queries, an application's CSS always appended after its views) rather than the order a maintainer would read the file in. DesignGuard::violations() now sorts everything it returns deterministically before handing it back, and a fixture proves it crosses both dimensions: a later-processed application-CSS file whose path sorts first, and two different checks landing on the same line in the opposite order from how they run. Plan step 42 (Phase F), Part B. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9