Fresh-eyes audit of every analyzer suppression and arbitration #317

What

Re-examine, with fresh eyes, every analyzer suppression and every arbitration the repository has written, and decide for each one whether it is still needed and whether its reason still holds.

Inventory at master c8936b45

• .editorconfig rules set to none or silent: 111
• #pragma warning disable in src/, tests/ and tools/: 22
• slopwatch suppressions: 37
• NoWarn lines in .props, .targets and .csproj files: 7
• arbitration ("winner") comments: about 63

How

• A reviewer of a different lineage from the one that wrote most of them (dispatch harness, review persona) gets the inventory. For each entry it reports one of: keep (the reason holds), remove (the diagnostic no longer fires, or the reason is stale), or replace with a narrower scope.
• Findings come as a report to the maintainer first. Fixes follow his decisions.
• A removal that turns up a real defect is fixed at its root, in its own PR.

Why 1.0

A suppression that hides a public-surface problem must be found before the freeze.

Done when

• Every entry is classified in the report, and the maintainer has decided on it.
• The decided removals and narrowings have landed.
• The suppression rule from Canon questions left open: reduced gates for docs-only changes, the suppression rule, the source-watch anchor refusal #216 is in canon.

Requested by the maintainer, 2026-10-15 (#216 discussion).