Refine or-true diagnostics with corpus categories

[k7r2-ricon]

Summary

• Classify lint:or-true findings as arithmetic increment, count/probe, best-effort/probe, high-risk, generic ignore missing reason, or unclassified.
• Require inline ignores to be rule-specific and justified (# codebase:ignore or-true — <reason>).
• Add corpus-calibrated tests for risky suppression, arithmetic increments, grep count/probe, best-effort cleanup/probe, explicit ignore justifications, and task help output.

Closes #50.

Validation

• bash -n .mise/tasks/lint/or-true
• shellcheck --exclude=SC1091,SC2034,SC2154 .mise/tasks/lint/or-true
• mise run test test/lint/or-true/or-true.bats
• mise run test (218/218)

Notes

codebase lint "$PWD" is not currently a normal self-validation path for this repo because mise.toml has no [_.codebase].lint rules configured. Direct mise run lint:or-true "$PWD" also intentionally reports fixture hits under test/lint/or-true/fixtures and migration fixtures, so I treated the BATS suite as the self-hosted validation path.

[rikonor]

Fucking spectacular

[x1f9-ricon]

Reviewed and validated. The classification buckets line up with the corpus findings, the stricter inline-ignore requirement is documented in help text and fixtures, and the tests cover arithmetic increments, grep count/probe cases, best-effort cleanup/probes, high-risk git/key suppression, and generic ignores without reasons.

Validation I ran:

• bash -n .mise/tasks/lint/or-true
• shellcheck --exclude=SC1091,SC2034,SC2154 .mise/tasks/lint/or-true
• mise run test test/lint/or-true/or-true.bats (30/30)
• full mise run test (218/218)
• git diff --check origin/main...HEAD

Hosted Ubuntu/macOS checks are green. Nice work.

[x1f9-ricon]

Merged via merge commit 958cddd.

Learning note / pattern worth carrying forward: this was a good example of corpus-calibrated lint work. The PR did not just make or-true stricter; it named the recurring categories, gave users concrete remediation text, and added fixture coverage for each class. For future lint refinements, this shape is strong: broad corpus examples → small taxonomy → rule-specific ignore contract → BATS fixtures for every category.

Local validation before merge: targeted or-true BATS, full suite, shellcheck, bash syntax, diff check; hosted Ubuntu/macOS were green.