SPEC-132 D5. Users have content we cannot anticipate, and a framework that nags them about a diagnostic they disagree with — or worse, refuses to build — is one they turn off wholesale. Give them a narrow switch so they do not reach for a wide one.
Tracking started Sep 13 — check back for trends.
2e63225Configurable per site and per error id. Deliberately not per page and not per tag: that granularity invites silencing the one call site that revealed a real bug, which is how a validation feature becomes decoration.
critical findings are not suppressible at all (D11). They mean the document could not be understood — a parse error, an unclosed tag — which is not a matter of preference. Only the error band is configurable.
critical findings are reported regardless of configuration, with a test proving a disabled config still surfaces onedescription in refrakt.config.schema.json worth reading (SPEC-126)Land it in the same release as WORK-556, not after. A validation feature that ships without an escape hatch teaches users to distrust the next one, and the hatch is cheap — it is a config field and a filter, reusing the allow-list WORK-556 already builds.
Worth deciding once and recording: whether disabling an id suppresses the finding entirely or demotes it to info. Demotion keeps it visible to anyone looking while removing the noise, which is usually the better default for a diagnostic someone has actively judged unimportant.