Defame1297
864e7c689c
Three rounds of review on the Vale prefilter surfaced patterns worth keeping rather than just fixing. The first has now recurred three times in a single PR — a check reporting success because it had silently not run — so it is flagged as a graduation candidate per LESSONS.md's own three-instance rule. - A clean linter result can mean "nothing was checked": the frontmatter scope silently not matching, warning-level rules never affecting an exit code, and globs matching zero files all produced green results that were then cited as evidence of cleanliness. - One signal, two consumers, no named distinction: Vale severities were tuned for the audit report while the commit gate silently inherited the resulting exit code, because CONTEXT.md described both as one mechanism. - Measure a rule's false-positive rate at the severity you will ship it at: VagueQualifier was trialled at warning, where a false positive is free, and shipped at error, where it costs a blocked commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MCQ648fLSFXPHGZdQ8gn58