peaks-loop 4.1.0 → 4.1.2

package/dist/services/codegraph/codegraph-exclude-reconciler.js

@@ -1,6 +1,5 @@
 // src/services/codegraph/codegraph-exclude-reconciler.ts
 //
-// Slice S1 of `2026-09-12-codegraph-exclude-integrity` — the pure
 // reconciliation core. It answers one question:
 //
 //   "Which git-tracked source files does the codegraph `exclude` list
@@ -34,10 +33,9 @@
 // uses `//` lines. Do not convert them to `/* ... */`.
 import { execFileSync } from 'node:child_process';
 import { readFileSync } from 'node:fs';
-import { join } from 'node:path';
 import picomatch from 'picomatch';
 import { normalizePath } from '../../shared/path-utils.js';
-import { CODEGRAPH_DIR_NAME } from './codegraph-service.js';
+import { codegraphConfigSourceFor, resolveCodegraphConfigSource } from './codegraph-project-config.js';
 // ─────────────────────────────────────────────────────────────────────
 // Glob matching — delegated to `picomatch`, the same engine upstream uses
 //
@@ -129,6 +127,32 @@ export function compileCodegraphGlobs(patterns) {
         }
     };
 }
+// The tracked files an `exclude` rule can actually cost the index, per model.
+//
+// WHY THIS IS MODEL-DEPENDENT (the 1.6.2 defect). A rule that only blocks files
+// upstream would not ingest is harmless, so the reconciler always pre-filtered
+// the tracked list — with the config's `include` globs, which is right only
+// when `include` IS the whitelist (0.7.x). Under 1.6.x selection is
+// `.gitignore`-driven and `include` can only force files IN, so an absent
+// list admits NOTHING: the candidate set came out empty, no rule could ever be
+// a violation, and the gate reported clean on every 1.6.x project while its own
+// `exclude` rules silently dropped tracked source. `force-include` answers
+// the same question with upstream's own extractor decision — the oracle the
+// index axis uses — so both axes agree on what upstream would ingest.
+//
+// `supportsPath` omitted keeps every tracked file: a caller with no oracle
+// reports MORE, never less, so the failure direction is a reviewable false
+// positive rather than a silent pass.
+function excludeCandidates(input) {
+    if (input.admissionModel !== 'force-include') {
+        return filterAdmittedTrackedFiles(input.trackedFiles, input.include);
+    }
+    const supportsPath = input.supportsPath;
+    if (supportsPath === undefined) {
+        return input.trackedFiles.map((file) => normalizePath(file));
+    }
+    return input.trackedFiles.map((file) => normalizePath(file)).filter((file) => supportsPath(file));
+}
 // The project-relative paths of the tracked files the config's `include`
 // globs admit, normalized. This is the ONE place the "would the index
 // ingest this path" question is answered, so this reconciler and the
@@ -165,7 +189,7 @@ export function reconcileCodegraphExclude(input) {
     // is the same verdict as an explicitly empty `include` list, so it
     // needs no special case here.
     const excludeRules = compileRules(input.exclude);
-    const trackedSourceFiles = filterAdmittedTrackedFiles(input.trackedFiles, input.include);
+    const trackedSourceFiles = excludeCandidates(input);
     const violations = [];
     const offendingRules = new Set();
     const blockedFiles = new Set();
@@ -187,11 +211,6 @@ export function reconcileCodegraphExclude(input) {
     };
 }
 // ─────────────────────────────────────────────────────────────────────
-// Thin boundary adapters — READ ONLY
-// ─────────────────────────────────────────────────────────────────────
-// Upstream `CONFIG_FILENAME` inside `<projectRoot>/.codegraph/`.
-export const CODEGRAPH_CONFIG_FILENAME = 'config.json';
-// ─────────────────────────────────────────────────────────────────────
 // Read provenance — why the shared-input seam refuses a fabricated value
 // ─────────────────────────────────────────────────────────────────────
 // Code review R4-1. The shared-input seam (perf F1) hands an inspector the
