/**
 * Build the full eslint flat-config array from pipework.config.ts.
 *
 * The generated `eslint.config.js` delegates here, passing its own directory as `cwd` —
 * eslint resolves flat-config globs against that directory, not the process cwd.
 * Everything that would normally live in `eslint.config.js` — extra plugins, rules, additional
 * flat-config blocks — flows through `pipework.config.ts` so pipework remains the single source
 * of truth and the generated file stays byte-stable for `pipework check`.
 *
 * Shape:
 *   - `lint.extra.plugins` → registered in pipework's main lint block; rules under
 *     `lint.extra.rules` (or `pipework`'s built-in rules) can reference them as `name/rule`.
 *   - `lint.extra.rules` → merged into pipework's main block (can override defaults).
 *   - `lint.extra.configs` → appended as additional flat-config entries after pipework's block.
 *   - `lint.include` (or a module's own `include`) → the block's `files`. Unset, the globs
 *     are derived from the workspace rooted at `base`: a glob for `src` plus one per
 *     workspace package under it, nested workspaces included. Without either, a package
 *     whose sources are not under `base/src` matches no block, eslint reports "no matching
 *     configuration", and `pipework check` still prints Lint ✓ (#392, #393).
 *   - `lint.modules` → per-module overrides. When `cwd` resolves inside a declared module
 *     (the case for every per-module `pipework check` lint pass), that module's `rules` and
 *     `configs` are layered on top of `lint.extra`. At repo root they do not apply — a
 *     per-module override belongs to its module, not the root lint pass.
 */
export declare function resolveLintConfig(cwd?: string): Promise<unknown[]>;
//# sourceMappingURL=resolver.d.ts.map