diff --git a/docs/guides/quality-gates.md b/docs/guides/quality-gates.md
index c4dca06f..6c7924ce 100644
--- a/docs/guides/quality-gates.md
+++ b/docs/guides/quality-gates.md
@@ -71,4 +71,4 @@ Every production pattern should have:
 
 The repository includes a root `.editorconfig` so editors, `dotnet format`, and CI agree on basic C# layout and style. Run `dotnet format PatternKit.slnx --verify-no-changes --verbosity minimal` before opening a PR; CI enforces the same gate for pull requests and `main` releases.
 
-The same rule applies to analyzer hardening. Built-in .NET analyzers currently surface many intentional API-shape warnings for fluent generic factories, benchmark method names, and netstandard-compatible guard code. Enable stricter analyzers by project and rule family with explicit baselines rather than turning on solution-wide warning enforcement in one step.
+Built-in .NET analyzers can be audited with `/p:EnableNETAnalyzers=true /p:AnalysisLevel=latest /p:AnalysisMode=Recommended /p:EnforceCodeStyleInBuild=true`. That audit currently surfaces project-specific baselines, including source-generator workspace gaps in examples and benchmarks, fluent API shape warnings in production code, benchmark naming warnings, and culture-sensitive string assertions in generator tests. Enable stricter analyzer families by project with explicit baselines rather than turning on every optional rule at once.