agent-doc-system 1.2.0 → 1.4.0

package/CHANGELOG.md

@@ -9,6 +9,183 @@ refused by the next with `AGENTDOC_COMPILER_MISMATCH` until it is recompiled.
 
 ## [Unreleased]
 
+## [1.4.0] - 2026-11-10
+
+`impact` now treats a change under a Drizzle migration directory as a change
+to the database it migrates. It reaches every component bound to that
+database, not only the component that holds the file. Any other ORM layout can
+be declared on the database Resource with the new `spec.migrationPaths`.
+Existing `migrations/` and `alembic/versions/` paths give the same answer as
+before.
+
+Before you upgrade:
+
+- **Recompile committed graphs.** As with every release, a graph compiled by
+  1.3.0 is refused with `AGENTDOC_COMPILER_MISMATCH` until you run
+  `agentdoc compile` again. Graphs of repositories that enable the `database`
+  adapter also gain `derived.migrationDirs` and the provenance behind it.
+- **A Drizzle config whose `out` is not a plain string** (an environment
+  variable, an expression, a spread) now raises the warning
+  `AGENTDOC_MIGRATION_DIR_UNRESOLVED`. Declare the directory with
+  `spec.migrationPaths`, or accept the warning ([#63]).
+
+### Added
+
+- A `logical-database` Resource can declare where its schema migrations live,
+  with `spec.migrationPaths` ([#63]). A change under a declared directory is a
+  change to that Resource, whichever component owns the file, so `impact`
+  reaches every component bound to the database. Paths are whole-segment
+  prefixes, not globs: `frontend/apps/web/drizzle` covers `0036_x.sql` and
+  `meta/_journal.json`, and never `drizzle-extra/`. A glob, a declaration on
+  another Resource type, or one path declared by two Resources fails with the
+  new `AGENTDOC_MIGRATION_PATH`; a path outside the repository fails with
+  `AGENTDOC_PATH_ESCAPE`, a missing one with `AGENTDOC_PATH_UNRESOLVED`. The
+  declaration never creates a binding.
+
+### Fixed
+
+- `impact` now classifies a change under a Drizzle migration directory as a
+  database change ([#63]). Only `migrations/`, `migration/` and
+  `alembic/versions/` used to count, so `impact
+  frontend/apps/web/drizzle/0036_email_locale.sql` reported the web component
+  alone and missed every other component bound to the same database. The
+  `database` adapter now reads Drizzle Kit's `out` from `drizzle.config.ts`
+  (`.js`, `.mjs`) as a string literal, without running it, and defaults to
+  `./drizzle`. An `out` it cannot read statically is reported with the
+  acceptable warning `AGENTDOC_MIGRATION_DIR_UNRESOLVED` instead of being
+  guessed. Detected directories, including `migrations` and `alembic/versions`,
+  are recorded in the graph as `derived.migrationDirs` with provenance, and
+  `impact` classifies from them. A detected directory still reaches a database
+  only through the component's existing bindings. The answer for an existing
+  `migrations/` or `alembic/versions/` path is unchanged. Committed graphs of
+  repositories that enable the `database` adapter gain `migrationDirs` and
+  must be recompiled.
+
+## [1.3.0] - 2026-11-07
+
+A graph compiled on your machine now passes `check` in CI and in a clean
+checkout. Files git ignores no longer count as compiler inputs, so a local
+build that fills an ignored directory no longer changes `inputHash`. A
+component whose descriptor sits at the repository root now owns the root files
+no other component owns, so `query` and `impact` route them. `init` and
+`scaffold --write` no longer write into your product's `docs/`: they follow the
+configured `docs.*` paths, and a new install without a configuration gets its
+skeleton under `agentdoc/docs/`. Releases are now published from CI with npm
+provenance, so `npm audit signatures` can verify that a release was built from
+this repository. The benchmark claim made in the 1.2.0 release notes is
+withdrawn, because its gap came from the evaluation and not from routing.
+
+Before you upgrade:
+
+- **Recompile committed graphs.** As with every release, a graph compiled by
+  1.2.0 is refused with `AGENTDOC_COMPILER_MISMATCH` until you run
+  `agentdoc compile` again.
+- **A descriptor or configuration path that points at a git-ignored file now
+  fails** with `AGENTDOC_PATH_UNRESOLVED`, as it would in a clean checkout.
+  Commit the file or stop ignoring it ([#45]).
+- **New installs write the documentation skeleton to `agentdoc/docs/`**
+  instead of `docs/`. A configuration that declares `docs.*` keeps its paths,
+  and no existing file is moved ([#59]).
+
+### Added
+
+- A deterministic `baseline-search` routing evaluation using working-tree file
+  reads and text search, without compiled relations ([#46]). CLI reports compare
+  catalog, corrected targeted and search recall/noise/check selectivity per
+  scenario, corpus and aggregate; `docs/EVALS.md` documents every heuristic.
+
+### Changed
+
+- Releases are now published only through a manual GitHub Actions workflow,
+  using npm trusted publishing (no token) with provenance, so `npm audit
+  signatures` can verify that a release was built from this repository
+  ([#51]). `RELEASING.md` in the repository describes the process.
+
+- **Behaviour change for new installs only:** without a configuration,
+  `agentdoc init` (and `scaffold --write`) now writes the documentation
+  skeleton to `agentdoc/docs/PRODUCT.md`, `agentdoc/docs/ARCHITECTURE.md`,
+  `agentdoc/docs/CONSTRAINTS.md` and `agentdoc/docs/adr/`, and records those
+  paths in the `docs:` block of the generated `agentdoc/agentdoc.config.yaml`
+  ([#59]). It used to write to `docs/`, which in many repositories is the
+  product's own user documentation and the source of a published docs site
+  (MkDocs, Docusaurus, GitHub Pages). Authored AgentDoc material now lives in
+  `agentdoc/`; generated output stays in `.agentdoc/`. Existing configurations
+  are unaffected: a configuration that declares `docs.*` keeps its paths,
+  `docs/...` included, and no existing file is moved. To keep `docs/` on a new
+  install, declare `docs.product`, `docs.architecture`, `docs.constraints` and
+  `docs.adrDir` in `agentdoc/agentdoc.config.yaml` before running `init`.
+
+### Fixed
+
+- A component whose descriptor sits at the repository root now owns the files
+  no nested component owns ([#50]). Before, `query vite.config.ts` failed with
+  `AGENTDOC_REF_UNRESOLVED` and `impact` listed the file in `unmatchedFiles`,
+  for both `vite.config.ts` and `./vite.config.ts`. Paths are now compared in
+  one canonical repository-relative form (no `./`), by whole path segment
+  (`src` never owns `src2/x`), and the longest owning root wins, so nested
+  components keep precedence and a contract file still routes to its API. A
+  root unit's derived paths (`README.md`, `package.json`, markers, provenance,
+  verification config paths) are no longer recorded as `./README.md`, so
+  `impact` now recognises them as documentation and compiler inputs. Without a
+  root descriptor, root files stay unmatched. Graphs of repositories without a
+  root component are unchanged.
+
+- `agentdoc scaffold --write` and `agentdoc init` now write the documentation
+  skeleton (`PRODUCT.md`, `ARCHITECTURE.md`, `CONSTRAINTS.md`, the ADR README)
+  to the configured `docs.product`, `docs.architecture`, `docs.constraints` and
+  `docs.adrDir` paths ([#49]). Both used to write to `docs/` even when the
+  configuration said otherwise, and `docs/` is often the product's own user
+  documentation. The paths are read through the same loader as `compile` and
+  `audit`. A role the configuration omits is listed under `notConfigured`
+  instead of falling back to `docs/`. An existing file is still skipped unless
+  `init --force` is given. A path that leaves the repository, including through
+  a symlink, fails with `AGENTDOC_PATH_ESCAPE` before anything is written.
+  Without a configuration, `init` uses the `agentdoc/docs/` defaults (see
+  [#59] under Changed).
+
+- Files git ignores no longer enter the compiler's inputs or `inputHash`
+  ([#45]). A local build writing into an ignored directory (`astro build`
+  filling `.astro/`, a `build/` tree, `*.log`) used to change the hash, so a
+  graph compiled after it failed `check` with `AGENTDOC_GRAPH_FRESHNESS` in CI
+  and in every clean checkout, while passing on the author's machine. Reads,
+  existence probes, listings and discovery now exclude git-ignored paths, with
+  git itself as the oracle: tracked files always count, and nested
+  `.gitignore`, `.git/info/exclude`, `core.excludesFile` and negations behave
+  exactly as in git. A non-ignored untracked file is still an input. Without
+  git the previous behaviour (filesystem minus `discovery.generatedDirs`)
+  holds. Committed graphs keep their hash. A descriptor or configuration
+  that points at a git-ignored file (for example a spec generated into an
+  ignored directory before `compile`) now fails with
+  `AGENTDOC_PATH_UNRESOLVED`, as it would in a clean checkout: commit the file
+  or stop ignoring it. The `git clean -fdX` before
+  `compile` documented as a workaround in lbframe/klozeo's `AGENTS.md` is no
+  longer needed.
+
+- `npm publish` no longer auto-corrects `package.json`: the `bin` path is
+  committed in npm's normalized form, `bin/agentdoc.mjs` ([#55]).
+
+- All routing evaluation systems and the noise closure now share fact labels
+  ([#46]). Corrected targeted micro-recall is 100/101 (0.9901), rather than
+  the previously reported gap. Search matches catalog recall in 21/30 scenarios;
+  measurements and limitations are in `docs/BENCHMARK.md`. Normalized full fact
+  counts fall below the existing size floor, so aggregate size reduction is
+  reported as unmeasured. Thresholds, scenarios and core routing are unchanged.
+
+- **Withdrawn benchmark claim.** The README, `docs/BENCHMARK.md` and the 1.2.0
+  release notes reported that routing retrieves 100% of the facts a change
+  needs against 58% for a baseline that reads only the touched component, with
+  noise under 9% against 40%, and an answer about 70% smaller than the whole
+  catalog. The gap came from the evaluation, not from
+  routing: the baseline already held almost every expected fact under a
+  different label, and it read relations from the compiled graph that an agent
+  without AgentDoc does not have. The size figure counted the same component
+  once per relation label; deduplicated, every corpus falls below the size
+  floor. Both claims are
+  removed. A baseline that finds
+  relations with search alone is now measured in the benchmark. The
+  [correction](docs/BENCHMARK.md#correction-the-fact-recall-comparison-is-withdrawn)
+  gives the details.
+
 ## [1.2.0] - 2026-10-27
 
 Rust and Python are now supported at the same level as Node and Go. Before
@@ -242,7 +419,9 @@ First public release.
   for project health.
 - An Agent Skill under `skills/agent-doc-system/`.
 
-[Unreleased]: https://github.com/lbframe/agent-doc-system/compare/v1.2.0...HEAD
+[Unreleased]: https://github.com/lbframe/agent-doc-system/compare/v1.4.0...HEAD
+[1.4.0]: https://github.com/lbframe/agent-doc-system/compare/v1.3.0...v1.4.0
+[1.3.0]: https://github.com/lbframe/agent-doc-system/compare/v1.2.0...v1.3.0
 [1.2.0]: https://github.com/lbframe/agent-doc-system/compare/v1.1.0...v1.2.0
 [1.1.0]: https://github.com/lbframe/agent-doc-system/compare/v1.0.0...v1.1.0
 [1.0.0]: https://github.com/lbframe/agent-doc-system/releases/tag/v1.0.0
@@ -267,3 +446,11 @@ First public release.
 [#40]: https://github.com/lbframe/agent-doc-system/issues/40
 [#41]: https://github.com/lbframe/agent-doc-system/issues/41
 [#43]: https://github.com/lbframe/agent-doc-system/issues/43
+[#45]: https://github.com/lbframe/agent-doc-system/issues/45
+[#46]: https://github.com/lbframe/agent-doc-system/issues/46
+[#49]: https://github.com/lbframe/agent-doc-system/issues/49
+[#50]: https://github.com/lbframe/agent-doc-system/issues/50
+[#51]: https://github.com/lbframe/agent-doc-system/issues/51
+[#55]: https://github.com/lbframe/agent-doc-system/issues/55
+[#59]: https://github.com/lbframe/agent-doc-system/issues/59
+[#63]: https://github.com/lbframe/agent-doc-system/issues/63

package/README.md

@@ -98,7 +98,7 @@ What every adapter derives, and what it deliberately cannot see, is in [docs/ADA
 
 Measured, reproducible, and with no model in the loop. Method and caveats are in [docs/BENCHMARK.md](docs/BENCHMARK.md).
 
-- **The right context: 100% vs. 58%.** Across 30 routing scenarios (Node, Go, Rust, Python), `query` + `impact` retrieves every fact the change needs. Reading only the touched component retrieves 58%. Noise stays under 9%, against 40%. Every check the change requires is in the answer, and that answer holds about half of the repository's checks (29% on the largest corpus), not all of them. The thresholds were fixed before the first run and have not moved since.
+- **The checks a change needs, not the whole suite.** Across 30 routing scenarios (Node, Go, Rust, Python), every check the change requires is in the answer, and that answer holds about half of the repository's checks (29% on the largest corpus), not all of them. The thresholds were fixed before the first run and have not moved since.
 - **Seconds to map a real repository.** A fresh `init` → `scaffold` → `compile` takes 1.0–4.6 s on four public repositories, from 141 to 5,142 files (axum, pydantic-ai, full-stack-fastapi-template, create-t3-turbo). No edit was needed beyond choosing each component's placement.
 - **A briefing, not a dump.** A `query` answer is about 100–260 tokens: what the change reaches, what to read, and which checks to run.
 - **The same graph every time.** Compiles are byte-identical, and CI can verify it.

package/adapters/cache.mjs

@@ -1,5 +1,6 @@
 // Cache adapter: Redis / in-memory cache client evidence as a derived binding.
 import { Adapter } from "./registry.mjs";
+import { joinPath } from "../core/paths.mjs";
 
 const CACHE_HINT = /(@upstash\/redis|ioredis|redis\.Redis|redis|go-redis|redis\.go|valkey|memcache|@memcached)/i;
 
@@ -11,12 +12,12 @@ export class CacheAdapter extends Adapter {
   extract(ctx, unit) {
     const { repo, prov, compRef } = ctx;
     const evFile = unit.goModule
-      ? unit.root + "/go.mod"
+      ? joinPath(unit.root, "go.mod")
       : unit.pythonManifest
         ? unit.pythonManifest
-        : repo.exists(unit.root + "/package.json")
-          ? unit.root + "/package.json"
-          : unit.root + "/Cargo.toml";
+        : repo.exists(joinPath(unit.root, "package.json"))
+          ? joinPath(unit.root, "package.json")
+          : joinPath(unit.root, "Cargo.toml");
     if (!repo.exists(evFile)) return {};
     const text = repo.readText(evFile);
     if (!CACHE_HINT.test(text)) return {};

package/adapters/database.mjs

@@ -9,6 +9,7 @@
 //     library shipped migrations but explicitly did not own a database.
 import { Adapter } from "./registry.mjs";
 import { firstExistingFile, findMigrationDirs } from "../core/sourcescan.mjs";
+import { canonicalPath, joinPath } from "../core/paths.mjs";
 
 const ORM_CONFIG = [
   "drizzle.config.ts", "drizzle.config.js", "drizzle.config.mjs",
@@ -37,8 +38,8 @@ export class DatabaseAdapter extends Adapter {
     }
     const alembicDir = migrationDirs.find((d) => d === "alembic/versions" || d.endsWith("/alembic/versions"));
     if (alembicDir) {
-      const ini = root + "/alembic.ini";
-      const pyproject = root + "/pyproject.toml";
+      const ini = joinPath(root, "alembic.ini");
+      const pyproject = joinPath(root, "pyproject.toml");
       if (repo.exists(ini)) {
         const text = repo.readText(ini);
         if (/^\s*\[alembic\]/m.test(text) || /^\s*script_location\s*=/m.test(text)) evidencePath = ini;
@@ -47,6 +48,12 @@ export class DatabaseAdapter extends Adapter {
       }
     }
     const pr = prov.add("observed", evidencePath, "migration-extractor", ["der:" + compRef + ":/bindings"]);
+    // Where this unit's migrations live, recorded in the graph so `impact`
+    // classifies a change from the graph rather than from a list of names.
+    // Authority over a directory, never ownership of a database: these records
+    // create no binding.
+    const recorded = recordMigrationDirs(ctx, unit, migrationDirs, ormConfig, pr);
+    const withDirs = (out) => (recorded.length ? { ...out, migrationDirs: recorded } : out);
 
     // A component that both migrates and opens a connection owns the database.
     const opensConnection = hasConnectionEvidence(ctx, unit);
@@ -65,7 +72,7 @@ export class DatabaseAdapter extends Adapter {
         evidenceClass: "DERIVED", confidence: "candidate", provRecs: [pr],
         semantics: "a schema exists here, but which component owns the logical database is unresolved",
       });
-      return { migrationAuthority: evidencePath };
+      return withDirs({ migrationAuthority: evidencePath });
     }
 
     const name = compRef.split("/")[1];
@@ -88,7 +95,7 @@ export class DatabaseAdapter extends Adapter {
         evidenceClass: "DERIVED", confidence: "candidate", provRecs: [pr],
         semantics: "this component opens a database connection, but no authored Resource claims ownership",
       });
-      return { migrationAuthority: evidencePath };
+      return withDirs({ migrationAuthority: evidencePath });
     }
     ctx.addFact(compRef, "resource.ownership", target.name, {
       evidenceClass: "DERIVED", confidence: "deterministic", provRecs: [pr],
@@ -100,10 +107,10 @@ export class DatabaseAdapter extends Adapter {
     const client = ctx.clientKeyForResourceType("logical-database");
     const attrs = client ? { via: "migrations+connection", client } : { via: "migrations+connection" };
     ctx.addEdge("usesResource", compRef, target.ref, attrs, [pr], "DERIVED");
-    return {
+    return withDirs({
       migrationAuthority: evidencePath,
       bindings: [{ kind: "database", logicalResourceRef: target.ref, resolution: "resolved", provenanceIds: null, _provs: new Set([pr]) }],
-    };
+    });
   }
 }
 
@@ -128,3 +135,145 @@ function findDatabaseResource(ctx, name) {
   );
   return cands.length === 1 ? cands[0] : null;
 }
+
+// ── migration directories ───────────────────────────────────────────────────
+//
+// Two routes, each with its own evidence:
+//   - a directory named by convention (`migrations`, `migration`,
+//     `alembic/versions`), evidenced by a file inside it;
+//   - Drizzle Kit's `out`, evidenced by the config file that states it.
+// Prisma Migrate writes to `prisma/migrations`, which the first route covers.
+function recordMigrationDirs(ctx, unit, conventionDirs, ormConfig, pr) {
+  const { repo, prov, compRef } = ctx;
+  const subject = "der:" + compRef + ":/migrationDirs";
+  const byPath = new Map();
+  const add = (dir, via, rec) => {
+    if (!byPath.has(dir)) byPath.set(dir, { path: dir, via: new Set(), _provs: new Set() });
+    byPath.get(dir).via.add(via);
+    byPath.get(dir)._provs.add(rec);
+  };
+  for (const dir of conventionDirs) {
+    // A directory with no file in the input set has nothing a change could
+    // touch, and nothing to cite as evidence.
+    const file = repo.walkUnit(unit.root, dir)[0];
+    if (!file) continue;
+    let rec;
+    if (file === pr.path) {
+      rec = pr;
+      pr.subjects.add(subject);
+    } else {
+      rec = prov.add("observed", file, "migration-extractor", [subject]);
+    }
+    add(dir, /(^|\/)alembic\/versions$/.test(dir) ? "alembic-versions" : "directory-name", rec);
+  }
+  if (ormConfig && /(^|\/)drizzle\.config\.[cm]?[jt]s$/.test(ormConfig)) {
+    const dir = drizzleOutDir(ctx, unit, ormConfig);
+    if (dir) add(dir, "drizzle-config", prov.add("observed", ormConfig, "drizzle-config-extractor", [subject]));
+  }
+  return [...byPath.values()]
+    .sort((a, b) => (a.path < b.path ? -1 : 1))
+    .map((d) => ({ path: d.path, via: [...d.via].sort(), provenanceIds: null, _provs: d._provs }));
+}
+
+// Drizzle Kit writes migrations to `out`, `./drizzle` when absent. The config
+// is code, and it is never executed: only a string literal is read. Anything
+// else — an expression, an environment variable, a spread that could carry
+// `out`, several `out` keys — is reported and not guessed, because a wrong
+// directory would route migrations to the wrong database silently.
+function drizzleOutDir(ctx, unit, configPath) {
+  const { repo, compRef } = ctx;
+  const unresolved = (why) => {
+    ctx.diagnostics.push({
+      severity: "warning",
+      code: "AGENTDOC_MIGRATION_DIR_UNRESOLVED",
+      subject: compRef,
+      refs: [compRef],
+      message:
+        "Drizzle migration directory in '" + configPath + "' is not recorded: " + why + ". " +
+        "Declare it with spec.migrationPaths on the logical-database Resource it migrates",
+      paths: [configPath],
+    });
+    return null;
+  };
+  const parsed = drizzleOut(repo.readText(configPath));
+  if (parsed.error) return unresolved(parsed.error);
+  const value = parsed.value ?? "./drizzle";
+  // Relative to the directory drizzle-kit runs from, which is the config's own
+  // directory in the documented layout (and the unit root here).
+  const base = configPath.includes("/") ? configPath.slice(0, configPath.lastIndexOf("/")) : ".";
+  const dir = value.startsWith("/") ? null : canonicalPath(joinPath(base, value));
+  if (!dir || dir === "." || dir === canonicalPath(unit.root)) {
+    return unresolved("out " + JSON.stringify(value) + " is not a directory inside the unit at '" + unit.root + "'");
+  }
+  if (!repo.ownsUnitPath(unit.root, dir)) {
+    return unresolved("out " + JSON.stringify(value) + " is outside the unit at '" + unit.root + "'");
+  }
+  // Not generated yet: nothing to classify. The probe is an input, so the
+  // first generated migration invalidates the graph.
+  if (!repo.isDir(dir)) return null;
+  return dir;
+}
+
+// Static read of `out` from a Drizzle config. Comments are removed and string
+// literals set aside first, so neither `// out: "x"` nor a string containing
+// "out:" is mistaken for the key.
+export function drizzleOut(text) {
+  const strings = [];
+  let code = "";
+  for (let i = 0; i < text.length; ) {
+    const c = text[i];
+    if (c === "/" && text[i + 1] === "/") {
+      while (i < text.length && text[i] !== "\n") i++;
+      continue;
+    }
+    if (c === "/" && text[i + 1] === "*") {
+      const end = text.indexOf("*/", i + 2);
+      i = end < 0 ? text.length : end + 2;
+      code += " ";
+      continue;
+    }
+    if (c === '"' || c === "'" || c === "`") {
+      let j = i + 1;
+      let value = "";
+      let closed = false;
+      while (j < text.length) {
+        if (text[j] === "\\") {
+          value += text[j + 1] ?? "";
+          j += 2;
+          continue;
+        }
+        if (text[j] === c) { closed = true; break; }
+        if (c !== "`" && text[j] === "\n") break;
+        value += text[j];
+        j++;
+      }
+      if (!closed) return { error: "the config could not be read statically" };
+      // A template with a substitution is an expression, not a literal.
+      strings.push(c === "`" && value.includes("${") ? null : value);
+      code += "\u0000" + (strings.length - 1) + "\u0000";
+      i = j + 1;
+      continue;
+    }
+    code += c;
+    i++;
+  }
+  const hits = [];
+  for (const m of code.matchAll(/(?:^|[{,\s])(?:out|\u0000(\d+)\u0000)\s*(:|[,}])/g)) {
+    // A quoted key counts only when it says "out".
+    if (m[1] !== undefined && strings[Number(m[1])] !== "out") continue;
+    hits.push(m);
+  }
+  if (hits.length === 0) {
+    // A spread could bring `out` in from elsewhere; the default is then a guess.
+    if (/\.\.\.\s*[A-Za-z_$(]/.test(code)) return { error: "the config spreads another object that may set out" };
+    return { value: null };
+  }
+  if (hits.length > 1) return { error: "out is set more than once" };
+  const m = hits[0];
+  if (m[2] !== ":") return { error: "out is a shorthand property, not a string literal" };
+  const rest = code.slice(m.index + m[0].length);
+  const lit = /^\s*\u0000(\d+)\u0000\s*(?:[,}]|$)/.exec(rest);
+  const value = lit ? strings[Number(lit[1])] : null;
+  if (typeof value !== "string" || value.trim() === "") return { error: "out is not a string literal" };
+  return { value };
+}

package/adapters/deploy-config.mjs

@@ -2,6 +2,7 @@
 // Only the file's existence is treated as evidence; no value from these files
 // is ever reported as deployed state.
 import { Adapter } from "./registry.mjs";
+import { joinPath } from "../core/paths.mjs";
 
 const DEPLOY_FILES = [
   "fly.toml", "app.yaml", "render.yaml", "railway.json", "vercel.json",
@@ -16,7 +17,7 @@ export class DeployConfigAdapter extends Adapter {
   }
   detect(ctx, root) {
     for (const n of DEPLOY_FILES) {
-      if (ctx.repo.exists(root + "/" + n)) return { path: root + "/" + n, shape: "deployable" };
+      if (ctx.repo.exists(joinPath(root, n))) return { path: joinPath(root, n), shape: "deployable" };
     }
     return null;
   }
@@ -24,7 +25,7 @@ export class DeployConfigAdapter extends Adapter {
     const { repo, prov, compRef } = ctx;
     const out = { deployConfigs: [] };
     for (const n of DEPLOY_FILES) {
-      const p = unit.root + "/" + n;
+      const p = joinPath(unit.root, n);
       if (!repo.exists(p)) continue;
       prov.add("observed", p, "deploy-extractor", ["der:" + compRef + ":/artifact"]);
       out.deployConfigs.push(p);

package/adapters/dockerfile.mjs

@@ -1,5 +1,6 @@
 // Dockerfile adapter: a Dockerfile is deployable-artifact evidence.
 import { Adapter } from "./registry.mjs";
+import { joinPath } from "../core/paths.mjs";
 
 export class DockerfileAdapter extends Adapter {
   static adapterName = "dockerfile";
@@ -8,7 +9,7 @@ export class DockerfileAdapter extends Adapter {
   }
   detect(ctx, root) {
     for (const n of ["Dockerfile", "Dockerfile.prod", "Containerfile"]) {
-      if (ctx.repo.exists(root + "/" + n)) return { path: root + "/" + n, shape: "deployable" };
+      if (ctx.repo.exists(joinPath(root, n))) return { path: joinPath(root, n), shape: "deployable" };
     }
     return null;
   }
@@ -16,7 +17,7 @@ export class DockerfileAdapter extends Adapter {
     const { repo, prov, compRef } = ctx;
     const out = { dockerfiles: [] };
     for (const n of ["Dockerfile", "Dockerfile.prod", "Containerfile"]) {
-      const p = unit.root + "/" + n;
+      const p = joinPath(unit.root, n);
       if (!repo.exists(p)) continue;
       prov.add("observed", p, "deploy-extractor", ["der:" + compRef + ":/artifact"]);
       out.dockerfiles.push(p);

package/adapters/generic.mjs

@@ -7,6 +7,7 @@
 import { Adapter } from "./registry.mjs";
 import { resolveClientResources } from "./resource-client.mjs";
 import { sourceFiles } from "../core/sourcescan.mjs";
+import { joinPath } from "../core/paths.mjs";
 
 // Conservative: a health route is an absolute string literal that looks like a
 // liveness or readiness endpoint. Anything more specific belongs to a
@@ -50,7 +51,7 @@ export class GenericAdapter extends Adapter {
     // Provenance must name a file that exists. The dependency evidence is the
     // manifest when there is one, and otherwise the unit's descriptor.
     const manifest = ["package.json", "go.mod", "Cargo.toml", "pyproject.toml", "pom.xml"]
-      .map((n) => unit.root + "/" + n)
+      .map((n) => joinPath(unit.root, n))
       .find((p) => repo.exists(p)) || ctx.componentEntity().file;
     const clientProv = prov.add("observed", manifest, "client-resolver", ["rel:pending", "der:" + compRef + ":/bindings"]);
     resolveClientResources(ctx, unit, compRef, clientProv);

package/adapters/github-actions.mjs

@@ -4,6 +4,7 @@
 import path from "node:path";
 import { Adapter } from "./registry.mjs";
 import { parseYamlDocuments } from "../core/yaml.mjs";
+import { ownsPath } from "../core/paths.mjs";
 
 export class GitHubActionsAdapter extends Adapter {
   static adapterName = "github-actions";
@@ -224,7 +225,7 @@ function literalPath(value) {
   const p = path.posix.normalize(value);
   return p === ".." || p.startsWith("../") ? null : p.replace(/\/$/, "");
 }
-function within(p, root) { return root === "." || p === root || p.startsWith(root + "/"); }
+function within(p, root) { return ownsPath(root, p); }
 function shellQuote(p) { return /^[A-Za-z0-9_./-]+$/.test(p) ? p : "'" + p.replace(/'/g, "'\\''") + "'"; }
 
 function scopedTo(unit, args, cwd, filters, units, repo) {

package/adapters/go.mjs

@@ -1,6 +1,7 @@
 // Go adapter: go.mod / go.work as unit markers, module graph as build
 // relations, and the go toolchain's own verification commands.
 import { Adapter } from "./registry.mjs";
+import { joinPath } from "../core/paths.mjs";
 
 export class GoAdapter extends Adapter {
   static adapterName = "go";
@@ -26,13 +27,13 @@ export class GoAdapter extends Adapter {
     return out;
   }
   detect(ctx, root) {
-    const p = root + "/go.mod";
+    const p = joinPath(root, "go.mod");
     if (!ctx.repo.exists(p)) return null;
-    return { path: p, shape: ctx.repo.isDir(root + "/cmd") ? "deployable" : "importable" };
+    return { path: p, shape: ctx.repo.isDir(joinPath(root, "cmd")) ? "deployable" : "importable" };
   }
   extract(ctx, unit) {
     const { repo, prov, compRef } = ctx;
-    const p = unit.root + "/go.mod";
+    const p = joinPath(unit.root, "go.mod");
     if (!repo.exists(p)) return {};
     const derived = { languages: new Set(["go"]), runtimes: new Set(["go"]) };
     const text = repo.readText(p);

package/adapters/node.mjs

@@ -1,5 +1,6 @@
 // Node adapter: package.json as the unit marker and manifest authority.
 import { Adapter } from "./registry.mjs";
+import { joinPath } from "../core/paths.mjs";
 
 // A script name maps to a verification tier. Deliberately conservative and
 // project-neutral: a script that does not look like a check is not a check.
@@ -20,7 +21,7 @@ export class NodeAdapter extends Adapter {
     super({ name: "node", version: "1.0.0", kind: "unit-marker" });
   }
   detect(ctx, root) {
-    const p = root + "/package.json";
+    const p = joinPath(root, "package.json");
     if (!ctx.repo.exists(p)) return null;
     let pkg;
     try {
@@ -34,7 +35,7 @@ export class NodeAdapter extends Adapter {
   extract(ctx, unit) {
     const { repo, prov, compRef } = ctx;
     const root = unit.root;
-    const manifestPath = root + "/package.json";
+    const manifestPath = joinPath(root, "package.json");
     if (!repo.exists(manifestPath)) return {};
     const derived = { languages: new Set(["javascript"]), runtimes: new Set(["node"]) };
     const pkg = unit.pkg || repo.readJson(manifestPath);

package/adapters/rust.mjs

@@ -225,6 +225,9 @@ function childDirectoryNames(repo, dir) {
     if (ent.isSymbolicLink() || !ent.isDirectory()) continue;
     if (!ent.name || ent.name.startsWith(".")) continue;
     if (generated.has(ent.name) || WORKSPACE_SKIP_DIRS.has(ent.name)) continue;
+    // Each child is probed for Cargo.toml, and a probe is an input: a
+    // git-ignored directory must not even be visited (issue #45).
+    if (repo.isIgnored && repo.isIgnored(dir ? dir + "/" + ent.name : ent.name)) continue;
     names.push(ent.name);
   }
   names.sort();

package/adapters/turborepo.mjs

@@ -4,6 +4,7 @@
 // verification answer available for a monorepo unit.
 import { Adapter } from "./registry.mjs";
 import { parseYamlDocuments } from "../core/yaml.mjs";
+import { isRepoRoot, joinPath } from "../core/paths.mjs";
 
 // Whether a declared task is a check is decided by `taskTier` alone, not by a
 // second, narrower pattern. Two lists meant two places to disagree: a task that
@@ -19,7 +20,7 @@ export class TurborepoAdapter extends Adapter {
     super({ name: "turborepo", version: "1.0.0", kind: "ci" });
   }
   detect(ctx, root) {
-    const p = root + "/turbo.json";
+    const p = joinPath(root, "turbo.json");
     if (!ctx.repo.exists(p)) return null;
     return { path: p, shape: "importable" };
   }
@@ -122,7 +123,7 @@ function taskTier(t) {
 
 // A task graph normally lives at the workspace root, not in each package.
 function nearestTurboConfig(repo, root) {
-  let dir = root;
+  let dir = isRepoRoot(root) ? "" : root;
   for (let i = 0; i < 12; i++) {
     const p = dir ? dir + "/turbo.json" : "turbo.json";
     if (repo.exists(p)) return p;