/**
 * The one MCP App resource this daemon ever serves: a self-contained
 * execution-monitor page rendered by MCP-App-capable hosts (Claude Desktop).
 * Frozen so `tool-surface.ts` and `mcp-adapter.ts` share a single source of
 * truth instead of re-declaring these literals.
 */
/**
 * Stable identity of the execution-app resource, WITHOUT the build fingerprint.
 * `resources/read` still accepts this exact form — see `executionResourceUriMatches`.
 */
export declare const EXECUTION_RESOURCE_URI = "ui://mma/execution.html";
export declare const EXECUTION_RESOURCE_MIME_TYPE = "text/html;profile=mcp-app";
/**
 * JSON-RPC error code for "resource not found". SDK 1.30.0's `ErrorCode`
 * enum has no `ResourceNotFound` member, so this is a named local constant
 * rather than an SDK re-export.
 */
export declare const RESOURCE_NOT_FOUND = -32002;
interface ExecutionArtifact {
    html: string;
    available: boolean;
}
/**
 * Resolve the compiled execution-app bundle path from a module URL.
 *
 * PURE function — takes its base as an argument rather than reading
 * `import.meta.url` internally, precisely so both source-mode (Vitest runs
 * this package straight from `src/` via the workspace alias) and
 * compiled-mode (`dist/mcp/*.js`) callers can be exercised by tests. A
 * resolver that closes over its own module URL could only ever be exercised
 * in whichever mode the test happens to run in, making the regression it
 * guards against untestable by construction.
 *
 * Always resolves to the package's `dist/ui/execution.html` — from compiled
 * `dist/mcp/*` that is the adjacent `../ui/execution.html`; from source/Vitest
 * execution it steps out of `src/` into the sibling `dist/`, never to the
 * unbundled `src/ui/execution/execution.html`.
 *
 * RESOLVED RELATIVE TO THE MODULE, NOT TO AN ABSOLUTE-PATH MARKER. An earlier
 * version searched the module path for a `/packages/server/` segment and fell
 * back to the module path ITSELF when absent. That segment only exists in this
 * monorepo, so every npm-installed copy took the fallback and built a path with
 * the filename embedded in it — `dist/mcp/execution-artifact.js/dist/ui/
 * execution.html` — which never reads. Shipped users therefore always got
 * `available: false`, and the daemon advertised `MCP_CAPABILITIES_TOOLS_ONLY`
 * despite carrying a perfectly good 381 KB bundle. Only the developing
 * monorepo, where the marker happens to match, ever served the App. Layout is
 * a property of the module's own location, so that is the only thing this
 * reads.
 */
export declare function resolveExecutionArtifactPath(moduleUrl: string): string;
/** Returns the same cached object on every call — never re-reads disk. */
export declare function getExecutionArtifact(): ExecutionArtifact;
/**
 * Test-only override to force either branch without touching the real
 * filesystem. Mirrors the `__setCoreTestProviderOverride` convention in
 * `tests/contract/fixtures/harness.ts`. Pass `null` to clear the override
 * back to the real cached/disk-derived value. Never read on any production
 * code path.
 */
export declare function __setExecutionArtifactOverrideForTests(value: ExecutionArtifact | null): void;
/**
 * Advertised URI for the execution app, carrying a fingerprint of the bytes it serves:
 * `ui://mma/execution.html?v=<8 hex>`.
 *
 * Hosts cache a UI resource by URI, and Claude Desktop caches it hard — hard enough that a
 * rebuilt bundle kept being served stale across daemon restarts and new conversations. As a
 * development annoyance that is merely slow; in production it is a shipping bug, because a
 * user who UPGRADES mma would keep running the old App indefinitely with no way to know. A
 * fixed URI gives the host nothing to invalidate on.
 *
 * Content-addressing fixes it at the only layer that can: new bytes produce a new URI, so the
 * cache misses exactly when it should and hits every other time.
 */
export declare function getExecutionResourceUri(): string;
/**
 * Accept the versioned URI AND the bare one.
 *
 * A host that cached an OLDER fingerprint will ask for that older URI. Refusing it would turn
 * a stale cache into a hard failure — strictly worse than serving current bytes under a name
 * the host happens to remember, since the response body is the truth either way. Any `?v=`
 * is therefore accepted and ignored; only the path has to match.
 */
export declare function executionResourceUriMatches(uri: string): boolean;
export {};
//# sourceMappingURL=execution-artifact.d.ts.map