/**
 * Agentuity legacy (v1/v2) runtime detector.
 *
 * v3 dropped `@agentuity/runtime` entirely, so the mere presence of
 * `@agentuity/runtime` at a v1 or v2 major is an unambiguous signal that a
 * project is a legacy app. Legacy apps don't fit the generic buildpack model:
 * they build with the legacy CLI's own `agentuity build` (which bundles a Bun
 * server entry plus a client bundle into `.agentuity/`) and start with
 * `bun .agentuity/app.js`. v1 and v2 share this layout.
 *
 * Without this detector the v3 pipeline mis-classifies a legacy app as a
 * generic `vite` SPA, builds only the client, and ships a deploy that fails at
 * warmup. Detecting it here lets the v3 CLI deploy a legacy app natively by
 * driving the legacy build + packaging the legacy server output.
 *
 * `agentuity build` is supplied by the project-local legacy CLI. The
 * global→local delegation (and self-heal) in `local-delegate.ts` ensures that
 * local CLI is present; when deploying with a non-global v3 CLI the project
 * must already have `@agentuity/cli` installed (legacy scaffolds do by default).
 */
import type { DetectedFramework, PackageJsonData } from './types.ts';
/**
 * Detect a legacy (v1/v2) Agentuity runtime app. Returns a `DetectedFramework`
 * describing how to build (`agentuity build`) and start (`bun .agentuity/app.js`)
 * it, or null when the project isn't a legacy app. The `agentuity-legacy`
 * framework name covers both v1 and v2.
 */
export declare function detectAgentuityLegacy(projectDir: string, pkg: PackageJsonData): Promise<DetectedFramework | null>;
//# sourceMappingURL=agentuity-legacy.d.ts.map