docguard-cli 0.14.0__tar.gz → 0.15.1__tar.gz

{docguard_cli-0.14.0/extensions/spec-kit-docguard → docguard_cli-0.15.1/.agent}/skills/docguard-fix/SKILL.md

@@ -6,10 +6,10 @@ description: AI-driven documentation repair with structured research workflow, t
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.14.0
+  version: 0.15.1
   source: extensions/spec-kit-docguard/skills/docguard-fix
 ---
-<!-- docguard:version: 0.14.0 -->
+<!-- docguard:version: 0.15.1 -->
 
 # DocGuard Fix Skill
 

{docguard_cli-0.14.0/extensions/spec-kit-docguard → docguard_cli-0.15.1/.agent}/skills/docguard-guard/SKILL.md

@@ -7,10 +7,10 @@ description: Run DocGuard guard validation against Canonical-Driven Development
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.14.0
+  version: 0.15.1
   source: extensions/spec-kit-docguard/skills/docguard-guard
 ---
-<!-- docguard:version: 0.14.0 -->
+<!-- docguard:version: 0.15.1 -->
 
 # DocGuard Guard Skill
 

{docguard_cli-0.14.0/extensions/spec-kit-docguard → docguard_cli-0.15.1/.agent}/skills/docguard-review/SKILL.md

@@ -6,10 +6,10 @@ description: Cross-document consistency analysis and quality assessment. Perform
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.14.0
+  version: 0.15.1
   source: extensions/spec-kit-docguard/skills/docguard-review
 ---
-<!-- docguard:version: 0.14.0 -->
+<!-- docguard:version: 0.15.1 -->
 
 # DocGuard Review Skill
 

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/.agent/skills/docguard-score/SKILL.md

@@ -6,10 +6,10 @@ description: CDD maturity assessment with category-aware improvement roadmap. Ru
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.14.0
+  version: 0.15.1
   source: extensions/spec-kit-docguard/skills/docguard-score
 ---
-<!-- docguard:version: 0.14.0 -->
+<!-- docguard:version: 0.15.1 -->
 
 # DocGuard Score Skill
 

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/.agent/skills/docguard-sync/SKILL.md

@@ -4,7 +4,7 @@ description: Keep canonical documentation ALWAYS UP TO DATE. Refreshes code-trut
 compatibility: Requires DocGuard CLI installed (npm i -g docguard-cli or npx docguard-cli)
 metadata:
   author: docguard
-  version: 0.14.0
+  version: 0.15.1
   source: extensions/spec-kit-docguard/skills/docguard-sync
 ---
 

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/CHANGELOG.md

