pub const KNOWN_CASES: &[&str];Expand description
Every case the binary knows how to load. Adding a new case requires:
- A new entry here (alphabetical-ish, but grouped by failure family).
- A matching
fixtures/cases/<name>.jsonfile. - A matching
fixtures/logs/<name>.logfile. - A
[rules.<rule_name>]section inprose.tomlif the case triggers a rule that doesn’t already exist.
The known_cases_matches_on_disk_fixtures test enforces (1)+(2)
stay in sync; new fixture without a constant entry — or vice versa —
breaks cargo test.