@@ -275,19 +294,63 @@ export function assertStringArray(value, field, configPath) {
     }
     return value;
 }
-// Read `<projectRoot>/.codegraph/config.json` and return just the two
-// glob lists the reconciler needs. Read-only: this module never writes
-// that file. Returns a READ-MARKED config — see `readTrackedFiles`.
+// Every key of the 1.6.x project config is OPTIONAL: upstream returns an empty
+// list for an absent one and only warns-and-skips a wrong-typed one. So a
+// hand-authored `codegraph.json` carrying only `exclude` is VALID, and treating
+// it as malformed would turn a legitimate project into exit 76. The line is
+// kept exact — absent → `[]`, present-but-not-an-array → throw, because
+// ignoring the second is how a wrong list survives a gate that reported clean.
+export function optionalStringArray(value, field, configPath) {
+    return value === undefined ? [] : assertStringArray(value, field, configPath);
+}
+// Read this project's codegraph config — the file the INSTALLED upstream reads
+// (`resolveCodegraphConfigSource`), not a path spelled here — and return just
+// the glob lists the reconciler needs, plus the source they came from.
+// Read-only, and READ-MARKED (see `readTrackedFiles`).
+//
+// ABSENCE IS NOT ONE THING — it is read per model:
+//
+//   - `force-include` (1.6.x): a missing `<root>/codegraph.json` is upstream's
+//     own documented ZERO-CONFIG DEFAULT, and its parser returns an empty
+//     config for it without throwing. Throwing here WAS the 1.6.2 defect:
+//     every freshly initialised project reported `index integrity could not be
+//     evaluated` and exited 76, over a config whose absence means "nothing
+//     withheld, nothing forced in".
+//   - `include-whitelist` (0.7.x): a missing config means the withholding list
+//     is unknown, so the read still throws.
+//
+// A file that EXISTS but does not parse throws in BOTH models: upstream
+// degrades a malformed config to the defaults, which is exactly the silent
+// pass this gate exists to prevent.
 export function readCodegraphExcludeConfig(projectRoot) {
-    const configPath = join(projectRoot, CODEGRAPH_DIR_NAME, CODEGRAPH_CONFIG_FILENAME);
+    return readCodegraphConfigFrom(projectRoot, resolveCodegraphConfigSource(projectRoot).model);
+}
+// `readCodegraphExcludeConfig` for a KNOWN model — the same split
+// `codegraphConfigSourceFor` makes, for the same reason: the model decides the
+// ABSENCE semantics as well as the path, so both arms must be drivable without
+// an install of the upstream that selects them.
+export function readCodegraphConfigFrom(projectRoot, model) {
+    const source = codegraphConfigSourceFor(projectRoot, model);
+    const { configPath } = source;
+    if (!source.present) {
+        if (model === 'force-include') {
+            return markAsRead({ configPath, present: false, model, include: [], exclude: [] });
+        }
+        // `readFileSync` still raises the ENOENT, so the operator-facing message
+        // keeps naming the path it looked for, as it always did.
+        readFileSync(configPath, 'utf8');
+    }
     const parsed = JSON.parse(readFileSync(configPath, 'utf8'));
     if (typeof parsed !== 'object' || parsed === null) {
         throw new Error(`codegraph config ${configPath}: expected a JSON object`);
     }
     const record = parsed;
     return markAsRead({
-        include: assertStringArray(record.include, 'include', configPath),
-        exclude: assertStringArray(record.exclude, 'exclude', configPath)
+        configPath,
+        present: true,
+        model,
+        include: optionalStringArray(record.include, 'include', configPath),
+        exclude: optionalStringArray(record.exclude, 'exclude', configPath)
     });
 }
 // Read both shared inputs exactly once, in the one place that owns the
