fix(louvain): demote native-path parity warning to debug

Warning fired on every communities computation because DEFAULTS.community
in config.ts always populates maxLevels/maxLocalPasses/refinementTheta, so
the != null guard never gated anything in practice. The message is an
informational parity note (Leiden knobs ignored by native Louvain), not
user-actionable — debug is the right level.

docs check acknowledged: no language/architecture/feature changes.

Impact: 1 functions changed, 10 affected

Author: carlos-alm

src/graph/algorithms/louvain.ts

@@ -6,7 +6,7 @@
  * JS fallback: Leiden algorithm via `detectClusters` (always undirected, `directed: false`).
  */
 
-import { warn } from '../../infrastructure/logger.js';
+import { debug } from '../../infrastructure/logger.js';
 import { loadNative } from '../../infrastructure/native.js';
 import type { CodeGraph } from '../model.js';
 import type { DetectClustersResult } from './leiden/index.js';
@@ -36,10 +36,8 @@ export function louvainCommunities(graph: CodeGraph, opts: LouvainOptions = {}):
 
   const native = loadNative();
   if (native?.louvainCommunities) {
-    // maxLevels, maxLocalPasses, and refinementTheta are Leiden-specific tuning knobs
-    // not supported by the Rust Louvain implementation. Warn callers who set them.
     if (opts.maxLevels != null || opts.maxLocalPasses != null || opts.refinementTheta != null) {
-      warn(
+      debug(
         'louvainCommunities: maxLevels/maxLocalPasses/refinementTheta are ignored by the native Rust path',
       );
     }