fix(doctor): emit tool-policy profile audit at debug level

KaiLi · Kailigithub · commit 8035b8645aa6 · 2026-05-29T11:14:34.000+08:00
When tools.profile is set to a named profile (e.g. "coding"), the tool-policy
 pipeline removes tools that don't belong to that profile. The resulting audit
 lines ("tool policy removed N tool(s) via tools.profile (coding): ...") are
 expected behavior, not actionable doctor findings.

 These lines were emitted at info level, causing normal doctor output to look
 noisy when a profile filter is active. Now they are emitted at debug level so
 they appear in verbose/debug logs but not in regular doctor output.

 The fix is isolated to auditToolPolicyFilter in tool-policy-audit.ts. Only
 steps whose label starts with "tools.profile" are affected; other audit paths
 (agents.allow, tools.deny, etc.) continue to log at info level.
diff --git a/src/agents/tool-policy-audit.ts b/src/agents/tool-policy-audit.ts
@@ -176,7 +176,9 @@ export function auditToolPolicyFilter(params: {
       tools: matchedRuleSourceTools,
     });
     const matchedRuleSuffix = matchedRules.length > 0 ? `; matched ${matchedRules.join(", ")}` : "";
-    toolPolicyAuditLogger.info(
+    const isProfileFilter = params.stepLabel.startsWith("tools.profile");
+    const logLevel = isProfileFilter ? "debug" : "info";
+    toolPolicyAuditLogger[logLevel](
       `tool policy removed ${removed.length} tool(s) via ${rule}: ${toolNames.join(", ")}${matchedRuleSuffix}`,
       {
         rule,
