melchizedek-agents 0.19.0 → 1.0.0

package/dist/lib/tools/memoryTools.d.ts

@@ -5,9 +5,8 @@
  * WHY this file exists:
  *   A syndicate with `memory_system: long-term` reaches its memory through
  *   two YAML tool names. Both were ADK's own objects (LOAD_MEMORY and
- *   PRELOAD_MEMORY), which only ADK's loop can run. Here they are the
- *   engine's, so the native runtime runs them, and the ADK runtime runs the
- *   same objects through lib/tools/adkTool.ts:
+ *   PRELOAD_MEMORY), which only ADK's loop could run. Here they are the
+ *   engine's, and the native loop runs them:
  *
  *     load_memory     a Tool the model calls with a query. It returns the
  *                     facts recalled for it, and while the run has memory it
@@ -18,8 +17,8 @@
  *
  * WORD FOR WORD: the declaration, the note, the result's shape and the
  * recalled block are what ADK's LoadMemoryTool and PreloadMemoryTool
- * produced, so a model reads the same request on either runtime
- * (tests/memoryTools.test.ts compares them with ADK's own tools).
+ * produced, so a model reads the request it read before 1.0.0
+ * (tests/memoryTools.test.ts holds them to ADK's recorded output).
  *
  * WHOSE MEMORY: both search through the context's `searchMemory`, which is
  * bound to the run's own `<appName>/<userId>` silo; a query can choose what
@@ -38,7 +37,7 @@ import type { InstructionTool } from './tool.ts';
 export declare const LOAD_MEMORY_INSTRUCTION = "You have memory. You can use it to answer questions. If any questions need\nyou to look up the memory, you should call load_memory function with a query.";
 /** What load_memory and ADK's LoadMemoryTool say when the run has no memory service. */
 export declare const NO_MEMORY_SERVICE = "Memory service is not initialized.";
-/** A memory's text: its parts' texts joined by a space, a part without text counting as empty, as ADK joins them. */
+/** A memory's text: its parts' texts joined by a space, a part without text counting as empty, as ADK joined them. */
 export declare function memoryText(memory: MemoryEntry): string;
 /** One recalled memory as load_memory returns it. */
 export interface LoadedMemory {

package/dist/lib/tools/memoryTools.js

@@ -5,9 +5,8 @@
  * WHY this file exists:
  *   A syndicate with `memory_system: long-term` reaches its memory through
  *   two YAML tool names. Both were ADK's own objects (LOAD_MEMORY and
- *   PRELOAD_MEMORY), which only ADK's loop can run. Here they are the
- *   engine's, so the native runtime runs them, and the ADK runtime runs the
- *   same objects through lib/tools/adkTool.ts:
+ *   PRELOAD_MEMORY), which only ADK's loop could run. Here they are the
+ *   engine's, and the native loop runs them:
  *
  *     load_memory     a Tool the model calls with a query. It returns the
  *                     facts recalled for it, and while the run has memory it
@@ -18,8 +17,8 @@
  *
  * WORD FOR WORD: the declaration, the note, the result's shape and the
  * recalled block are what ADK's LoadMemoryTool and PreloadMemoryTool
- * produced, so a model reads the same request on either runtime
- * (tests/memoryTools.test.ts compares them with ADK's own tools).
+ * produced, so a model reads the request it read before 1.0.0
+ * (tests/memoryTools.test.ts holds them to ADK's recorded output).
  *
  * WHOSE MEMORY: both search through the context's `searchMemory`, which is
  * bound to the run's own `<appName>/<userId>` silo; a query can choose what
@@ -38,7 +37,7 @@ export const LOAD_MEMORY_INSTRUCTION = `You have memory. You can use it to answe
 you to look up the memory, you should call load_memory function with a query.`;
 /** What load_memory and ADK's LoadMemoryTool say when the run has no memory service. */
 export const NO_MEMORY_SERVICE = 'Memory service is not initialized.';
-/** A memory's text: its parts' texts joined by a space, a part without text counting as empty, as ADK joins them. */
+/** A memory's text: its parts' texts joined by a space, a part without text counting as empty, as ADK joined them. */
 export function memoryText(memory) {
     return memory.content.parts?.map((p) => p.text ?? '').join(' ') ?? '';
 }

package/dist/lib/tools/nativeTools.d.ts

@@ -5,20 +5,15 @@
  * WHY this file exists:
  *   web_search, x_search, url_context and collections_search are run by the
  *   provider, not here: the model asks its own vendor to search or read, and
- *   the answer arrives inside the model's response. Each was an ADK BaseTool
- *   that declared nothing and left itself in the request for the adapter to
- *   find. The native runtime needs them without ADK, so each is first a
- *   NativeToolMarker (lib/tools/tool.ts): a name, a description for a reader,
- *   and the NativeTool it stands for. A marker declares no function; a
- *   request carries it in `nativeTools`, and each adapter adds its
- *   provider's tool object or drops it (lib/models/capabilities.ts).
- *
- *   The ADK runtime keeps its sentinels (lib/tools/webSearchTool.ts and its
- *   siblings), which carry the same marker symbol, so every reader
- *   (nativeToolOf in lib/models/schemaNormalize.ts) recognises both by
- *   marker. lib/tools/adkTool.ts turns a marker into its sentinel
- *   (toAdkNativeTool). google_search is ADK's own GOOGLE_SEARCH on that
- *   runtime, recognised by ADK's marker.
+ *   the answer arrives inside the model's response. Under ADK each was a
+ *   BaseTool that declared nothing and left itself in the request for the
+ *   adapter to find. Here each is a NativeToolMarker (lib/tools/tool.ts): a
+ *   name, a description for a reader, and the NativeTool it stands for. A
+ *   marker declares no function; a request carries it in `nativeTools`, and
+ *   each adapter adds its provider's tool object or drops it
+ *   (lib/models/capabilities.ts). Every reader (nativeToolOf in
+ *   lib/models/schemaNormalize.ts) recognises a marker by its symbol, never
+ *   by class.
  *
  *   Code execution is not here: it is an agent's `code_execution: gemini`,
  *   not a tool it lists, and reaches the request as the agent's code

package/dist/lib/tools/nativeTools.js

@@ -5,20 +5,15 @@
  * WHY this file exists:
  *   web_search, x_search, url_context and collections_search are run by the
  *   provider, not here: the model asks its own vendor to search or read, and
- *   the answer arrives inside the model's response. Each was an ADK BaseTool
- *   that declared nothing and left itself in the request for the adapter to
- *   find. The native runtime needs them without ADK, so each is first a
- *   NativeToolMarker (lib/tools/tool.ts): a name, a description for a reader,
- *   and the NativeTool it stands for. A marker declares no function; a
- *   request carries it in `nativeTools`, and each adapter adds its
- *   provider's tool object or drops it (lib/models/capabilities.ts).
- *
- *   The ADK runtime keeps its sentinels (lib/tools/webSearchTool.ts and its
- *   siblings), which carry the same marker symbol, so every reader
- *   (nativeToolOf in lib/models/schemaNormalize.ts) recognises both by
- *   marker. lib/tools/adkTool.ts turns a marker into its sentinel
- *   (toAdkNativeTool). google_search is ADK's own GOOGLE_SEARCH on that
- *   runtime, recognised by ADK's marker.
+ *   the answer arrives inside the model's response. Under ADK each was a
+ *   BaseTool that declared nothing and left itself in the request for the
+ *   adapter to find. Here each is a NativeToolMarker (lib/tools/tool.ts): a
+ *   name, a description for a reader, and the NativeTool it stands for. A
+ *   marker declares no function; a request carries it in `nativeTools`, and
+ *   each adapter adds its provider's tool object or drops it
+ *   (lib/models/capabilities.ts). Every reader (nativeToolOf in
+ *   lib/models/schemaNormalize.ts) recognises a marker by its symbol, never
+ *   by class.
  *
  *   Code execution is not here: it is an agent's `code_execution: gemini`,
  *   not a tool it lists, and reaches the request as the agent's code

package/dist/lib/tools/openapiTools.d.ts

@@ -1,4 +1,3 @@
-import type { FunctionTool } from '@google/adk';
 import type { Tool } from './tool.ts';
 export { namesTool, toSnake } from './openapi/parse.ts';
 export interface OpenApiAuthConfig {
@@ -43,18 +42,17 @@ export declare function credentialEnvProblem(name: string, env?: NodeJS.ProcessE
  */
 export declare function boundResult(result: unknown): unknown;
 /**
- * The own Tools one `openapi:` entry gives an agent, for either runtime.
+ * The own Tools one `openapi:` entry gives an agent.
  * Throws (failing the compile) on a missing spec, an unset auth variable,
  * an operation the spec does not have, or a server the guard refuses.
  */
 export declare function buildOpenApiOwnTools(entry: OpenApiConfig, baseDir?: string): Promise<Tool[]>;
 /**
- * The tools one `openapi:` entry gives an agent on the ADK runtime: each own
- * Tool through toFunctionTool, marked so require_approval can name it by
- * its operationId. ADK's RestApiTool and OpenAPIToolset are not used.
+ * The tools one `openapi:` entry gives an agent: buildOpenApiOwnTools' own
+ * Tools, each marked so require_approval can name it by its operationId.
  */
-export declare function buildOpenApiTools(entry: OpenApiConfig, baseDir?: string): Promise<FunctionTool[]>;
-/** The operationId of a tool built from an `openapi:` entry (own or ADK), or undefined. */
+export declare function buildOpenApiTools(entry: OpenApiConfig, baseDir?: string): Promise<Tool[]>;
+/** The operationId of a tool built from an `openapi:` entry, or undefined. */
 export declare function openApiOperationId(tool: unknown): string | undefined;
 /** True for a tool built from an `openapi:` entry. */
 export declare function isOpenApiTool(tool: unknown): boolean;

package/dist/lib/tools/openapiTools.js

@@ -10,8 +10,7 @@
  * tools and builds their declarations, by the rules ADK's OpenAPIToolset
  * had; the engine's own caller (lib/tools/openapi/call.ts, ADR 0067) sends
  * each call, by the rules ADK's RestApiTool had. Each operation is an own
- * Tool (lib/tools/tool.ts), which the ADK runtime runs through
- * toFunctionTool. An agent's `openapi:` list hands it a spec file:
+ * Tool (lib/tools/tool.ts). An agent's `openapi:` list hands it a spec file:
  *
  *   openapi:
  *     - spec: "specs/weather.yaml"          # beside this YAML file
@@ -60,7 +59,6 @@
  */
 import { closeSync, openSync, readSync } from 'node:fs';
 import { extname, resolve } from 'node:path';
-import { toFunctionTool } from './adkTool.js';
 import { MAX_RESULT_CHARS as TOOL_RESULT_CHARS, capResult } from './tool.js';
 import { callOperation, hostProblem } from './openapi/call.js';
 import { MAX_SPEC_BYTES, operationNamed, parseOpenApiSpec } from './openapi/parse.js';
@@ -167,7 +165,7 @@ function operationTool(op, credential) {
     return tool;
 }
 /**
- * The own Tools one `openapi:` entry gives an agent, for either runtime.
+ * The own Tools one `openapi:` entry gives an agent.
  * Throws (failing the compile) on a missing spec, an unset auth variable,
  * an operation the spec does not have, or a server the guard refuses.
  */
@@ -204,18 +202,13 @@ export async function buildOpenApiOwnTools(entry, baseDir = process.cwd()) {
     return chosen.map((o) => operationTool(o, credential));
 }
 /**
- * The tools one `openapi:` entry gives an agent on the ADK runtime: each own
- * Tool through toFunctionTool, marked so require_approval can name it by
- * its operationId. ADK's RestApiTool and OpenAPIToolset are not used.
+ * The tools one `openapi:` entry gives an agent: buildOpenApiOwnTools' own
+ * Tools, each marked so require_approval can name it by its operationId.
  */
 export async function buildOpenApiTools(entry, baseDir = process.cwd()) {
-    return (await buildOpenApiOwnTools(entry, baseDir)).map((own) => {
-        const adkTool = toFunctionTool(own);
-        Object.defineProperty(adkTool, OPENAPI_TOOL, { value: openApiOperationId(own) });
-        return adkTool;
-    });
+    return buildOpenApiOwnTools(entry, baseDir);
 }
-/** The operationId of a tool built from an `openapi:` entry (own or ADK), or undefined. */
+/** The operationId of a tool built from an `openapi:` entry, or undefined. */
 export function openApiOperationId(tool) {
     if (!tool || typeof tool !== 'object')
         return undefined;

package/dist/lib/tools/scienceTools.d.ts

@@ -1,9 +1,9 @@
 /**
  * lib/tools/scienceTools.ts — the clinical-evidence tools, defined as tool
  * CONTRACTS (lib/tools/toolContract.ts): one zod schema per tool is the single
- * source of truth, from which both deployment surfaces derive — the ADK
- * FunctionTools consumed by lib/toolRegistry.ts, and the MCP tools/list entries
- * served by scripts/science_mcp_server.ts.
+ * source of truth, from which both deployment surfaces derive — the own Tools
+ * consumed by lib/toolRegistry.ts, and the MCP tools/list entries served by
+ * scripts/science_mcp_server.ts.
  *
  * Ported from the science desk (2026-09-08). The four source clients under
  * lib/tools/science/ are that desk's, verbatim: Europe PMC (literature and

package/dist/lib/tools/scienceTools.js

@@ -1,9 +1,9 @@
 /**
  * lib/tools/scienceTools.ts — the clinical-evidence tools, defined as tool
  * CONTRACTS (lib/tools/toolContract.ts): one zod schema per tool is the single
- * source of truth, from which both deployment surfaces derive — the ADK
- * FunctionTools consumed by lib/toolRegistry.ts, and the MCP tools/list entries
- * served by scripts/science_mcp_server.ts.
+ * source of truth, from which both deployment surfaces derive — the own Tools
+ * consumed by lib/toolRegistry.ts, and the MCP tools/list entries served by
+ * scripts/science_mcp_server.ts.
  *
  * Ported from the science desk (2026-09-08). The four source clients under
  * lib/tools/science/ are that desk's, verbatim: Europe PMC (literature and
@@ -268,10 +268,8 @@ export const SCIENCE_TOOL_CONTRACTS = [
     surveyFieldContract,
     checkRetractionContract,
 ];
-// No `export const …Tool = toFunctionTool(…)` line here on purpose.
-// lib/toolRegistry.ts derives the ADK FunctionTools itself, straight from
-// SCIENCE_TOOL_CONTRACTS — the same shape lib/tools/wikiTools.ts uses. Seven
-// eagerly-built duplicates used to sit here that nothing imported, so every
-// consumer of this module (the MCP server and scripts/wiki/build.ts among them,
-// neither of which wants ADK tools at all) paid for seven schema conversions
-// and seven FunctionTool constructions at import time.
+// No `export const …Tool = asTool(…)` line here on purpose.
+// lib/toolRegistry.ts derives the registry's tools itself, straight from
+// SCIENCE_TOOL_CONTRACTS — the same shape lib/tools/wikiTools.ts uses — so a
+// consumer of this module that wants only the contracts (the MCP server,
+// scripts/wiki/build.ts) builds nothing else at import time.

package/dist/lib/tools/skillToolset.d.ts

@@ -30,8 +30,7 @@
  * THE PIECES (lib/tools/skills/, no ADK import): frontmatter.ts reads and
  *   checks a SKILL.md, loader.ts loads a directory of skills, executor.ts
  *   runs a script on this machine, tools.ts holds the tools and the
- *   SkillToolset. The ADK runtime runs the toolset through
- *   lib/tools/adkTool.ts (toAdkToolset), as it runs every own Tool.
+ *   SkillToolset. The native loop expands the toolset before each request.
  *
  * WHAT RUNS: only scripts shipped in a skill's `scripts/` directory, on
  *   the local executor (`skills.scripts: local`), after approval. The

package/dist/lib/tools/skillToolset.js

@@ -30,8 +30,7 @@
  * THE PIECES (lib/tools/skills/, no ADK import): frontmatter.ts reads and
  *   checks a SKILL.md, loader.ts loads a directory of skills, executor.ts
  *   runs a script on this machine, tools.ts holds the tools and the
- *   SkillToolset. The ADK runtime runs the toolset through
- *   lib/tools/adkTool.ts (toAdkToolset), as it runs every own Tool.
+ *   SkillToolset. The native loop expands the toolset before each request.
  *
  * WHAT RUNS: only scripts shipped in a skill's `scripts/` directory, on
  *   the local executor (`skills.scripts: local`), after approval. The

package/dist/lib/tools/skills/executor.d.ts

@@ -7,7 +7,7 @@
  *   `skills.scripts: local` (ADR 0029) runs a skill's own scripts after a
  *   person approves each run (run_skill_script in ./tools.ts). The harness
  *   ran them through ADK's local executor until WS3-3. This module runs
- *   them the same way, so a run returns the same result on either runtime.
+ *   them the same way, so a run returns the result it returned under ADK.
  *
  * WHAT A RUN IS, AND WHAT A SCRIPT CAN REACH (unchanged from ADK's executor):
  *   1. A fresh private directory under the OS temp directory (mkdtemp,

package/dist/lib/tools/skills/executor.js

@@ -7,7 +7,7 @@
  *   `skills.scripts: local` (ADR 0029) runs a skill's own scripts after a
  *   person approves each run (run_skill_script in ./tools.ts). The harness
  *   ran them through ADK's local executor until WS3-3. This module runs
- *   them the same way, so a run returns the same result on either runtime.
+ *   them the same way, so a run returns the result it returned under ADK.
  *
  * WHAT A RUN IS, AND WHAT A SCRIPT CAN REACH (unchanged from ADK's executor):
  *   1. A fresh private directory under the OS temp directory (mkdtemp,

package/dist/lib/tools/skills/frontmatter.d.ts

@@ -7,8 +7,8 @@
  *   frontmatter (the open Agent Skills standard): `name`, `description`,
  *   and optionally `license`, `compatibility`, `allowed-tools` and
  *   `metadata`. The harness read it through ADK's loader until WS3-3. This
- *   module reads it the same way, so a skill loads to the same object on
- *   either runtime and the frontmatter a model sees in load_skill's result
+ *   module reads it the same way, so a skill loads to the same object it
+ *   did under ADK and the frontmatter a model sees in load_skill's result
  *   does not change:
  *   - the frontmatter is the text between the opening `---` and the next
  *     `---`, wherever it falls, and the body is everything after that,

package/dist/lib/tools/skills/frontmatter.js

@@ -7,8 +7,8 @@
  *   frontmatter (the open Agent Skills standard): `name`, `description`,
  *   and optionally `license`, `compatibility`, `allowed-tools` and
  *   `metadata`. The harness read it through ADK's loader until WS3-3. This
- *   module reads it the same way, so a skill loads to the same object on
- *   either runtime and the frontmatter a model sees in load_skill's result
+ *   module reads it the same way, so a skill loads to the same object it
+ *   did under ADK and the frontmatter a model sees in load_skill's result
  *   does not change:
  *   - the frontmatter is the text between the opening `---` and the next
  *     `---`, wherever it falls, and the body is everything after that,

package/dist/lib/tools/skills/tools.d.ts

@@ -4,11 +4,9 @@
  *
  * WHY this file exists:
  *   The skills harness (ADR 0029) was built on ADK's SkillToolset until
- *   WS3-3. These are the same tools as own Tools, so the native loop runs
- *   them directly and the ADK runtime runs them through the one tool
- *   adapter (lib/tools/adkTool.ts, toAdkToolset). A model is sent the same
- *   names, descriptions and parameters as before, and reads the same
- *   results and error texts, on either runtime:
+ *   WS3-3. These are the same tools as own Tools, and the native loop runs
+ *   them directly. A model is sent the same names, descriptions and
+ *   parameters as before, and reads the same results and error texts:
  *   - list_skills: the `<available_skills>` index (ADK's ListSkillsTool).
  *     The harness leaves it out, since the index is in the instruction.
  *   - load_skill: the procedure, the frontmatter and the NAMES of the files
@@ -21,8 +19,8 @@
  *     skill ships on the local executor (./executor.ts).
  *
  * ACTIVATION: load_skill appends the skill's name to the session state key
- *   `_adk_activated_skill_<agent>` (ADK's key, so a session stored by
- *   either runtime reads the same). SkillToolset.getTools reads it and adds
+ *   `_adk_activated_skill_<agent>` (ADK's key, so a session ADK stored
+ *   reads the same). SkillToolset.getTools reads it and adds
  *   the tools the activated skills name (`metadata.adk_additional_tools`,
  *   filled from `allowed-tools`), but only from the tools the YAML handed
  *   it under `skills.tools`: a skill cannot grant itself a tool the YAML
@@ -66,7 +64,7 @@ export interface SkillToolsetOptions {
  * The tools an agent with `skills:` carries: load_skill and
  * load_skill_resource always, run_skill_script with `scripts: local`, and
  * the tools its loaded skills unlock. A toolset by shape (getTools), which
- * the native loop expands and lib/tools/adkTool.ts wraps for ADK.
+ * the native loop expands.
  */
 export declare class SkillToolset implements Toolset {
     #private;
@@ -156,8 +154,8 @@ export declare class LoadSkillResourceTool extends SkillTool {
  * run_skill_script behind a person's approval: the first call asks for it
  * (the hint names the skill, the script and the arguments) and returns
  * without running; the call made again with the answer runs only when the
- * answer approved it. The confirmation travels as `adk_request_confirmation`
- * on either runtime, so the turn pauses `input-required` exactly as for
+ * answer approved it. The confirmation travels as `adk_request_confirmation`,
+ * so the turn pauses `input-required` exactly as for
  * `require_approval` (ADR 0028), with this tool's own texts.
  */
 export declare class RunSkillScriptTool extends SkillTool {

package/dist/lib/tools/skills/tools.js

@@ -4,11 +4,9 @@
  *
  * WHY this file exists:
  *   The skills harness (ADR 0029) was built on ADK's SkillToolset until
- *   WS3-3. These are the same tools as own Tools, so the native loop runs
- *   them directly and the ADK runtime runs them through the one tool
- *   adapter (lib/tools/adkTool.ts, toAdkToolset). A model is sent the same
- *   names, descriptions and parameters as before, and reads the same
- *   results and error texts, on either runtime:
+ *   WS3-3. These are the same tools as own Tools, and the native loop runs
+ *   them directly. A model is sent the same names, descriptions and
+ *   parameters as before, and reads the same results and error texts:
  *   - list_skills: the `<available_skills>` index (ADK's ListSkillsTool).
  *     The harness leaves it out, since the index is in the instruction.
  *   - load_skill: the procedure, the frontmatter and the NAMES of the files
@@ -21,8 +19,8 @@
  *     skill ships on the local executor (./executor.ts).
  *
  * ACTIVATION: load_skill appends the skill's name to the session state key
- *   `_adk_activated_skill_<agent>` (ADK's key, so a session stored by
- *   either runtime reads the same). SkillToolset.getTools reads it and adds
+ *   `_adk_activated_skill_<agent>` (ADK's key, so a session ADK stored
+ *   reads the same). SkillToolset.getTools reads it and adds
  *   the tools the activated skills name (`metadata.adk_additional_tools`,
  *   filled from `allowed-tools`), but only from the tools the YAML handed
  *   it under `skills.tools`: a skill cannot grant itself a tool the YAML
@@ -89,7 +87,7 @@ function isToolsetShaped(value) {
  * The tools an agent with `skills:` carries: load_skill and
  * load_skill_resource always, run_skill_script with `scripts: local`, and
  * the tools its loaded skills unlock. A toolset by shape (getTools), which
- * the native loop expands and lib/tools/adkTool.ts wraps for ADK.
+ * the native loop expands.
  */
 export class SkillToolset {
     name = 'skill_toolset';
@@ -321,8 +319,8 @@ export class LoadSkillResourceTool extends SkillTool {
  * run_skill_script behind a person's approval: the first call asks for it
  * (the hint names the skill, the script and the arguments) and returns
  * without running; the call made again with the answer runs only when the
- * answer approved it. The confirmation travels as `adk_request_confirmation`
- * on either runtime, so the turn pauses `input-required` exactly as for
+ * answer approved it. The confirmation travels as `adk_request_confirmation`,
+ * so the turn pauses `input-required` exactly as for
  * `require_approval` (ADR 0028), with this tool's own texts.
  */
 export class RunSkillScriptTool extends SkillTool {
@@ -351,7 +349,7 @@ export class RunSkillScriptTool extends SkillTool {
             return { error: 'This script run was rejected.' };
         return this.#run(args);
     }
-    /** ADK's RunSkillScriptTool.runAsync, after the gate. */
+    /** The script run, after the gate, as ADK's RunSkillScriptTool ran it. */
     async #run(args) {
         const skillName = stringArg(args, 'skill_name');
         const scriptPath = stringArg(args, 'script_path');

package/dist/lib/tools/tool.d.ts

@@ -3,14 +3,12 @@
  * call hands it (ADR 0045, ADR 0051).
  *
  * WHY this file exists:
- *   Every tool used to be an ADK FunctionTool, so running one needed ADK's
- *   loop and ADK's `Context`. The native runtime owns its loop, so it owns
- *   the tool's shape too: a name, the declaration the model receives (the
- *   model contract's ToolDeclaration, lib/models/contract.ts), and an
- *   `execute(args, ctx)` the loop calls. During the dual-runtime period the
- *   ADK runtime runs the same tools through one wrapper,
- *   lib/tools/adkTool.ts (`toFunctionTool`), so a tool is written once and
- *   runs on both.
+ *   The engine owns its loop, so it owns the tool's shape too: a name, the
+ *   declaration the model receives (the model contract's ToolDeclaration,
+ *   lib/models/contract.ts), and an `execute(args, ctx)` the loop calls.
+ *   Nothing here needs ADK's FunctionTool or its `Context`; registerTool
+ *   refuses an ADK tool (anything with runAsync), naming 1.0.0 and
+ *   defineTool.
  *
  *   A tool is usually built with `defineTool` (lib/tools/toolContract.ts),
  *   which derives the declaration from a zod schema and validates arguments
@@ -75,7 +73,7 @@ export interface ToolActions {
     skipSummarization?: boolean;
 }
 export interface ToolContext {
-    /** The run (ADK's invocation) this call belongs to. */
+    /** The run (an invocation, in ADK's word) this call belongs to. */
     readonly invocationId?: string;
     /** The agent whose model asked for the call. */
     readonly agentName?: string;
@@ -130,9 +128,8 @@ export interface ToolContext {
      * person has granted it their next message runs this call again, when
      * `accessToken(provider)` returns their token. `accessToken` asks by itself
      * when the person has not connected the provider, so most tools never
-     * call this. Present only on the native runtime, in a run with a consent
-     * step, for a call the turn runs directly (not inside a delegated
-     * subagent).
+     * call this. Present only in a run with a consent step, for a call the
+     * turn runs directly (not inside a delegated subagent).
      */
     readonly requestCredential?: (provider: string) => Promise<void>;
 }
@@ -184,15 +181,15 @@ export interface ToolsetContext {
  * Listed under an agent's tools like a Tool, but yields the tools the agent
  * has for the next request: the skills harness (lib/tools/skills/tools.ts),
  * whose tools grow as skills are loaded. The native loop expands it before
- * every request; lib/tools/adkTool.ts wraps it as an ADK BaseToolset.
+ * every request.
  */
 export interface Toolset {
     readonly name?: string;
     getTools(ctx?: ToolsetContext): Promise<unknown[]>;
 }
-/** True for an own Toolset: getTools, and neither a Tool nor an ADK tool or toolset. */
+/** True for an own Toolset: getTools, and neither a Tool nor an ADK-shaped tool or toolset (runAsync, processLlmRequest). */
 export declare function isOwnToolset(value: unknown): value is Toolset;
-/** The own Toolset behind `value`: the value itself, or the one an ADK toolset was made from by toAdkToolset. */
+/** The own Toolset `value` is, else undefined. */
 export declare function toolsetOf(value: unknown): Toolset | undefined;
 /**
  * Listed under an agent's `tools:` like a Tool, but declares no function and
@@ -205,8 +202,7 @@ export interface InstructionTool {
 }
 /**
  * Where a server-side tool names the NativeTool it stands for. A global
- * symbol, so a second copy of this module, or an ADK sentinel made from a
- * marker, still matches.
+ * symbol, so a second copy of this module still matches.
  */
 export declare const NATIVE_TOOL: unique symbol;
 /**
@@ -226,8 +222,8 @@ export interface NativeToolMarker {
 export declare function nativeToolMarker(nativeTool: NativeTool, description?: string): NativeToolMarker;
 /**
  * The NativeTool `value` stands for, read from its marker: the marker
- * itself, or anything carrying the marker's symbol (the ADK sentinels in
- * lib/tools/*Tool.ts carry it). Undefined for anything else. Never by class
+ * itself, or anything carrying the marker's symbol. Undefined for anything
+ * else. Never by class
  * or by name: a client-side tool registered as `web_search` carries no
  * marker and stays a client-side tool.
  */
@@ -238,8 +234,8 @@ export declare function isNativeToolMarker(value: unknown): value is NativeToolM
 export declare function isInstructionTool(value: unknown): value is InstructionTool;
 /**
  * Appended to a long-running tool's description, word for word what ADK's
- * LongRunningFunctionTool appends, so a model reads the same declaration on
- * either runtime.
+ * LongRunningFunctionTool appended, so a model reads the declaration it
+ * read before 1.0.0.
  */
 export declare const LONG_RUNNING_NOTE = "\n\nNOTE: This is a long-running operation. Do not call this tool again if it has already returned some intermediate or pending status.";
 /** True for a tool whose answer arrives later. */
@@ -247,8 +243,9 @@ export declare function isLongRunning(tool: Tool): boolean;
 /** True for anything shaped like a Tool (and not an ADK tool, which has runAsync). */
 export declare function isTool(value: unknown): value is Tool;
 /**
- * The texts ADK's FunctionTool gate writes, kept word for word so a call
- * gated on either runtime stores the same interrupt and the same response.
+ * The texts ADK's FunctionTool gate wrote, kept word for word so a call
+ * gated now stores the interrupt and the response a session written before
+ * 1.0.0 holds.
  */
 export declare const APPROVAL_TEXTS: {
     readonly hint: (name: string) => string;
@@ -318,7 +315,7 @@ export interface StandaloneToolContext extends ToolContext {
     };
 }
 /**
- * A ToolContext over plain data: for the native runtime, for a call made
+ * A ToolContext over plain data: for the native loop, for a call made
  * outside a run (MCP, a test), and for a caller that knows only who the call
  * is for. The runtime reads `stateDelta`, `actions` and `confirmationRequest`
  * back after the call.
@@ -333,22 +330,9 @@ export declare function isToolContext(value: unknown): value is ToolContext;
  */
 export declare function toToolContext(ctx?: Partial<ToolContext>): ToolContext;
 /**
- * Where lib/tools/adkTool.ts keeps the Tool an ADK tool was made from. A
- * global symbol, so a second copy of either module still finds it.
- */
-export declare const OWN_TOOL: unique symbol;
-/**
- * The Tool behind `value`: the value itself when it is a Tool, the Tool an
- * ADK tool was made from by toFunctionTool, else undefined: a server-side
- * tool, an InstructionTool, a local subagent's AgentTool, an OpenAPI or
- * skills tool. An ADK tool that was
- * gated afterwards (lib/compile.ts sets `requireConfirmation`) yields the
- * gated Tool, so the gate survives the trip back.
+ * The Tool `value` is, else undefined (a server-side tool and an
+ * InstructionTool are not Tools).
  */
 export declare function toolOf(value: unknown): Tool | undefined;
-/**
- * The InstructionTool behind `value`: the value itself, or the one an ADK
- * tool was made from by toAdkInstructionTool (lib/tools/adkTool.ts), else
- * undefined.
- */
+/** The InstructionTool `value` is, else undefined. */
 export declare function instructionToolOf(value: unknown): InstructionTool | undefined;