import { type Feature } from './features.js';
/**
 * The toolchain every generated app needs, exported because
 * `scripts/gen-mcp-corpus.ts` puts the same in `@dunx/mcp`'s starter manifest.
 * The base `tsconfig.json` declares `types: ["bun"]`, so a starter without
 * `@types/bun` fails its first `bun check` with TS2688. `bun check` carries its
 * own TypeScript, so there is no `typescript` to install.
 */
export declare const DEV_TOOLCHAIN: Readonly<Record<string, string>>;
export declare const manifest: (features: readonly Feature[], binary?: boolean) => string;
/**
 * Third-party versions, exact for the reason dunx's own manifests are, and
 * written here rather than read off `examples/full` at run time:
 * the generated app installs from npm and the example installs from the workspace,
 * so the example's manifest is not a statement about what a consumer should take.
 * `features.test.ts` checks these against the example's, which is what stops them
 * silently diverging from a version combination that is actually exercised.
 */
export declare const THIRD_PARTY: Readonly<Record<string, string>>;
export declare const appModule: (name: string, features: readonly Feature[]) => string;
export declare const main: (name: string, features: readonly Feature[]) => string;
export declare const envExample: (groups: readonly string[]) => string;
export declare const readme: (name: string, features: readonly Feature[], binary?: boolean) => string;