import type { LspOperation, LspRequestParams, LspResult } from "./lsp.js";
/**
 * file:// URI for an absolute path. channel [388](service win32 真机逮):this serves TWO lanes —
 * TOC host files (NodeLspManager, host semantics correct) AND remote WS-lane container paths
 * (E2B/kata sidecar, Linux form). `pathToFileURL` is HOST-platform-semantic: on a win32 host it
 * parses a remote `/home/user/x.ts` as drive-relative → `file:///C:/home/user/x.ts` → the remote
 * LSP server gets a nonexistent URI(win32 host + 远程 lane 全瘫). Structural form detection
 * instead(与 [385] fs-safety 双家族修同哲学——路径来自 ExecutionEnv,可能是另一家族,绝不按
 * process.platform 判):POSIX-form absolutes are hand-assembled(percent-encoded per segment,
 * no host path module);drive-letter form keeps `pathToFileURL`(CC parity for Windows files).
 * On a POSIX host the hand-assembled branch matches `pathToFileURL(p).href` for typical paths(space 等常见字符同形;极端字符按 encodeURIComponent 更严格,LSP server 两者都收).
 */
export declare function pathToUri(p: string): string;
/**
 * [K-PLATFORM-SWEEP] MINOR#5: structural inverse of {@link pathToUri} — the naive `file://` prefix strip
 * left win-form URIs as `/C:/x` (never matching the didOpen keys) and never percent-decoded (a space in a
 * filename broke the staleness map). Form-detected, never host `fileURLToPath` (cross-family lanes).
 */
export declare function uriToPath(uri: string): string;
/** The follow-up method for the 2-step call ops (issued by the session after prepareCallHierarchy). */
export declare function callHierarchyMethod(op: "incomingCalls" | "outgoingCalls"): string;
/** The LSP method + params for an op (incoming/outgoing FIRST issue prepareCallHierarchy — the session 2-steps). */
export declare function buildRequest(op: LspOperation, params: LspRequestParams): {
    method: string;
    params: unknown;
} | undefined;
export declare function parseResult(op: LspOperation, raw: unknown): LspResult;
//# sourceMappingURL=lsp-protocol.d.ts.map