Code Quality Gate

Build a gate from project risks and observed baselines. Do not present a tool's sample threshold as a universal standard, and do not weaken a gate merely to make a pipeline green.

Diagnose a Failure

1. Read the exact CI log and tool version.
2. Reproduce the narrow failing check locally when safe.
3. Separate:
   • product defect;
   • test defect or flaky signal;
   • configuration drift;
   • generated or third-party code;
   • credible false positive.
4. Fix the cause at the smallest responsible layer.
5. Re-run the failed check and relevant neighboring checks.
6. Record any accepted exception with owner, evidence, expiry, and review date.

Do not bulk-suppress rules, mark findings false-positive without evidence, or add tests that only execute lines without checking behavior.