/**
 * extract_response_types — aggregates all statically-knowable response types
 * (status code + body shape hint + error classes) per route. Closes Hono
 * GitHub Issue #4270: error response types are not inferrable by RPC clients
 * so client-side type narrowing silently drops them. This tool surfaces them
 * from the inline_analysis data so callers can generate RPC client types
 * that include error paths.
 *
 * Spec: docs/specs/2026-04-11-hono-phase-2-plan.md (T9)
 */
export interface ResponseTypeEntry {
    status: number;
    kind: "json" | "text" | "html" | "body" | "redirect" | "newResponse";
    shape_hint?: string;
}
export interface ErrorTypeEntry {
    status: number;
    exception_class: string;
    message_hint?: string;
}
export interface RouteResponseTypes {
    route: string;
    file: string;
    line: number;
    responses: ResponseTypeEntry[];
    errors: ErrorTypeEntry[];
    /** Distinct status codes reachable (union of responses + errors). */
    status_codes: number[];
}
export interface ResponseTypesResult {
    routes?: RouteResponseTypes[];
    total_routes?: number;
    total_statuses?: number;
    error?: string;
}
export declare function extractResponseTypes(repo: string): Promise<ResponseTypesResult>;
//# sourceMappingURL=hono-response-types.d.ts.map