/**
 * analyze_inline_handler — returns structured body analysis for a specific
 * inline handler. Consumes HonoRoute.inline_analysis populated by T3.
 *
 * Closes blog API demo gap #1: all 7 blog routes are (c) => c.json(...) inline
 * arrows, and Phase 1 reported them as opaque "<inline>" handlers with zero
 * introspection. With this tool, callers can ask "what does GET /users/:id do?"
 * and get responses, errors, DB calls, fetch calls, context access, and
 * validators — all statically extracted.
 *
 * Spec: docs/specs/2026-04-11-hono-phase-2-plan.md (T8)
 */
import type { InlineHandlerAnalysis } from "../parser/extractors/hono-model.js";
export interface InlineHandlerReport {
    route: string;
    file: string;
    line: number;
    analysis: InlineHandlerAnalysis;
}
export interface InlineHandlerResult {
    reports?: InlineHandlerReport[];
    total?: number;
    error?: string;
}
/**
 * @param repo repository identifier
 * @param method optional HTTP method filter (e.g. "GET"); case-insensitive
 * @param path optional path filter (e.g. "/users/:id"); exact match
 */
export declare function analyzeInlineHandler(repo: string, method?: string, routePath?: string): Promise<InlineHandlerResult>;
//# sourceMappingURL=hono-inline-analyze.d.ts.map