@@ -322,8 +385,14 @@ export function resolveSharedConfig(supplied, projectRoot) {
 // Read-only entry point: resolve the project's tracked files + codegraph
 // config from disk and reconcile them. S2's repair path consumes this
 // result and writes the reduced `exclude` list back; S1 only computes.
-export function reconcileCodegraphExcludeFromProject(projectRoot) {
+export function reconcileCodegraphExcludeFromProject(projectRoot, supportsPath) {
     const trackedFiles = readTrackedFiles(projectRoot);
-    const { include, exclude } = readCodegraphExcludeConfig(projectRoot);
-    return reconcileCodegraphExclude({ trackedFiles, include, exclude });
+    const config = readCodegraphExcludeConfig(projectRoot);
+    return reconcileCodegraphExclude({
+        trackedFiles,
+        include: config.include,
+        exclude: config.exclude,
+        admissionModel: config.model,
+        supportsPath
+    });
 }

package/dist/services/codegraph/codegraph-exclude-repair.d.ts

@@ -1,64 +1,14 @@
 import { type CodegraphProcessRunner } from './codegraph-service.js';
-import { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude, repairCodegraphInclude, type CodegraphConfigRepairOutcome, type CodegraphConfigRepairPlan, type CodegraphExcludeRepairPlan } from './codegraph-config-repair-writer.js';
-export { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude, repairCodegraphInclude };
+import { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude, type CodegraphConfigRepairOutcome, type CodegraphConfigRepairPlan, type CodegraphExcludeRepairPlan } from './codegraph-config-repair-writer.js';
+export { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude };
 export type { CodegraphConfigRepairOutcome, CodegraphConfigRepairPlan, CodegraphExcludeRepairPlan };
 export type CodegraphExcludeRepairReport = {
     /** True when the config was actually rewritten. */
     readonly applied: boolean;
     /** Rules dropped from `exclude`. */
     readonly rulesRemoved: readonly string[];
-    /**
-     * Patterns appended to `include` (slice-002). Always a subset of the
-     * include reconciler's candidates that were not already admitted.
-     */
-    readonly includePatternsAdded: readonly string[];
     /** Distinct tracked source files the dropped rules had been hiding. */
     readonly filesRecovered: number;
-    /**
-     * Distinct tracked source files the WIDENED `include` list newly admits —
-     * the INCLUDE axis' counterpart of `filesRecovered`, and a DIFFERENT
-     * number on purpose.
-     *
-     * `filesRecovered` counts the exclude axis only. Before this field
-     * existed, `appliedRepairNote` printed `filesRecovered` inside a sentence
-     * whose subject was both axes, so the measured run that added 5 include
-     * patterns for 31 tracked `.mjs`/`.cjs` files reported "removed 0 exclude
-     * rule(s), recovering 0 tracked source file(s)" — a true statement about
-     * one axis read as a verdict on both (defect A1 of
-     * `2026-09-17-codegraph-msg-and-refresh`).
-     *
-     * It is a measured DELTA, not a re-report of an absolute count:
-     * `includeAdmittedAfter` minus the same admission measurement taken over
-     * the ON-DISK include list. Reporting `includeAdmittedAfter` itself as
-     * "recovered" would be the tautology slice-002 removed from the
-     * coverage ratio (an absolute count says nothing about what changed).
-     *
-     * Zero by construction when the include plan did not change — the
-     * normalized list IS the on-disk list then — which is also why the extra
-     * admission pass is gated on `includePlan.changed`: the no-op path (every
-     * automatic seam, every re-run) pays nothing for it, unlike the pass
-     * slice-002 removed (that one ran on ALL seams, including no-ops).
-     */
-    readonly includeFilesRecovered: number;
-    /**
-     * Tracked files the normalized `include` list admits — the NUMERATOR of
-     * the coverage ratio. Identical to
-     * `reconcileCodegraphExclude`'s `trackedSourceCount` for the normalized
-     * list, so it costs no second filtering pass.
-     */
-    readonly includeAdmittedAfter: number;
-    /**
-     * Tracked files upstream's extractor would ingest (any supported
-     * extension) — the DENOMINATOR, and the same quantity the index axis
-     * reports under this same field name (`CodegraphIndexIntegrityReport`).
-     *
-     * It is measured independently of `includeAdmittedAfter` (an extension
-     * decision per tracked file, not a glob match), so the two CAN differ and
-     * the ratio can report a shortfall. The field used to be fed from the
-     * reconciler's admitted count, i.e. the numerator again, which made every
-     * "N of N" the consumers printed a tautology.
-     */
-    readonly trackedSourceCount: number;
     /**
      * Absolute path of the rewritten config. Empty when nothing was written
      * AND the reads failed (there is no config to name).
@@ -153,16 +103,14 @@ export type CodegraphExcludeRepairOptions = {
     readonly reindex?: boolean | 'force';
 };
 /**
- * Reconcile `projectRoot`'s config against its tracked files — normalize
- * `include`, then drop the `exclude` rules that block tracked source files
- * — and rebuild the index so the recovered files actually land in it.
+ * Reconcile `projectRoot`'s config against its tracked files — drop the
+ * `exclude` rules that block tracked source files — and rebuild the index so
+ * the recovered files actually land in it.
  *
- * ORDER IS LOAD-BEARING. `exclude` is reconciled against the NORMALIZED
- * include list, never the on-disk one: an `exclude` rule that blocks only a
- * file `include` drops reconciles clean today and starts biting the moment
- * `include` is widened, so reconciling before normalizing would let this
- * run report success over a config it had just made worse. See the module
- * header.
+ * The reconciliation runs the config's OWN `include` filter first, exactly as
+ * upstream applies it, so a rule that only blocks files the index would not
+ * ingest anyway is not a violation. See the module header for what this seam
+ * no longer does and why.
  *
  * This is the ONE shared "after upstream init" self-heal: the CLI's
  * fresh `peaks codegraph init`, the pre-dispatch preflight and the

package/dist/services/codegraph/codegraph-exclude-repair.js

@@ -1,55 +1,49 @@
 // src/services/codegraph/codegraph-exclude-repair.ts
 //
-// Slice S2 of `2026-09-12-codegraph-exclude-integrity` — the WRITE path.
-// WIDENED by slice-002 of `2026-09-16-codegraph-index-integrity` from one
-// axis to BOTH config axes; the file name and the entry point's name are
+// reconcilers to the config axes; the file name and the entry point's name are
 // retained because three seams import them by name and the exclude axis is
-// still the entry condition. See the ordering note below — the widening is
-// not a second feature bolted on, it is what makes the exclude repair
-// correct.
+// still the entry condition.
+//
+// ── THE INCLUDE AXIS IS GONE (1.6.2 upgrade) ──────────────────────────
+//
+// This seam used to repair BOTH axes: it appended the extensions upstream's
+// own default `include` template omitted, then reconciled `exclude` against
+// that widened list. 1.6.x removed both halves of the premise. It ships no
+// `include` template at all, and it inverted what `include` MEANS: upstream's
+// own description is now "first-party source to force INTO the index even when
+// `.gitignore` drops it", while selection became `.gitignore`-driven. So the
+// candidate set stopped being "the five extensions the template forgot" and
+// became every extension the extractor supports — and appending those would
+// not have covered a gap, it would have told upstream to index gitignored
+// source. That is a defect, not a deferral, so the axis and its reconciler
+// were deleted rather than left pending.
+//
+// The exclude axis survives, and its job is now STRICTLY NARROWER than it was.
+// It used to hunt two things: a rule from upstream's 99-entry default template
+// that collided with real source (1.6.x ships no such template, so that class
+// is gone), and a rule a project AUTHORED that blocks its own tracked source.
+// The second is live — `codegraph.json`'s `exclude` still means "keep OUT of
+// the index even when git-tracked" — and it is what this seam repairs.
 //
 // The reconcilers compute; this module applies. Two callers are allowed to
 // reach it and nothing else is:
 //
-//   1. `peaks codegraph init` — after a fresh upstream init (which
-//      always writes upstream's 99-rule default `exclude` template AND
-//      its 32-entry default `include` template), so a brand new clone /
-//      new machine ends up with a complete index instead of silently
-//      dropping tracked source files.
-//   2. `peaks codegraph repair-exclude` (exclude axis, incremental
-//      rebuild) and `peaks codegraph repair-index` (both axes, FORCED
-//      rebuild) — the explicit repair for a workspace that was
-//      initialized before this shipped, or whose config drifted.
+//   1. `peaks codegraph init` — after a fresh upstream init, so a brand new
+//      clone / new machine ends up with an index that does not silently drop
+//      tracked source files.
+//   2. `peaks codegraph repair-exclude` (incremental rebuild) and
+//      `peaks codegraph repair-index` (FORCED rebuild) — the explicit repair
+//      for a workspace whose config drifted.
 //
 // `status` and the doctor check deliberately do NOT live here: they
 // read the integrity inspectors and never write.
 //
-// ── WHY THE INCLUDE AXIS IS PART OF *THIS* REPAIR ─────────────────────
-//
-// Slice-001's RD measured the reason with a real test failure: an
-// `exclude` rule that blocks ONLY a file `include` already drops
-// reconciles COMPLETELY CLEAN today — `include: ['**/*.ts']` with
-// `exclude: ['**/tool.mjs']` reports `gap:false, rulesToRemove:[]` even
-// though that rule is actively harmful. The moment `include` is widened
-// (which is exactly what repairing the include axis does) the rule starts
-// biting, and the exclude reconciliation is the only thing that can see it.
-//
-// So the ORDER IS LOAD-BEARING and is enforced structurally rather than by
-// comment: `repairCodegraphExcludeFromProject` reconciles `exclude` against
-// the NORMALIZED include list, never against the on-disk one. Reconciling
-// first would bless a rule that the same run was about to make harmful —
-// the repair would report success over a config it had just broken.
-//
 // Safety posture (the file being edited belongs to a THIRD-PARTY tool):
 //   - `rulesToRemove` comes from the exclude reconciler, which only ever
 //     lists a rule that actually blocks at least one git-tracked source
-//     file AFTER include normalization. A rule that matches nothing
-//     tracked is never dropped.
-//   - `includePatternsToAdd` comes from the include reconciler, which only
-//     ever appends a bare-extension pattern for an extension upstream's
-//     extractor supports and its own template omits. User entries are
-//     never removed, reordered or rewritten.
-//   - Nothing is written when both lists are empty — the config bytes, and
+//     file. A rule that matches nothing tracked is never dropped, and no
+//     user entry is ever added, removed, reordered or rewritten.
+//   - Nothing is written when the list is empty — the config bytes, and
 //     its mtime, are untouched.
 //   - The original bytes are copied to `config.json.bak` before the
 //     rewrite, so a rollback is byte-exact *whenever that copy is THIS
@@ -76,40 +70,37 @@
 //     write can be redirected into another project's `.codegraph/`
 //     (security R1). Containment is the predicate, not link-ness — see the
 //     function's own note on why an in-project link is allowed.
-//   - Both axes move in ONE rewrite through a same-directory temp file plus
-//     `renameSync`, so the config is never observed half-written, there is
-//     never a moment where `include` is widened but `exclude` still holds
-//     the rules the widened list just made harmful, and one backup covers
-//     both.
+//   - The rewrite is ONE same-directory temp file plus `renameSync`, so the
+//     config is never observed half-written.
 //   - Every other key of the config survives verbatim, in its original
-//     position; only `include` and `exclude` change.
-import { join } from 'node:path';
-import { CODEGRAPH_CONFIG_FILENAME, filterAdmittedTrackedFiles, readCodegraphProjectInputs, reconcileCodegraphExclude } from './codegraph-exclude-reconciler.js';
-import { normalizeCodegraphInclude, upstreamUnnamedIncludeExtensions } from './codegraph-include-reconciler.js';
+//     position; only `exclude` changes.
+import { readCodegraphProjectInputs, reconcileCodegraphExclude } from './codegraph-exclude-reconciler.js';
 import { upstreamSupportsPath } from './codegraph-index-integrity.js';
-import { CODEGRAPH_DIR_NAME, createCodegraphInvocation, executeCodegraphInvocation } from './codegraph-service.js';
-import { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude, repairCodegraphInclude } from './codegraph-config-repair-writer.js';
+import { resolveCodegraphConfigSource } from './codegraph-project-config.js';
+import { createCodegraphInvocation, executeCodegraphInvocation } from './codegraph-service.js';
+import { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude } from './codegraph-config-repair-writer.js';
 // ─────────────────────────────────────────────────────────────────────
 // Public surface, unchanged
 // ─────────────────────────────────────────────────────────────────────
 // Re-exported so every existing `codegraph-exclude-repair.js` import site
 // keeps resolving: the extraction moved the definitions, not the contract.
-export { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude, repairCodegraphInclude };
+export { applyCodegraphConfigRepair, CODEGRAPH_CONFIG_BACKUP_SUFFIX, repairCodegraphExclude };
 function errorMessage(error) {
     return error instanceof Error ? error.message : String(error);
 }
+// The config this seam reads and writes is the one the installed upstream
+// consults, so the path comes from that one resolver rather than being spelled
+// here — see `codegraph-project-config.ts`. Called on failure paths too, which
+// is safe: resolving is a probe, not a read, so it names the file even when
+// opening it is what failed.
 function configPathOf(projectRoot) {
-    return join(projectRoot, CODEGRAPH_DIR_NAME, CODEGRAPH_CONFIG_FILENAME);
+    return resolveCodegraphConfigSource(projectRoot).configPath;
 }
 function emptyRepairReport(warning) {
     return {
         applied: false,
         rulesRemoved: [],
-        includePatternsAdded: [],
         filesRecovered: 0,
-        includeFilesRecovered: 0,
-        includeAdmittedAfter: 0,
-        trackedSourceCount: 0,
         configPath: '',
         backupPath: null,
         reindexed: false,
@@ -118,16 +109,14 @@ function emptyRepairReport(warning) {
     };
 }
 /**
- * Reconcile `projectRoot`'s config against its tracked files — normalize
- * `include`, then drop the `exclude` rules that block tracked source files
- * — and rebuild the index so the recovered files actually land in it.
+ * Reconcile `projectRoot`'s config against its tracked files — drop the
+ * `exclude` rules that block tracked source files — and rebuild the index so
+ * the recovered files actually land in it.
  *
- * ORDER IS LOAD-BEARING. `exclude` is reconciled against the NORMALIZED
- * include list, never the on-disk one: an `exclude` rule that blocks only a
- * file `include` drops reconciles clean today and starts biting the moment
- * `include` is widened, so reconciling before normalizing would let this
- * run report success over a config it had just made worse. See the module
- * header.
+ * The reconciliation runs the config's OWN `include` filter first, exactly as
+ * upstream applies it, so a rule that only blocks files the index would not
+ * ingest anyway is not a violation. See the module header for what this seam
+ * no longer does and why.
  *
  * This is the ONE shared "after upstream init" self-heal: the CLI's
  * fresh `peaks codegraph init`, the pre-dispatch preflight and the
@@ -144,83 +133,28 @@ export async function repairCodegraphExcludeFromProject(projectRoot, runner, opt
     const forcedRebuild = options.reindex === 'force';
     let trackedFiles;
     let config;
-    let includePlan;
     try {
-        // Read once, in the one place that owns the readers. The exclude
-        // reconciler is then fed the NORMALIZED include list below, which is
-        // what makes the ordering guarantee structural: there is no code path
-        // here that reconciles against the on-disk include.
+        // Read once, in the one place that owns the readers. The config this
+        // returns is the one the installed upstream consults, and `exclude` is
+        // reconciled against the on-disk list exactly as upstream would apply it.
         ({ trackedFiles, config } = readCodegraphProjectInputs(projectRoot));
-        // INSIDE the guard on purpose. The adapter loads upstream's own
-        // `types.js` / `extraction/grammars.js` out of the installed package and
-        // throws if the pinned install is damaged or its `dist/` layout moved;
-        // this function's contract is "never throws", and the alternative is
-        // that `repair-exclude` / `repair-index` escape to the CLI's generic
-        // UNHANDLED_ERROR (and `init` prints FAILURE for an init that already
-        // succeeded). A failure here is reported as a warning like every other
-        // one.
-        includePlan = normalizeCodegraphInclude({
-            include: config.include,
-            candidateExtensions: upstreamUnnamedIncludeExtensions()
-        });
     }
     catch (error) {
         return emptyRepairReport(`codegraph exclude reconcile skipped: ${errorMessage(error)}`);
     }
-    // AFTER normalization, never before. `admitted` here is the normalized
-    // admission set, so a rule that the widening would make harmful is
-    // visible to this reconciliation in the SAME run that widens.
     const reconcile = reconcileCodegraphExclude({
         trackedFiles,
-        include: includePlan.include,
-        exclude: config.exclude
+        include: config.include,
+        exclude: config.exclude,
+        admissionModel: config.model,
+        // Same oracle as the index axis — see `excludeCandidates`.
+        supportsPath: upstreamSupportsPath
     });
-    // The numerator is the normalized admission count, which the reconciliation
-    // just computed — it is not re-filtered here.
-    const includeAdmittedAfter = reconcile.trackedSourceCount;
-    // The denominator is a DIFFERENT measurement over the same file list: an
-    // extension decision per tracked file (`upstreamSupportsPath`, the same
-    // oracle the index axis uses), not a glob match. Two independent
-    // measurements can disagree, which is the whole point — a ratio whose
-    // numerator and denominator are the same expression cannot report the
-    // shortfall it exists to report. It is also cheap: no glob is compiled.
-    //
-    // This replaced a full `filterAdmittedTrackedFiles(trackedFiles,
-    // config.include)` pass whose only consumer was the on-disk "was N"
-    // trailer of a user-facing sentence. Perf measured that second pass at
-    // 11.73 ms of the repair entry's +14.13 ms (83 %), on ALL THREE automatic
-    // seams and both repair commands, including no-ops; the trailer was not
-    // worth it. Measured again here on this repo (2,104 tracked files x 32
-    // include rules, paired runs): the removed pass 9.78 ms median, this
-    // extension check 0.18 ms — and it reports the same 1,240 the status line
-    // reports as the denominator, which is the point of using one oracle.
-    const trackedSourceCount = trackedFiles.filter((file) => upstreamSupportsPath(file)).length;
-    // A1 (2026-09-17): the include axis' own file count, measured as a DELTA
-    // against the ON-DISK include list — `includeAdmittedAfter` is the count
-    // for the NORMALIZED list, so the difference is exactly the tracked files
-    // this run's appends newly admit. Never negative: `includePlan.include` is
-    // a superset of `config.include` and admission is monotone in the rule
-    // list, so the before-count cannot exceed the after-count.
-    //
-    // GATED on `includePlan.changed`, which is exact rather than an
-    // optimization: when nothing was appended the normalized list IS the
-    // on-disk list, so the delta is 0 without measuring anything. The pass
-    // this gate keeps off the hot path is the one slice-002 deleted for cost
-    // (see the `trackedSourceCount` note above) — the difference is that THIS
-    // pass runs only on the one run per project that actually widens
-    // `include`, where a repair is about to spend seconds rebuilding an index.
-    const includeFilesRecovered = includePlan.changed
-        ? includeAdmittedAfter - filterAdmittedTrackedFiles(trackedFiles, config.include).length
-        : 0;
-    const nothingToRepair = includePlan.addedPatterns.length === 0 && reconcile.rulesToRemove.length === 0;
+    const nothingToRepair = reconcile.rulesToRemove.length === 0;
     const unchanged = {
         applied: false,
         rulesRemoved: [],
-        includePatternsAdded: [],
         filesRecovered: 0,
-        includeFilesRecovered: 0,
-        includeAdmittedAfter,
-        trackedSourceCount,
         configPath: configPathOf(projectRoot),
         backupPath: null,
         reindexed: false,
@@ -244,8 +178,7 @@ export async function repairCodegraphExcludeFromProject(projectRoot, runner, opt
     if (!nothingToRepair) {
         try {
             outcome = applyCodegraphConfigRepair(projectRoot, {
-                rulesToRemove: reconcile.rulesToRemove,
-                includePatternsToAdd: includePlan.addedPatterns
+                rulesToRemove: reconcile.rulesToRemove
             });
         }
         catch (error) {
@@ -261,11 +194,7 @@ export async function repairCodegraphExcludeFromProject(projectRoot, runner, opt
     const base = {
         applied: outcome !== null,
         rulesRemoved: outcome?.removedRules ?? [],
-        includePatternsAdded: outcome?.addedIncludePatterns ?? [],
         filesRecovered: reconcile.excludedTrackedCount,
-        includeFilesRecovered,
-        includeAdmittedAfter,
-        trackedSourceCount,
         configPath: configPathOf(projectRoot),
         backupPath: outcome?.backupPath ?? null
     };
@@ -313,13 +242,12 @@ export async function repairCodegraphExcludeFromProject(projectRoot, runner, opt
         };
     }
 }
-// "2 exclude rule(s) removed, 5 include pattern(s) added" — the trailing
-// half of every degraded-path warning above. Written once so the four
-// warnings cannot drift from each other, and it names BOTH axes because
-// either may be the one that changed.
+// "2 exclude rule(s) removed" — the trailing half of every degraded-path
+// warning above. Written once so the four warnings cannot drift from each
+// other.
 function describeRepair(outcome) {
     if (outcome === null || !outcome.applied) {
         return 'nothing written';
     }
-    return `${outcome.removedRules.length} exclude rule(s) removed, ${outcome.addedIncludePatterns.length} include pattern(s) added`;
+    return `${outcome.removedRules.length} exclude rule(s) removed`;
 }

package/dist/services/codegraph/codegraph-foreign-removal.d.ts

@@ -0,0 +1,21 @@
+import { type CodegraphInitGuardResult } from './codegraph-service.js';
+/** Reported by the CLI as `CODEGRAPH_FOREIGN_REMOVAL_REFUSED`. */
+export declare class ForeignCodegraphRemovalError extends Error {
+    constructor(message: string);
+}
+/**
+ * Remove `<projectRoot>/.codegraph` and return the path that was deleted.
+ * Throws `ForeignCodegraphRemovalError` for a link or for a
+ * peaks-loop-managed directory.
+ */
+export declare function removeForeignCodegraphDir(projectRoot: string): string;
+/**
+ * Remove the foreign directory and re-run the init guard, so the caller sees an
+ * ordinary fresh init. Kept next to the removal because the two are one
+ * decision: what `--force` means is "replace it, then continue as if it had
+ * never been foreign".
+ */
+export declare function forcePastForeignConflict(projectRoot: string): {
+    removed: string;
+    outcome: CodegraphInitGuardResult;
+};