/** * `opensip graph --list-files` — discovery-only mode. * * Resolves the exact source-file set the graph build would analyze for the * requested scope and prints it, WITHOUT building the catalog. This is the * cheap, side-effect-free way to answer "which files does graph actually * see?" — e.g. to diff graph's view of a repo against `git ls-files`. * * Faithfulness: it calls the same adapter stage-0 `discoverFiles` the real * pipeline uses (orchestrate.ts) for the same scope, so the list reflects a * real run — `.d.ts` excluded, TypeScript extension-priority collisions * collapsed (a `foo.tsx` shadowed by a sibling `foo.ts` is dropped), and each * tsconfig's include/exclude honored. * * Scope mirrors the `graph` command's own scoping: * - bare → whole project (the dominant-language adapter's * whole-tree discovery; this is the set a single-process * build analyzes) * - `...` → union of each positional subtree's discovery * - `--workspace` → union of every detected workspace unit's discovery * (per-unit tsconfigs, mirrors resolveShards) — note * this can differ from the whole-project set when a * package's tsconfig excludes paths the root tree does * not (e.g. `__fixtures__`) * - `--language X` → forces adapter X for discovery */ import type { GraphCommandOptions } from './graph-options.js'; import type { ToolCliContext } from '@opensip-cli/core'; /** * Run `graph --list-files`: resolve the discovery set for the scope encoded in * `opts` and emit it through the CLI seam (`emitJson` for `--json`, the * `graph-status` render path otherwise — never raw stdout). Always sets an * exit code; never throws to the caller (errors are mapped via * `handleGraphError`, the same boundary `executeGraph` uses). */ export declare function executeListFiles(opts: GraphCommandOptions, cli: ToolCliContext): Promise; //# sourceMappingURL=list-files.d.ts.map