/**
 * Application Debug Snapshot
 *
 * GET /api/applications/:id/debug
 *
 * One-stop diagnostic dump for a stuck application creation. Returns
 * the full persisted state for the application (row, interactive
 * session, every workflow step, recent message timing, recent
 * operation_log_entries) plus computed staleness indicators so the
 * caller can tell at a glance which layer is wedged:
 *
 *  - The "Building the pieces" step has been `running` for X seconds
 *    but no agent message has landed in N seconds → workflow lost
 *    its in-process turn-done event (very likely dev-server HMR or
 *    daemon restart while a Promise was awaiting).
 *  - The interactive session is `ready` / `idle` but the workflow
 *    step is still `running` → the orchestrator's awaiting Promise
 *    is orphaned. Use the existing `force-stop` UI control to
 *    flip the step to `interrupted` and retry.
 *  - The application row's `setup_complete` is `0` and `agent_session_id`
 *    is `null` despite the chat showing tool messages → the workflow
 *    never reached its terminal `update setupComplete=true` write.
 *
 * This route is intentionally thin (presentation pulls everything via
 * existing repository ports through DI — no business logic) and
 * read-only. No state mutation. Safe to hit any time.
 *
 * Surfaced from the application page header in dev mode via the
 * "Debug" link rendered by `application-page.tsx`. Works in production
 * too — there's nothing dev-specific about the data, just the link.
 */
import 'reflect-metadata';
import type { NextRequest } from 'next/server';
import { NextResponse } from 'next/server';
export declare const dynamic = "force-dynamic";
interface RouteParams {
    params: Promise<{
        id: string;
    }>;
}
export declare function GET(_request: NextRequest, { params }: RouteParams): Promise<NextResponse>;
export {};
//# sourceMappingURL=route.d.ts.map