/**
 * Default-path resolver for the top-level `sqlite` block (issue #401).
 *
 * Policy:
 *  - **dev + node + non-CLI**: `<projectRoot>/dist/sessions.sqlite` —
 *    keeps dev data under the project tree so multiple frontmcp apps in
 *    different repos don't share the same database.
 *  - **prod OR CLI mode**: `~/.{appName}/sessions.sqlite` — per-app
 *    namespace under the user's home directory. Multiple installed
 *    frontmcp apps therefore get isolated databases. Falls back to
 *    `~/.frontmcp/` when `info.name` is missing or unsanitizable.
 *  - **edge / non-node runtimes**: never apply a default path; callers
 *    must surface the existing edge-runtime error (better-sqlite3 is a
 *    native module and won't load there).
 *
 * The resolver is pure — it returns a string. Filesystem side-effects
 * (mkdir on the parent dir) happen in the caller after the path is
 * resolved so this module stays unit-testable without a real disk.
 */
export interface SqlitePathResolverContext {
    /** Server name from `@FrontMcp({ info: { name } })`. */
    appName?: string;
    /** True when the SDK is running under the `frontmcp` CLI. */
    cliMode: boolean;
    /** Override for process.cwd() (used by tests). */
    cwd?: string;
}
export declare function resolveDefaultSqlitePath(ctx: SqlitePathResolverContext): string;
//# sourceMappingURL=resolve.d.ts.map