/**
 * AIWG.md generator — content-rich CLAUDE.md companion for non-Claude providers.
 *
 * Per ADR-1 §0.5: AIWG.md at project root has the same content shape as
 * CLAUDE.md. Both files `@`-reference the project's `.aiwg/AIWG.md` (the
 * source of truth). Non-Claude providers reach AIWG.md transitively via the
 * AGENTS.md `## Framework Context` link. The two project-root files contain
 * identical framework prose; they exist as two named files because Claude
 * Code looks for `CLAUDE.md` and the seven AGENTS.md providers reach
 * AIWG.md via the AGENTS.md hook-up.
 *
 * Generation strategy: read the project's CLAUDE.md (which already exists in
 * a properly-configured repo) and emit AIWG.md as the same content with the
 * AIWG signature comment in place. If CLAUDE.md is absent (early-init repos),
 * fall back to a minimal stub that points readers at `.aiwg/AIWG.md`.
 */
/**
 * Build the AIWG.md content for emission at project root.
 *
 * - When CLAUDE.md exists at project root: copy its content with the AIWG
 *   signature comment inserted in the second line so future runs of the
 *   generator know the file is AIWG-managed.
 * - When CLAUDE.md does not exist: emit a minimal stub directing readers to
 *   the project's `.aiwg/AIWG.md` source.
 *
 * Returns the rendered content as a string. Caller is responsible for the
 * atomic-write emission and the operator-claimed-file detection.
 */
export declare function buildAiwgMdContent(projectPath: string): Promise<string>;
/**
 * Public API: build AIWG.md content for a given project.
 *
 * The wrapper exists so future variants (per-provider AIWG.md customization,
 * AIWG.local.md operator overrides, etc.) have a single entry point in the
 * surface API without callers reaching into the implementation.
 */
export declare function generateAiwgMd(projectPath: string): Promise<string>;
//# sourceMappingURL=aiwg-md.d.ts.map