/**
 * Built-in tools plugin.
 *
 * Owns registration of the cross-platform meta tools (`device`, `screen`,
 * `ui`, ...), their v3.0.x/v3.1.x backward-compat aliases, and the module
 * metadata catalog.
 *
 * History
 * -------
 * - D4 (3.12.0) moved meta-tool registration out of `src/index.ts` into this
 *   plugin so the entry point no longer hard-codes the meta-tool surface.
 * - D8.3 (3.12.0) moved the meta-tool *catalogue* out of this plugin into
 *   `src/tools/meta/index.ts`. The plugin no longer enumerates every meta
 *   tool — it iterates `META_TOOL_DESCRIPTORS` and forwards aliases from
 *   `META_SHORT_ALIASES` / `META_LEGACY_ALIASES`. Adding a meta tool means
 *   touching the barrel only; this file is now stable.
 *
 * Design notes
 * ------------
 * - Meta tools use the legacy `ToolDefinition` shape (`{ tool, handler }`)
 *   carrying a `ToolContext` per call. The plugin-api `ToolDefinition`
 *   doesn't model that context, and `PluginContext.registerTool` only
 *   accepts the plugin-api shape — so registration goes through the legacy
 *   `registerTools` / `registerToolsHidden` functions directly. This keeps
 *   the public effect identical: visible meta tools end up in `toolMap`,
 *   hidden ones in `toolMap + hiddenTools`. Extending `PluginContext` to
 *   carry a typed tool-context is a separate scope.
 * - Profile resolution stays here: it reads `MOBILE_PROFILE` from
 *   `ctx.config` first (forwarded by the kernel via `configFor` if a host
 *   ever opts in), falling back to `process.env.MOBILE_PROFILE` to keep
 *   behaviour identical for the MCP entry point.
 */
import type { PluginContext, PluginManifest, SourcePlugin } from "@claude-in-mobile/plugin-api";
export declare const BUILTIN_TOOLS_PLUGIN_MANIFEST: PluginManifest;
export declare class BuiltinToolsPlugin implements SourcePlugin {
    readonly manifest: PluginManifest;
    init(ctx: PluginContext): void;
}
export declare function createBuiltinToolsPlugin(): SourcePlugin;
//# sourceMappingURL=index.d.ts.map