@@ -7,6 +7,95 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.15.1] - 2026-05-26
+
+Feature + performance release. **497 tests** (was 492, +5). 22 validators.
+Headline: full `--changed-only` set now covers **5 validators in ~100ms** on
+both wu-whatsappinbox AND a synthetic 1000-file repo. New `.docguard.json`
+JSON Schema for IDE autocomplete.
+
+> **Note**: v0.15.0 was committed but never published — the CI self-guard
+> failed because the new `tests/scoping-extended.test.mjs` had literal
+> `// DRIFT:` strings inside JS fixture data that Drift-Comments treated as
+> real drift comments. v0.15.1 includes a two-part fix: the test uses string
+> concatenation so the literal marker isn't in source, AND Drift-Comments
+> now skips test files by default (matching TODO-Tracking's pattern; opt in
+> via `config.drift.includeTestFiles`). Everything else in this release was
+> ready in v0.15.0 — see the v0.15.0-planned features below.
+
+### Fixed (v0.15.1 hotfix)
+
+- **Drift-Comments false-positives from test fixtures.** Test files commonly carry literal `// DRIFT:` strings inside JS string fixtures (`'// DRIFT: example\n'`). Reading the test as source treated those as real drift comments. Drift-Comments now skips test files by default — same defensive posture TODO-Tracking adopted in v0.11.2 for the same reason. New `config.drift.includeTestFiles` opt-in for projects that genuinely use DRIFT markers in test code.
+
+### Added
+
+- **P3: Drift-Comments + TODO-Tracking honor `config.changedFiles`.** Extending the v0.13 N-1 + v0.14-P2 lite-mode scoping. Now 5 of 22 validators scope to changed files in `--changed-only` mode (was 3). `CHANGED_ONLY_VALIDATORS` updated to include `drift` and `todoTracking`. **Result on wu: `--changed-only --since HEAD~3` runs 5 validators in 116ms** (was 78ms with 3 validators in v0.14 — adding two more validators cost only ~40ms because each is scoped). **Result on synthetic 1000-file repo: 91ms** (verified via new stress test).
+- **P4: JSON Schema for `.docguard.json`.** New `schemas/docguard-config.schema.json` shipped in the npm package. `docguard init` now writes `$schema` reference into newly-created configs so VS Code / IntelliJ / any JSON-Schema-aware editor gets autocomplete + inline validation for every config field. Includes types, descriptions, enums (severity = high/medium/low; profile = starter/standard/enterprise; projectType = cli/library/webapp/api/unknown), and field-level help text. Zero runtime impact — DocGuard ignores the `$schema` field itself.
+- **Q: Stress-test fixture.** New `tests/stress-test.test.mjs` builds a synthetic 1000-file monorepo (500 services + 500 routes + 1000 doc references) and asserts:
+  - `--changed-only` finishes in **< 500ms** (actual: ~91ms).
+  - Full guard finishes in **< 5s** (actual: ~755ms).
+  Opt-in via `STRESS=1` to keep `npm test` fast. Catches regressions where any scoping path accidentally devolves to a full tree walk.
+
+### Performance
+
+- **P1: `buildMemoryPlan` cache.** Memoizes the memory plan per (projectDir + scanner-relevant config) within a single process. Helps cross-command flows where `guard` then `sync` would otherwise rebuild the plan twice. New `clearMemoryPlanCache()` export for tests. Single-`guard` runs see no change (only one caller per process).
+- **P2: `walkDir` cache in `cli/scanners/schemas.mjs`.** `walkDir` was called 8× inside `scanSchemasDeep` for different entity types (Pydantic, Mongoose, Prisma, SQLAlchemy, Sequelize, GORM, Sqlx, Hibernate). Now caches the file list per directory; subsequent callers iterate an array instead of re-traversing. Net gain on wu's mixed Python+TS stack is modest (~3% of total validator time) but real, and helps on stacks where multiple scanners hit the same root dir.
+- **Combined P1+P2+P3 result on wu**: full guard 1456ms → 1431ms (~2%). `--changed-only` covers 5/22 validators in 116ms (vs 1456ms full = **12.6× faster**).
+
+### Internal
+
+- **2 new test files**: `tests/scoping-extended.test.mjs` (4 tests covering P3) and `tests/stress-test.test.mjs` (2 stress tests + 1 always-passes smoke). **Total: 492 → 497 tests (+5 — stress tests opt-in via STRESS=1).**
+- New helpers: `clearMemoryPlanCache()`, `clearWalkDirCache()`, `_scanTodoFile()`.
+- `schemas/docguard-config.schema.json` is the first non-code file under `schemas/` — added to `package.json#files` so it ships in the npm tarball.
+- `.docguard.json` now self-documents via `$schema` reference when created by `init`.
+- Dry-run on wu: **672/672 PASS in 1.43s**.
+- No new NPM deps.
+
+### Out of scope (deferred to v0.16)
+
+- **Deeper Generated-Staleness optimization** — still the slowest validator at 26% of guard time on wu. The cache helps cross-command flows but not single-guard runs. Next attack vector: stream `buildMemoryPlan` so it yields partial results as scanners complete, letting the validator early-exit on the first non-stale section.
+- **`upgrade --apply --pr` battle-test** on a real GitHub repo. Logic shipped in v0.14; end-to-end PR creation hasn't been tested against a live remote with branch protections.
+- **Cross-process memoization** — if guard / sync / fix runs in CI sequentially, they each rebuild the plan. A serialized cache under `.docguard/plan.cache.json` (keyed by a tree-state hash) would share across processes.
+- **Tree-state hashing for plan cache invalidation** — currently the in-process cache assumes the tree doesn't change mid-run. A proper hash would let long-running `watch` mode keep a stable cache that only invalidates on actual file changes.
+
+## [0.14.1] - 2026-05-26
+
+Patch + small feature release responding to the wu-whatsappinbox v0.12 feedback.
+**492 tests** (was 481, +11). 22 validators.
+
+### Fixed
+
+- **N-1: Metrics-Consistency double-counted warnings.** When a doc mentioned the stale validator/check count multiple times (e.g. once in a heading, once in a body table), the validator emitted one warning per regex match — producing "4 warnings for 2 files" on wu-whatsappinbox. Now dedupes by `(file, label, found-value)` so a single file contributes ONE warning per distinct drift value. The `replace-count` mechanical fix already uses replace-all semantics, so one fix per (file, label) is sufficient. **Reported by wu-whatsappinbox.**
+
+### Added
+
+- **S-12+: High-confidence anchor matches now auto-fix via `fix --write`.** v0.13.1 added "did you mean #X?" hints when Cross-Reference flagged a broken anchor. v0.14.1 takes the next step: when the suggested anchor is **unambiguous** (edit distance ≤ 2 AND no other candidates within the same distance), the warning is tagged `[auto-fixable]` and the validator emits a `replace-anchor` mechanical fix. New `replace-anchor` applier in `cli/writers/mechanical.mjs` rewrites only the anchor inside markdown link form `](#X)`, leaves plain-text occurrences and link text alone, is idempotent. **Three of five wu broken-anchor cases in v0.12.0 were "heading renamed, link not updated" — those are now `fix --write`-resolvable.**
+
+### Note to wu — the "still open" suggestions are all already shipped
+
+The S-1, S-11, S-12 items in the v0.12 feedback letter all shipped earlier. The user just needs to upgrade:
+
+- **S-1** (`sync --since <ref>` surgical refresh) → shipped in **v0.13.0** as L-1. Run `docguard sync --write --since main` to refresh only sections touched by code in the diff.
+- **S-11** (changed-file → affected-doc map) → shipped in **v0.13.1** as the `docguard impact` command. Run `docguard impact --since HEAD~1` after a commit; JSON mode for CI bots.
+- **S-12** (anchor "did you mean..." hints) → shipped in **v0.13.1**. Extended in this release (v0.14.1) so high-confidence matches are auto-fixable.
+
+Run `docguard upgrade --apply` (or `npm i -g docguard-cli@latest`) to pick all of these up.
+
+### Internal
+
+- **2 new test files**: `tests/metrics-dedup.test.mjs` (4) and `tests/anchor-autofix.test.mjs` (7). **Total: 481 → 492 tests (+11).**
+- **New mechanical fix type**: `replace-anchor`. The APPLIERS registry now lists 6 types.
+- **New helper** in `cli/validators/cross-reference.mjs`: `isUnambiguousSuggestion()` — gates the auto-fix on edit distance ≤ 2 AND single close candidate.
+- No new NPM deps.
+
+### Out of scope (deferred to v0.15)
+
+Same backlog as v0.14:
+- Generated-Staleness perf optimization (33% of validator time).
+- Shared tree walk.
+- Cross-validator `config.changedFiles` opt-in.
+- `upgrade --pr` battle-test.
+
 ## [0.14.0] - 2026-05-26
 
 Feature release closing the v0.13 backlog (4 features) + 2 quality investments

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: docguard-cli
-Version: 0.14.0
+Version: 0.15.1
 Summary: The enforcement tool for Canonical-Driven Development (CDD). Audit, generate, and guard your project documentation. Zero dependencies.
 Project-URL: Homepage, https://github.com/raccioly/docguard
 Project-URL: Documentation, https://github.com/raccioly/docguard#readme

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/commands/guard.mjs

