/**
 * HonoInlineAnalyzer — shared body-analysis for inline handlers and middleware.
 *
 * Walks a tree-sitter syntax node (expected: arrow_function / function_expression)
 * and extracts:
 *   - c.json/text/html/body/redirect/newResponse emissions with status
 *   - throw new HTTPException/Error with status
 *   - Database calls (prisma.*, db.*, knex.*, drizzle*, .query, .execute)
 *   - Fetch calls (fetch, axios.*)
 *   - c.set/get/var/env context access
 *   - Inline validator references (zValidator, vValidator, etc.)
 *   - has_try_catch presence flag
 *
 * Used by HonoExtractor.walkHttpRoutes (Phase 2 T3) and consumed by
 * analyze_inline_handler, extract_response_types, audit_hono_security.
 *
 * Defensive: accepts any node. Non-function nodes return an empty analysis
 * (no throws). Nested functions inside the handler body ARE walked — that is
 * intentional so closures over request context are captured.
 */
import type Parser from "web-tree-sitter";
import type { InlineHandlerAnalysis } from "./hono-model.js";
export declare class HonoInlineAnalyzer {
    /**
     * Analyze a handler/middleware body. The caller (HonoExtractor) owns the
     * file path — line numbers here are node-relative (1-based), file-agnostic.
     *
     * The Hono context parameter name is extracted from the first function
     * parameter, so handlers written as `(ctx) => ...` or `(context) => ...`
     * are recognized as well as the canonical `(c) => ...`.
     */
    analyze(handlerNode: Parser.SyntaxNode): InlineHandlerAnalysis;
}
//# sourceMappingURL=hono-inline-analyzer.d.ts.map