@@ -198,7 +198,7 @@ export function runGuardInternal(projectDir, config) {
  * Freshness (git log), Traceability (REQ scan), Doc-Quality (prose lint) —
  * stay off for speed.
  */
-export const CHANGED_ONLY_VALIDATORS = ['docsSync', 'environment', 'apiSurface'];
+export const CHANGED_ONLY_VALIDATORS = ['docsSync', 'environment', 'apiSurface', 'drift', 'todoTracking'];
 
 /**
  * Build a validators map that enables only the pre-commit-lite set.

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/commands/init.mjs

@@ -167,6 +167,10 @@ export async function runInit(projectDir, config, flags) {
     const ptc = typeDefaults[detectedType] || typeDefaults.unknown;
 
     const defaultConfig = {
+      // v0.15-P4: $schema reference enables VS Code / IDE autocomplete +
+      // validation for .docguard.json fields. Picked up by any
+      // JSON-Schema-aware editor; ignored by DocGuard itself.
+      $schema: 'https://raccioly.github.io/docguard/schemas/docguard-config.schema.json',
       projectName: config.projectName,
       version: '0.5',
       profile: profileName,

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/scanners/memory-plan.mjs

@@ -29,13 +29,58 @@ const md = {
   },
 };
 
+/**
+ * v0.15-P1: in-process cache. buildMemoryPlan is expensive (~400ms on
+ * wu-whatsappinbox, 33% of total guard validator time) because it triggers
+ * routes/schemas/screens/frontend scanners — all of which walk the source
+ * tree. Within a single guard run, sync, generate, and the Generated-
+ * Staleness validator all ask for the SAME plan; without caching they each
+ * re-pay the cost.
+ *
+ * Cache key: projectDir + a config fingerprint that captures the fields the
+ * scanners actually consume (sourceRoot, ignore, projectType). Other config
+ * mutations (e.g. changedFiles per-validator) don't invalidate the plan.
+ *
+ * Bypass with `_skipCache: true` in opts — used by tests and any caller that
+ * wants a fresh scan.
+ */
+const _memoryPlanCache = new Map(); // key → plan
+
+export function clearMemoryPlanCache() {
+  _memoryPlanCache.clear();
+}
+
+function _cacheKey(projectDir, config) {
+  return JSON.stringify({
+    dir: projectDir,
+    sourceRoot: config.sourceRoot,
+    ignore: Array.isArray(config.ignore) ? [...config.ignore].sort() : null,
+    projectType: config.projectType,
+    profile: config.profile,
+  });
+}
+
 /**
  * Build the full memory plan for a project.
  * @returns {{ profile, surface, docs, agentTasks }}
  *   docs[].sections[]: { id, source:'code', body } OR { id, source:'human', task, grounding }
  *   agentTasks: flattened prose tasks the AI must write.
  */
-export function buildMemoryPlan(projectDir, config = {}) {
+export function buildMemoryPlan(projectDir, config = {}, opts = {}) {
+  if (!opts._skipCache) {
+    const key = _cacheKey(projectDir, config);
+    const cached = _memoryPlanCache.get(key);
+    if (cached) return cached;
+  }
+  const result = _buildMemoryPlanUncached(projectDir, config);
+  if (!opts._skipCache) {
+    _memoryPlanCache.set(_cacheKey(projectDir, config), result);
+  }
+  return result;
+}
+
+// Original implementation, renamed so the public buildMemoryPlan can wrap it.
+function _buildMemoryPlanUncached(projectDir, config = {}) {
   const profile = detectProjectProfile(projectDir, config);
   const primaryFramework = profile.primary?.framework || profile.frameworks[0] || '';
 

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/scanners/schemas.mjs

@@ -690,20 +690,45 @@ function readFileSafe(path) {
   try { return readFileSync(path, 'utf-8'); } catch { return null; }
 }
 
+// v0.15-P2: walkDir is called 8 times across schemas.mjs (Pydantic, Mongoose,
+// Prisma, SQLAlchemy, Sequelize, GORM, Sqlx, Hibernate). Each call walks the
+// same tree. Cache the file list per (dir, extension-set) so subsequent
+// callers iterate an array instead of re-traversing.
+//
+// Cache key: just the dir path. The extension filter is constant across all
+// callers (the regex hard-coded below), so a single cache slot per dir works.
+// Lifetime: per-process. `clearWalkDirCache()` invalidates for tests.
+const _walkDirCache = new Map(); // dir → string[] of file paths
+
+export function clearWalkDirCache() {
+  _walkDirCache.clear();
+}
+
+const _CODE_FILE_RE = /\.(js|mjs|cjs|ts|tsx|jsx|py|rs|go|java|kt|rb)$/;
+
+function _collectFiles(dir, out) {
+  let entries;
+  try { entries = readdirSync(dir, { withFileTypes: true }); } catch { return; }
+  for (const entry of entries) {
+    if (IGNORE_DIRS.has(entry.name) || entry.name.startsWith('.')) continue;
+    const fullPath = join(dir, entry.name);
+    if (entry.isDirectory()) {
+      _collectFiles(fullPath, out);
+    } else if (entry.isFile() && _CODE_FILE_RE.test(entry.name)) {
+      out.push(fullPath);
+    }
+  }
+}
+
 function walkDir(dir, callback) {
   if (!existsSync(dir)) return;
-  try {
-    const entries = readdirSync(dir, { withFileTypes: true });
-    for (const entry of entries) {
-      if (IGNORE_DIRS.has(entry.name) || entry.name.startsWith('.')) continue;
-      const fullPath = join(dir, entry.name);
-      if (entry.isDirectory()) {
-        walkDir(fullPath, callback);
-      } else if (entry.isFile() && /\.(js|mjs|cjs|ts|tsx|jsx|py|rs|go|java|kt|rb)$/.test(entry.name)) {
-        callback(fullPath);
-      }
-    }
-  } catch { /* skip */ }
+  let files = _walkDirCache.get(dir);
+  if (!files) {
+    files = [];
+    _collectFiles(dir, files);
+    _walkDirCache.set(dir, files);
+  }
+  for (const f of files) callback(f);
 }
 
 /**

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/validators/cross-reference.mjs

@@ -27,7 +27,7 @@
  */
 
 import { existsSync, readFileSync, readdirSync, statSync } from 'node:fs';
-import { resolve, join, dirname, basename } from 'node:path';
+import { resolve, join, dirname, basename, relative } from 'node:path';
 
 /**
  * Slugify a heading the way GitHub's markdown anchors work.
@@ -294,6 +294,7 @@ function collectCanonicalDocs(projectDir) {
 export function validateCrossReferences(projectDir, _config = {}) {
   const errors = [];
   const warnings = [];
+  const fixes = [];
   let passed = 0;
   let total = 0;
 
@@ -364,13 +365,27 @@ export function validateCrossReferences(projectDir, _config = {}) {
         if (!matches) {
           const where = targetPath === docPath ? 'same doc' : basename(targetPath);
           // S-12: suggest the closest matching anchor when there's a near-miss.
-          // Three of five wu user-fixes were "heading renamed, link not updated"
-          // — a suggested-slug hint makes those deterministic-fixable.
           const suggestion = anchors ? suggestAnchor(normalizedAnchor, anchors) : null;
           const hint = suggestion ? ` (did you mean #${suggestion}?)` : '';
+          // v0.14.1-S12+: when the suggestion is HIGH-CONFIDENCE — unambiguous
+          // and very close (edit distance <= 2) — emit a mechanical fix so
+          // `docguard fix --write` resolves it without AI. Other near-misses
+          // still get the hint but no fix (the user needs to verify intent).
+          const isHighConfidence = suggestion && isUnambiguousSuggestion(normalizedAnchor, suggestion, anchors);
           warnings.push(
-            `${docName}:${ref.line} — broken anchor: "#${ref.anchor}" in ${where} doesn't match any heading${hint}`
+            `${docName}:${ref.line} — broken anchor: "#${ref.anchor}" in ${where} doesn't match any heading${hint}` +
+            (isHighConfidence ? ' [auto-fixable]' : '')
           );
+          if (isHighConfidence) {
+            fixes.push({
+              type: 'replace-anchor',
+              doc: relative(projectDir, docPath),
+              line: ref.line,
+              from: ref.anchor,
+              to: suggestion,
+              summary: `${docName}:${ref.line} #${ref.anchor} → #${suggestion}`,
+            });
+          }
           continue;
         }
       }
@@ -379,5 +394,28 @@ export function validateCrossReferences(projectDir, _config = {}) {
     }
   }
 
-  return { errors, warnings, passed, total };
+  return { errors, warnings, passed, total, fixes };
+}
+
+/**
+ * v0.14.1-S12+ — is the suggested anchor an unambiguous, high-confidence
+ * match? Two criteria, both must hold:
+ *   1. Edit distance between the broken anchor and the suggestion is <= 2
+ *      (catches typos and minor renames, refuses major slug rewrites).
+ *   2. The suggestion is the ONLY anchor that close — no other anchor
+ *      within distance <= 2. Avoids fixing to the wrong candidate when
+ *      multiple are similar.
+ */
+function isUnambiguousSuggestion(broken, suggestion, anchors) {
+  if (!broken || !suggestion || !anchors) return false;
+  const sugDist = editDistance(broken, suggestion);
+  if (sugDist > 2) return false;
+  // Count other anchors that are also within the same tight budget.
+  let closeCandidates = 0;
+  for (const a of anchors) {
+    if (a === suggestion) continue;
+    if (editDistance(broken, a) <= 2) closeCandidates++;
+    if (closeCandidates > 0) return false; // ambiguous
+  }
+  return true;
 }

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/validators/drift.mjs

@@ -20,21 +20,27 @@ const IGNORE_DIRS = new Set([
 export function validateDrift(projectDir, config) {
   const results = { name: 'drift', errors: [], warnings: [], passed: 0, total: 0 };
 
-  // Find all // DRIFT: comments in source code
-  const driftComments = [];
-  walkDir(projectDir, (filePath) => {
+  // v0.15-P3: when config.changedFiles is set (--changed-only mode), only
+  // visit the listed paths. Drift comments in unchanged files are still in
+  // git so they'll be caught by a full guard run; pre-commit hooks care
+  // about NEW drift comments in this commit.
+  const scanFile = (filePath) => {
     const ext = extname(filePath);
     if (!CODE_EXTENSIONS.has(ext)) return;
-
-    const content = readFileSync(filePath, 'utf-8');
-
-    // Fast early-return: skip expensive string split if no comment exists
+    // v0.15 hotfix: test files commonly contain literal `// DRIFT:` inside
+    // string fixtures (e.g. `'// DRIFT: a-drift\n'`). Reading the test as
+    // source would treat the string as a real drift comment. Skip test
+    // files unless the user opts in — same pattern TODO-Tracking uses.
+    const rel = filePath.replace(projectDir + '/', '');
+    const includeTests = config?.drift?.includeTestFiles === true;
+    if (!includeTests && /(^|\/)(__tests__|tests?|spec)\/|\.(test|spec)\.[^.]+$/.test(rel)) {
+      return;
+    }
+    let content;
+    try { content = readFileSync(filePath, 'utf-8'); } catch { return; }
     if (!content.includes('DRIFT:')) return;
-
     const lines = content.split('\n');
-
     lines.forEach((line, i) => {
-      // Match various comment styles: // DRIFT:, # DRIFT:, /* DRIFT:, -- DRIFT:
       const match = line.match(/(?:\/\/|#|\/\*|\-\-)\s*DRIFT:\s*(.+)/i);
       if (match) {
         driftComments.push({
@@ -44,7 +50,16 @@ export function validateDrift(projectDir, config) {
         });
       }
     });
-  });
+  };
+
+  const driftComments = [];
+  if (Array.isArray(config.changedFiles) && config.changedFiles.length > 0) {
+    for (const rel of config.changedFiles) {
+      scanFile(resolve(projectDir, rel));
+    }
+  } else {
+    walkDir(projectDir, scanFile);
+  }
 
   if (driftComments.length === 0) {
     // No // DRIFT: comments to reconcile — not applicable (NOT a pass).

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/validators/metrics-consistency.mjs

@@ -64,6 +64,14 @@ export function validateMetricsConsistency(projectDir, config, guardResults) {
     { key: 'validators', regex: /(?<!\d\/)\b(\d{2,})\s+validators?\b/gi, label: 'validators' },
   ];
 
+  // v0.14.1-N1: dedup by (file, label, found) — a file that mentions the
+  // stale number multiple times produces ONE warning, not one per occurrence.
+  // The replace-count applier already uses replace-all semantics, so a single
+  // fix per (file, label) is sufficient. Previously: "X.md" appearing 2× with
+  // the same drift would generate 2 warnings + 2 fixes (the second a no-op).
+  const reportedDrift = new Set();      // key: `${relPath}|${label}|${found}`
+  const reportedPass  = new Set();      // key: `${relPath}|${label}` — only count one pass per (file, label)
+
   for (const mdFile of mdFiles) {
     const relPath = relative(projectDir, mdFile);
     // Skip changelog (historical numbers are fine by definition)
@@ -79,16 +87,32 @@ export function validateMetricsConsistency(projectDir, config, guardResults) {
 
       regex.lastIndex = 0;
       let match;
+      // Collect distinct (found-value) instances within THIS file first,
+      // then emit ONE warning per distinct value. A file that says "20" on
+      // line 5 and "20" on line 50 is the same drift; "20" on line 5 and
+      // "19" on line 50 are two distinct drifts.
+      const distinctFoundInFile = new Set();
       while ((match = regex.exec(content)) !== null) {
-        total++;
-        const found = parseInt(match[1], 10);
-        if (found !== actuals[key] && found > 0) {
+        distinctFoundInFile.add(parseInt(match[1], 10));
+      }
+      if (distinctFoundInFile.size === 0) continue;
+
+      for (const found of distinctFoundInFile) {
+        if (found > 0 && found !== actuals[key]) {
+          const driftKey = `${relPath}|${label}|${found}`;
+          if (reportedDrift.has(driftKey)) continue;
+          reportedDrift.add(driftKey);
+          total++;
           warnings.push(
             `${relPath} says "${found} ${label}" but actual count is ${actuals[key]}. Fix with \`docguard fix --write\``
           );
-          // Deterministic, surgical token replacement — safe to auto-apply.
           fixes.push({ type: 'replace-count', file: relPath, label, found, actual: actuals[key] });
         } else {
+          // Matches the actual count — one pass per (file, label), not per occurrence.
+          const passKey = `${relPath}|${label}`;
+          if (reportedPass.has(passKey)) continue;
+          reportedPass.add(passKey);
+          total++;
           passed++;
         }
       }

{docguard_cli-0.14.0 → docguard_cli-0.15.1}/cli/validators/todo-tracking.mjs

@@ -329,6 +329,20 @@ function isSelfPath(fullPath) {
 }
 
 function findTodos(rootDir, dir, todos, config) {
+  // v0.15-P3: when config.changedFiles is set (--changed-only mode), only
+  // scan those paths. New TODOs in this commit get caught; pre-existing
+  // TODOs in unchanged files are still tracked by full guard runs.
+  if (dir === rootDir && Array.isArray(config?.changedFiles) && config.changedFiles.length > 0) {
+    for (const rel of config.changedFiles) {
+      const full = resolve(rootDir, rel);
+      let stat;
+      try { stat = statSync(full); } catch { continue; }
+      if (!stat.isFile()) continue;
+      _scanTodoFile(rootDir, full, todos, config);
+    }
+    return;
+  }
+
   let entries;
   try { entries = readdirSync(dir); } catch { return; }
 
@@ -345,47 +359,44 @@ function findTodos(rootDir, dir, todos, config) {
     if (stat.isDirectory()) {
       findTodos(rootDir, full, todos, config);
     } else {
-      const ext = extname(entry).toLowerCase();
-      if (!SOURCE_EXTENSIONS.has(ext)) continue;
-
-      const relPath = relative(rootDir, full);
-
-      // Skip test files unless explicitly opted in — test fixture strings
-      // commonly contain comment markers inside template literals that the
-      // single-line heuristic can't distinguish from real comments.
-      if (!includeTests && isTestFilePath(relPath)) continue;
-
-      // Skip the validator's own source file — its docstring legitimately
-      // names the annotation keywords it scans for.
-      if (isSelfPath(full)) continue;
-
-      // Apply config ignore patterns (todoIgnore + global ignore)
-      if (config && shouldIgnore(relPath, config, 'todoIgnore')) continue;
-
-      let content;
-      try { content = readFileSync(full, 'utf-8'); } catch { continue; }
-
-      // Fast early-return: skip expensive string split if no TODO patterns exist
-      if (!TODO_PATTERN.test(content)) continue;
-
-      const lines = content.split('\n');
-
-      for (let i = 0; i < lines.length; i++) {
-        // Restrict scanning to text inside a comment — keeps the regex from
-        // matching its own keyword list when DocGuard reads its own source.
-        const commentText = commentPortion(lines[i]);
-        if (commentText === null) continue;
-        if (TODO_PATTERN.test(commentText)) {
-          const match = commentText.match(TODO_EXTRACT);
-          if (match) {
-            todos.push({
-              keyword: match[1].toUpperCase(),
-              text: match[2].trim(),
-              file: relPath,
-              line: i + 1,
-            });
-          }
-        }
+      _scanTodoFile(rootDir, full, todos, config);
+    }
+  }
+}
+
+/**
+ * v0.15-P3: per-file TODO scan extracted so both the full-tree walker and
+ * the --changed-only path can reuse it. Honors test-file filtering,
+ * self-path skip, ignore patterns, and the TODO regex.
+ */
+function _scanTodoFile(rootDir, full, todos, config) {
+  const includeTests = config?.todoTracking?.includeTestFiles === true;
+  const ext = extname(full).toLowerCase();
+  if (!SOURCE_EXTENSIONS.has(ext)) return;
+
+  const relPath = relative(rootDir, full);
+
+  if (!includeTests && isTestFilePath(relPath)) return;
+  if (isSelfPath(full)) return;
+  if (config && shouldIgnore(relPath, config, 'todoIgnore')) return;
+
+  let content;
+  try { content = readFileSync(full, 'utf-8'); } catch { return; }
+  if (!TODO_PATTERN.test(content)) return;
+
+  const lines = content.split('\n');
+  for (let i = 0; i < lines.length; i++) {
+    const commentText = commentPortion(lines[i]);
+    if (commentText === null) continue;
+    if (TODO_PATTERN.test(commentText)) {
+      const match = commentText.match(TODO_EXTRACT);
+      if (match) {
+        todos.push({
+          keyword: match[1].toUpperCase(),
+          text: match[2].trim(),
+          file: relPath,
+          line: i + 1,
+        });
       }
     }
   }