@agentic-kit/pi 0.17.0 → 0.18.0

package/README.md

@@ -12,13 +12,14 @@
    <a href="https://www.npmjs.com/package/@agentic-kit/pi"><img height="20" src="https://img.shields.io/github/package-json/v/constructive-io/constructive?filename=agentic%2Fpi%2Fpackage.json"/></a>
 </p>
 
-The **one** [pi coding agent](https://github.com/badlogic/pi-mono) adapter for **agentic-kit**: the Constructive typed database tools, and everything that attaches a platform run to a pi session — the run gate, the run log, the metering gateway and usage reporting — for any host to register: Constructive Desktop, the [`agent` CLI](https://www.npmjs.com/package/@agentic-kit/cli), or your own pi-based agent.
+The **one** [pi coding agent](https://github.com/badlogic/pi-mono) adapter for **agentic-kit**: everything that attaches a platform run to a pi session — the Constructive db tools bound to pi's tool shape, the run gate, the run log, the metering gateway and usage reporting — for any host to register: Constructive Desktop, the [`agent` CLI](https://www.npmjs.com/package/@agentic-kit/cli), or your own pi-based agent.
 
 What a run *does* is harness-neutral and lives elsewhere; only its attachment to pi lives here.
 
 ```
 neutral contracts                      this package                pi
 ────────────────────────────────────   ─────────────────────────   ────────────────────
+@agentic-kit/db-tools (18 db tools)    toPiTool ─► ToolDefinition pi.registerTool
 @agentic-kit/harness  (gate, adapter)  tool_call ─► RunGate       pi.on('tool_call')
 @agentic-kit/metering (gateway, usage) MeteredGateway ─► provider  pi.registerProvider
 @agentic-kit/run-log  (append-only)    SessionMirror              pi's session manager
@@ -32,7 +33,7 @@ npm install @agentic-kit/pi
 
 ## What's inside
 
-- **16 typed db tools** — `provision_database`, `provision_blueprint`, `describe_schema`, `add_relation`, `delete_table`, `create_field` / `update_field` / `delete_field`, `add_policies`, `add_records`, `run_codegen`, and the template suite (`list` / `create` / `apply` / `update` / `delete`). Tool schemas are authored in [zod](https://zod.dev) and emitted as plain JSON Schema at pi's tool boundary.
+- **The db tools, bound to pi** — the 18 typed Constructive tools live in [`@agentic-kit/db-tools`](https://www.npmjs.com/package/@agentic-kit/db-tools) as neutral `HarnessTool`s (zod parameters, `execute(params, { cwd, signal })`, no pi import); `toPiTool()` binds each one to pi's `ToolDefinition` — JSON Schema parameters, pi's execute arity, `ctx.cwd` forwarded — and `dbTools` registers the whole list plus the confirm gate. That conversion is the whole of what pi asks of a tool, so a sibling adapter writes its own `toXTool()` and registers the same tools unchanged. The tools' own surface (host contract, project context, provisioning) is re-exported here so a pi host keeps one import.
 - **Confirm gate** — the harness's host-neutral gate wired to pi's `tool_call` events. Hosts with a rich confirm surface (Desktop) expose `confirmTool`/`notifyToolSkipped` on `ctx.ui`; everyone else gets pi's built-in `ui.confirm` dialog.
 - **Run lanes** — `composeRun` / `startRun` build a pi session with the run's lanes attached: `createRunLogExtension` mirrors pi's session entries into the run log under `transcriptFormat: 'pi'`, `createMeteredModelExtension` points pi at the Constructive gateway so usage cannot be under-reported, `createUsageReportExtension` self-reports usage when the host owns the provider keys, and `createGateExtension` suspends a gated tool call until a human answers.
 - **`piHarness`** — the `HarnessAdapter` face of the above: an `id`, the `transcriptFormat` its entries are written under, and `startRun`.
@@ -90,7 +91,7 @@ For local development, the cold path and the warm pool depend on the backend's j
 
 ## Host contract
 
-`PiToolsHost` is the only integration surface:
+`ToolsHost` (from `@agentic-kit/db-tools`, re-exported here) is the only integration surface:
 
 | Member | Purpose |
 | --- | --- |
@@ -102,16 +103,13 @@ For local development, the cold path and the warm pool depend on the backend's j
 
 ## Related
 
+- [`@agentic-kit/db-tools`](https://www.npmjs.com/package/@agentic-kit/db-tools) — the Constructive db tools, harness-neutral
 - [`@agentic-kit/harness`](https://www.npmjs.com/package/@agentic-kit/harness) — host-neutral skills, gating, blueprint core, and the `HarnessAdapter` contract
 - [`@agentic-kit/metering`](https://www.npmjs.com/package/@agentic-kit/metering) — the metered gateway and usage reporting
 - [`@agentic-kit/run-log`](https://www.npmjs.com/package/@agentic-kit/run-log) — the append-only run log
 - [`@agentic-kit/cli`](https://www.npmjs.com/package/@agentic-kit/cli) — `agent`, a local secure-by-default coding agent
 - [`agentic-kit`](https://www.npmjs.com/package/agentic-kit) — the umbrella package
 
-## Credits
-
-Built on the excellent [pi coding agent](https://github.com/badlogic/pi-mono) by Mario Zechner.
-
 ---
 
 ## Education and Tutorials

package/confirm-gate.d.ts

@@ -1,7 +1,6 @@
+import type { createTemplatePreviewTables, resolveDataToken, resolveProjectContext } from '@agentic-kit/db-tools';
 import { type GatePolicy } from '@agentic-kit/harness';
 import type { ExtensionContext, ToolCallEvent, ToolCallEventResult } from '@earendil-works/pi-coding-agent';
-import type { resolveDataToken, resolveProjectContext } from './context';
-import type { createTemplatePreviewTables } from './tools/templates';
 export type ConfirmGateDeps = {
     resolveProjectContext: typeof resolveProjectContext;
     resolveDataToken: typeof resolveDataToken;

package/esm/confirm-gate.d.ts

@@ -1,7 +1,6 @@
+import type { createTemplatePreviewTables, resolveDataToken, resolveProjectContext } from '@agentic-kit/db-tools';
 import { type GatePolicy } from '@agentic-kit/harness';
 import type { ExtensionContext, ToolCallEvent, ToolCallEventResult } from '@earendil-works/pi-coding-agent';
-import type { resolveDataToken, resolveProjectContext } from './context';
-import type { createTemplatePreviewTables } from './tools/templates';
 export type ConfirmGateDeps = {
     resolveProjectContext: typeof resolveProjectContext;
     resolveDataToken: typeof resolveDataToken;

package/esm/host.d.ts

@@ -1,112 +1,7 @@
 /**
- * Host contract for the pi-hosted Constructive tools.
- *
- * The typed db tools were extracted from Constructive Desktop, where they read
- * an Electron-side `runtime` singleton (account store, backend config, data-auth
- * broker, preview token). Hosts now inject the same surface here once at
- * startup (`configureHost`); the tool modules stay module-level `ToolDefinition`
- * consts and read it lazily via `getHost()`.
+ * Deep-import compatibility: the host contract moved to
+ * `@agentic-kit/db-tools`, where it belongs — nothing about it is pi-specific.
+ * Hosts that import `@agentic-kit/pi/host` keep working; new code should
+ * import from `@agentic-kit/db-tools`.
  */
-export type HostAccount = {
-    userId: string;
-    accessToken: string;
-    apiKey?: string;
-};
-export type HostBackendConfig = {
-    apiEndpoint?: string;
-    modulesEndpoint?: string;
-};
-export type ActiveDataToken = {
-    token: string;
-    userId?: string;
-    expiresAt: number;
-    origin?: string;
-};
-/**
- * Optional data-plane token broker: remembers per-database end-user tokens
- * across tool calls and invalidates declined/expired ones. Hosts without a
- * broker fall back to the preview-token harvest on every call.
- */
-export interface DataAuthBroker {
-    getActiveToken(databaseId: string): ActiveDataToken | undefined | null;
-    isInvalidToken(databaseId: string, token: string): boolean;
-    adoptToken(databaseId: string, token: ActiveDataToken): void;
-}
-/** Token harvested from the host's app preview (end-user sign-in). */
-export type PreviewToken = {
-    accessToken: string;
-    accessTokenExpiresAt?: string;
-    userId?: string;
-};
-/**
- * Overlay layered over the pinned base preset when provisioning a database.
- * Structurally the `ProvisionOverlay` from `provision-database/resolve`; typed
- * loosely here to keep `host.ts` free of provision-internal imports.
- */
-export interface HostProvisionOverlay {
-    preset?: string;
-    add?: (string | [string, Record<string, unknown>])[];
-    remove?: string[];
-}
-/**
- * A minted secret handed to the host for out-of-band delivery (.env write +
- * one-time reveal). The plaintext never enters tool results or the transcript;
- * pi forgets it after this call.
- */
-export type SecretDelivery = {
-    databaseId: string;
-    /** Project directory whose `.env` receives the key. */
-    cwd: string;
-    envVar: string;
-    plaintext: string;
-    keyId: string;
-    expiresAt?: string;
-};
-/**
- * Context for a host-side step-up: enough to derive the per-database auth
- * endpoint and look up the app session without re-resolving the project.
- */
-export type StepUpRequest = {
-    databaseId: string;
-    databaseName: string;
-    apiEndpoint: string;
-};
-export interface PiToolsHost {
-    /** Signed-in platform account, or null/undefined when signed out. */
-    account(): HostAccount | null | undefined;
-    /** Host-configured backend endpoints (env-aware). */
-    backendConfig(): HostBackendConfig | null | undefined;
-    /** Optional data-plane token broker (see DataAuthBroker). */
-    dataAuthBroker?: DataAuthBroker;
-    /**
-     * Host-specific sign-in instruction, substituted into signed-out failure
-     * reasons (e.g. the CLI's "Run `agent login` to sign in."). Absent hosts get
-     * the desktop wording.
-     */
-    signInHint?: string;
-    /** Harvest an end-user token from the host's app preview, if it has one. */
-    previewToken?(): Promise<PreviewToken | null>;
-    /** Treat tokens expiring within this window as already expired. Default 30s. */
-    dataTokenSkewMs?: number;
-    /**
-     * Optional provision overlay: pick a base preset and/or layer module
-     * add/remove on top of it. The base module list always comes from the pinned
-     * `node-type-registry` preset — this only customizes it. Distributed as data
-     * (e.g. materialized from appstash / a pinned git ref), never as code.
-     */
-    provisionOverlay?(): HostProvisionOverlay | null | undefined | Promise<HostProvisionOverlay | null | undefined>;
-    /**
-     * Complete MFA step-up for the database's app session in the host's own
-     * process (password dialog + verifyPassword). The password never passes
-     * through pi or the model. Resolve true when step-up succeeded.
-     */
-    requestStepUp?(request: StepUpRequest): Promise<boolean>;
-    /**
-     * Deliver a minted secret to the user (.env write + one-time reveal).
-     * Required for create_api_key — without it the tool refuses to mint.
-     */
-    deliverSecret?(delivery: SecretDelivery): Promise<void>;
-}
-export declare const DEFAULT_DATA_TOKEN_SKEW_MS = 30000;
-export declare function configureHost(host: PiToolsHost): void;
-export declare function getHost(): PiToolsHost;
+export { type ActiveDataToken, configureHost, type DataAuthBroker, DEFAULT_DATA_TOKEN_SKEW_MS, getHost, type HostAccount, type HostBackendConfig, type HostProvisionOverlay, type PreviewToken, type SecretDelivery, type StepUpRequest, type ToolsHost, } from '@agentic-kit/db-tools';

package/esm/host.js

@@ -1,20 +1,7 @@
 /**
- * Host contract for the pi-hosted Constructive tools.
- *
- * The typed db tools were extracted from Constructive Desktop, where they read
- * an Electron-side `runtime` singleton (account store, backend config, data-auth
- * broker, preview token). Hosts now inject the same surface here once at
- * startup (`configureHost`); the tool modules stay module-level `ToolDefinition`
- * consts and read it lazily via `getHost()`.
+ * Deep-import compatibility: the host contract moved to
+ * `@agentic-kit/db-tools`, where it belongs — nothing about it is pi-specific.
+ * Hosts that import `@agentic-kit/pi/host` keep working; new code should
+ * import from `@agentic-kit/db-tools`.
  */
-export const DEFAULT_DATA_TOKEN_SKEW_MS = 30_000;
-let currentHost = null;
-export function configureHost(host) {
-    currentHost = host;
-}
-export function getHost() {
-    if (!currentHost) {
-        throw new Error('@agentic-kit/pi host not configured. Call configureHost() (or createDbTools(host)) before using the db tools.');
-    }
-    return currentHost;
-}
+export { configureHost, DEFAULT_DATA_TOKEN_SKEW_MS, getHost, } from '@agentic-kit/db-tools';

package/esm/index.d.ts

@@ -1,10 +1,17 @@
+import { type ToolsHost } from '@agentic-kit/db-tools';
 import type { ExtensionFactory } from '@earendil-works/pi-coding-agent';
-import { type PiToolsHost } from './host';
+/**
+ * The Constructive db tools bound to pi.
+ *
+ * The tools themselves live in `@agentic-kit/db-tools` and know nothing about
+ * pi; this is the binding — `toPiTool` per tool, plus the confirm gate on pi's
+ * `tool_call` event. A sibling adapter writes its own equivalent of this file
+ * and registers the same `constructiveDbTools`.
+ */
 export declare const dbTools: ExtensionFactory;
 /** Configure the host and get the extension in one call. */
-export declare function createDbTools(host: PiToolsHost): ExtensionFactory;
+export declare function createDbTools(host: ToolsHost): ExtensionFactory;
 export { type ConfirmGate, type ConfirmGateDeps, type ConfirmGateOptions, createConfirmGate, } from './confirm-gate';
-export { CONTEXT_ENV_KEYS, CONTEXT_ENV_PREFIX, type ContextEnvKey, type ContextSource, deriveSubdomainEndpoint, fromEnvFile, fromEnvironment, type ModulesClient, type ProjectContext, type ProjectContextFailureCode, resolveDataToken, resolveProjectContext, } from './context';
 export { type ComposedLanes, type ComposedRun, composeRun, type ComposeRunOptions, type GateLane, type MeteringLane, type RunLogLane, } from './embed/lanes';
 export { type CreateResourceLoader, type EmbeddedRun, type PiModule, type ResourceLoaderRequest, startRun, type StartRunOptions, } from './embed/session';
 export { createGateExtension, type GateExtension, type GateExtensionOptions, } from './extensions/gate';
@@ -12,10 +19,11 @@ export { createMeteredModelExtension, type MeteredModelExtension, type MeteredMo
 export { createRunLogExtension, MIRROR_EVENTS, type MirrorEvent, type RunLogExtension, type RunLogExtensionOptions, } from './extensions/run-log';
 export { createUsageReportExtension, type UsageReportExtension, type UsageReportExtensionOptions, } from './extensions/usage-report';
 export { PI_HARNESS_ID, piHarness, type PiHarnessRun } from './harness';
-export { type ActiveDataToken, configureHost, type DataAuthBroker, getHost, type HostAccount, type HostBackendConfig, type HostProvisionOverlay, type PiToolsHost, type PreviewToken, } from './host';
-export { loadProvisionManifest, parseProvisionManifest, PROVISION_MANIFEST_FILE, type ProvisionManifest, } from './provision-database/manifest';
-export { allModulePresets, DEFAULT_PROVISION_PRESET, getModulePreset, type ModulePreset, type ProvisionModule, } from './provision-database/presets';
-export { moduleKey, type ProvisionOverlay, resolveProvisionModules, } from './provision-database/resolve';
-export { toolSchema } from './tool-schema';
-export { createTemplatePreviewTables } from './tools/templates';
+export { toPiTool, toPiTools } from './pi-tool';
+/**
+ * The db tools' own surface, re-exported so a pi host keeps one import. The
+ * package to depend on directly is `@agentic-kit/db-tools`.
+ */
+export { type ActiveDataToken, configureHost, constructiveDbTools, CONTEXT_ENV_KEYS, CONTEXT_ENV_PREFIX, type ContextEnvKey, type ContextSource, createTemplatePreviewTables, type DataAuthBroker, DEFAULT_PROVISION_PRESET, deriveSubdomainEndpoint, fromEnvFile, fromEnvironment, getHost, type HostAccount, type HostBackendConfig, type HostProvisionOverlay, loadProvisionManifest, moduleKey, type ModulePreset, type ModulesClient, parseProvisionManifest, type PreviewToken, type ProjectContext, type ProjectContextFailureCode, PROVISION_MANIFEST_FILE, type ProvisionManifest, type ProvisionModule, type ProvisionOverlay, resolveDataToken, resolveProjectContext, resolveProvisionModules, type SecretDelivery, type StepUpRequest, toolSchema, type ToolsHost, } from '@agentic-kit/db-tools';
+export { allModulePresets, getModulePreset } from '@agentic-kit/db-tools';
 export default dbTools;

package/esm/index.js

@@ -1,36 +1,18 @@
+import { configureHost, constructiveDbTools, createTemplatePreviewTables, resolveDataToken, resolveProjectContext, } from '@agentic-kit/db-tools';
 import { createConfirmGate } from './confirm-gate';
-import { resolveDataToken, resolveProjectContext } from './context';
-import { configureHost } from './host';
-import { addPoliciesTool } from './tools/add-policies';
-import { addRecordsTool } from './tools/add-records';
-import { addRelationTool } from './tools/add-relation';
-import { createApiKeyTool } from './tools/create-api-key';
-import { describeSchemaTool } from './tools/describe-schema';
-import { manageEntityTypesTool } from './tools/manage-entity-types';
-import { createFieldTool, deleteFieldTool, deleteTableTool, updateFieldTool } from './tools/mutations';
-import { provisionBlueprintTool } from './tools/provision-blueprint';
-import { provisionDatabaseTool } from './tools/provision-database';
-import { runCodegenTool } from './tools/run-codegen';
-import { applyTemplateTool, createTemplatePreviewTables, createTemplateTool, deleteTemplateTool, listTemplatesTool, updateTemplateTool, } from './tools/templates';
+import { toPiTool } from './pi-tool';
+/**
+ * The Constructive db tools bound to pi.
+ *
+ * The tools themselves live in `@agentic-kit/db-tools` and know nothing about
+ * pi; this is the binding — `toPiTool` per tool, plus the confirm gate on pi's
+ * `tool_call` event. A sibling adapter writes its own equivalent of this file
+ * and registers the same `constructiveDbTools`.
+ */
 export const dbTools = (pi) => {
-    pi.registerTool(provisionDatabaseTool);
-    pi.registerTool(describeSchemaTool);
-    pi.registerTool(listTemplatesTool);
-    pi.registerTool(provisionBlueprintTool);
-    pi.registerTool(addRelationTool);
-    pi.registerTool(deleteTableTool);
-    pi.registerTool(createFieldTool);
-    pi.registerTool(updateFieldTool);
-    pi.registerTool(deleteFieldTool);
-    pi.registerTool(addPoliciesTool);
-    pi.registerTool(applyTemplateTool);
-    pi.registerTool(createTemplateTool);
-    pi.registerTool(updateTemplateTool);
-    pi.registerTool(deleteTemplateTool);
-    pi.registerTool(addRecordsTool);
-    pi.registerTool(manageEntityTypesTool);
-    pi.registerTool(createApiKeyTool);
-    pi.registerTool(runCodegenTool);
+    for (const tool of constructiveDbTools) {
+        pi.registerTool(toPiTool(tool));
+    }
     const gate = createConfirmGate({
         resolveProjectContext,
         resolveDataToken,
@@ -45,7 +27,6 @@ export function createDbTools(host) {
     return dbTools;
 }
 export { createConfirmGate, } from './confirm-gate';
-export { CONTEXT_ENV_KEYS, CONTEXT_ENV_PREFIX, deriveSubdomainEndpoint, fromEnvFile, fromEnvironment, resolveDataToken, resolveProjectContext, } from './context';
 export { composeRun, } from './embed/lanes';
 export { startRun, } from './embed/session';
 export { createGateExtension, } from './extensions/gate';
@@ -53,10 +34,11 @@ export { createMeteredModelExtension, piProviderConfig, } from './extensions/met
 export { createRunLogExtension, MIRROR_EVENTS, } from './extensions/run-log';
 export { createUsageReportExtension, } from './extensions/usage-report';
 export { PI_HARNESS_ID, piHarness } from './harness';
-export { configureHost, getHost, } from './host';
-export { loadProvisionManifest, parseProvisionManifest, PROVISION_MANIFEST_FILE, } from './provision-database/manifest';
-export { allModulePresets, DEFAULT_PROVISION_PRESET, getModulePreset, } from './provision-database/presets';
-export { moduleKey, resolveProvisionModules, } from './provision-database/resolve';
-export { toolSchema } from './tool-schema';
-export { createTemplatePreviewTables } from './tools/templates';
+export { toPiTool, toPiTools } from './pi-tool';
+/**
+ * The db tools' own surface, re-exported so a pi host keeps one import. The
+ * package to depend on directly is `@agentic-kit/db-tools`.
+ */
+export { configureHost, constructiveDbTools, CONTEXT_ENV_KEYS, CONTEXT_ENV_PREFIX, createTemplatePreviewTables, DEFAULT_PROVISION_PRESET, deriveSubdomainEndpoint, fromEnvFile, fromEnvironment, getHost, loadProvisionManifest, moduleKey, parseProvisionManifest, PROVISION_MANIFEST_FILE, resolveDataToken, resolveProjectContext, resolveProvisionModules, toolSchema, } from '@agentic-kit/db-tools';
+export { allModulePresets, getModulePreset } from '@agentic-kit/db-tools';
 export default dbTools;

package/esm/pi-tool.d.ts

@@ -0,0 +1,16 @@
+import type { AnyHarnessTool, HarnessTool } from '@agentic-kit/harness';
+import type { ToolDefinition } from '@earendil-works/pi-coding-agent';
+import type { z } from 'zod';
+/**
+ * Bind a neutral `HarnessTool` to pi's `ToolDefinition`.
+ *
+ * This is the whole of what pi wants that a tool does not state: parameters as
+ * a typebox schema rather than zod, and an execute arity carrying pi's tool
+ * call id, update callback and `ExtensionContext`. Everything a Constructive
+ * tool actually reads out of that context is `cwd` and the abort signal, so
+ * that is all this forwards — the rest stops here, which is the point of the
+ * seam: another harness writes its own binding and the tools do not change.
+ */
+export declare function toPiTool<TParams extends z.ZodType, TDetails>(tool: HarnessTool<TParams, TDetails>): ToolDefinition<any, TDetails>;
+/** Bind a whole tool set, in registration order. */
+export declare function toPiTools(tools: readonly AnyHarnessTool[]): ToolDefinition<any, any>[];

package/esm/pi-tool.js

@@ -0,0 +1,32 @@
+import { toolSchema } from '@agentic-kit/db-tools';
+/**
+ * Bind a neutral `HarnessTool` to pi's `ToolDefinition`.
+ *
+ * This is the whole of what pi wants that a tool does not state: parameters as
+ * a typebox schema rather than zod, and an execute arity carrying pi's tool
+ * call id, update callback and `ExtensionContext`. Everything a Constructive
+ * tool actually reads out of that context is `cwd` and the abort signal, so
+ * that is all this forwards — the rest stops here, which is the point of the
+ * seam: another harness writes its own binding and the tools do not change.
+ */
+export function toPiTool(tool) {
+    return {
+        name: tool.name,
+        label: tool.label,
+        description: tool.description,
+        ...(tool.promptSnippet === undefined ? {} : { promptSnippet: tool.promptSnippet }),
+        ...(tool.promptGuidelines === undefined ? {} : { promptGuidelines: tool.promptGuidelines }),
+        parameters: toolSchema(tool.parameters),
+        async execute(_toolCallId, params, signal, _onUpdate, ctx) {
+            const result = await tool.execute(params, {
+                cwd: ctx.cwd,
+                signal,
+            });
+            return result;
+        },
+    };
+}
+/** Bind a whole tool set, in registration order. */
+export function toPiTools(tools) {
+    return tools.map((tool) => toPiTool(tool));
+}

package/host.d.ts

@@ -1,112 +1,7 @@
 /**
- * Host contract for the pi-hosted Constructive tools.
- *
- * The typed db tools were extracted from Constructive Desktop, where they read
- * an Electron-side `runtime` singleton (account store, backend config, data-auth
- * broker, preview token). Hosts now inject the same surface here once at
- * startup (`configureHost`); the tool modules stay module-level `ToolDefinition`
- * consts and read it lazily via `getHost()`.
+ * Deep-import compatibility: the host contract moved to
+ * `@agentic-kit/db-tools`, where it belongs — nothing about it is pi-specific.
+ * Hosts that import `@agentic-kit/pi/host` keep working; new code should
+ * import from `@agentic-kit/db-tools`.
  */
-export type HostAccount = {
-    userId: string;
-    accessToken: string;
-    apiKey?: string;
-};
-export type HostBackendConfig = {
-    apiEndpoint?: string;
-    modulesEndpoint?: string;
-};
-export type ActiveDataToken = {
-    token: string;
-    userId?: string;
-    expiresAt: number;
-    origin?: string;
-};
-/**
- * Optional data-plane token broker: remembers per-database end-user tokens
- * across tool calls and invalidates declined/expired ones. Hosts without a
- * broker fall back to the preview-token harvest on every call.
- */
-export interface DataAuthBroker {
-    getActiveToken(databaseId: string): ActiveDataToken | undefined | null;
-    isInvalidToken(databaseId: string, token: string): boolean;
-    adoptToken(databaseId: string, token: ActiveDataToken): void;
-}
-/** Token harvested from the host's app preview (end-user sign-in). */
-export type PreviewToken = {
-    accessToken: string;
-    accessTokenExpiresAt?: string;
-    userId?: string;
-};
-/**
- * Overlay layered over the pinned base preset when provisioning a database.
- * Structurally the `ProvisionOverlay` from `provision-database/resolve`; typed
- * loosely here to keep `host.ts` free of provision-internal imports.
- */
-export interface HostProvisionOverlay {
-    preset?: string;
-    add?: (string | [string, Record<string, unknown>])[];
-    remove?: string[];
-}
-/**
- * A minted secret handed to the host for out-of-band delivery (.env write +
- * one-time reveal). The plaintext never enters tool results or the transcript;
- * pi forgets it after this call.
- */
-export type SecretDelivery = {
-    databaseId: string;
-    /** Project directory whose `.env` receives the key. */
-    cwd: string;
-    envVar: string;
-    plaintext: string;
-    keyId: string;
-    expiresAt?: string;
-};
-/**
- * Context for a host-side step-up: enough to derive the per-database auth
- * endpoint and look up the app session without re-resolving the project.
- */
-export type StepUpRequest = {
-    databaseId: string;
-    databaseName: string;
-    apiEndpoint: string;
-};
-export interface PiToolsHost {
-    /** Signed-in platform account, or null/undefined when signed out. */
-    account(): HostAccount | null | undefined;
-    /** Host-configured backend endpoints (env-aware). */
-    backendConfig(): HostBackendConfig | null | undefined;
-    /** Optional data-plane token broker (see DataAuthBroker). */
-    dataAuthBroker?: DataAuthBroker;
-    /**
-     * Host-specific sign-in instruction, substituted into signed-out failure
-     * reasons (e.g. the CLI's "Run `agent login` to sign in."). Absent hosts get
-     * the desktop wording.
-     */
-    signInHint?: string;
-    /** Harvest an end-user token from the host's app preview, if it has one. */
-    previewToken?(): Promise<PreviewToken | null>;
-    /** Treat tokens expiring within this window as already expired. Default 30s. */
-    dataTokenSkewMs?: number;
-    /**
-     * Optional provision overlay: pick a base preset and/or layer module
-     * add/remove on top of it. The base module list always comes from the pinned
-     * `node-type-registry` preset — this only customizes it. Distributed as data
-     * (e.g. materialized from appstash / a pinned git ref), never as code.
-     */
-    provisionOverlay?(): HostProvisionOverlay | null | undefined | Promise<HostProvisionOverlay | null | undefined>;
-    /**
-     * Complete MFA step-up for the database's app session in the host's own
-     * process (password dialog + verifyPassword). The password never passes
-     * through pi or the model. Resolve true when step-up succeeded.
-     */
-    requestStepUp?(request: StepUpRequest): Promise<boolean>;
-    /**
-     * Deliver a minted secret to the user (.env write + one-time reveal).
-     * Required for create_api_key — without it the tool refuses to mint.
-     */
-    deliverSecret?(delivery: SecretDelivery): Promise<void>;
-}
-export declare const DEFAULT_DATA_TOKEN_SKEW_MS = 30000;
-export declare function configureHost(host: PiToolsHost): void;
-export declare function getHost(): PiToolsHost;
+export { type ActiveDataToken, configureHost, type DataAuthBroker, DEFAULT_DATA_TOKEN_SKEW_MS, getHost, type HostAccount, type HostBackendConfig, type HostProvisionOverlay, type PreviewToken, type SecretDelivery, type StepUpRequest, type ToolsHost, } from '@agentic-kit/db-tools';

package/host.js

@@ -1,25 +1,13 @@
 "use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.getHost = exports.DEFAULT_DATA_TOKEN_SKEW_MS = exports.configureHost = void 0;
 /**
- * Host contract for the pi-hosted Constructive tools.
- *
- * The typed db tools were extracted from Constructive Desktop, where they read
- * an Electron-side `runtime` singleton (account store, backend config, data-auth
- * broker, preview token). Hosts now inject the same surface here once at
- * startup (`configureHost`); the tool modules stay module-level `ToolDefinition`
- * consts and read it lazily via `getHost()`.
+ * Deep-import compatibility: the host contract moved to
+ * `@agentic-kit/db-tools`, where it belongs — nothing about it is pi-specific.
+ * Hosts that import `@agentic-kit/pi/host` keep working; new code should
+ * import from `@agentic-kit/db-tools`.
  */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.DEFAULT_DATA_TOKEN_SKEW_MS = void 0;
-exports.configureHost = configureHost;
-exports.getHost = getHost;
-exports.DEFAULT_DATA_TOKEN_SKEW_MS = 30_000;
-let currentHost = null;
-function configureHost(host) {
-    currentHost = host;
-}
-function getHost() {
-    if (!currentHost) {
-        throw new Error('@agentic-kit/pi host not configured. Call configureHost() (or createDbTools(host)) before using the db tools.');
-    }
-    return currentHost;
-}
+var db_tools_1 = require("@agentic-kit/db-tools");
+Object.defineProperty(exports, "configureHost", { enumerable: true, get: function () { return db_tools_1.configureHost; } });
+Object.defineProperty(exports, "DEFAULT_DATA_TOKEN_SKEW_MS", { enumerable: true, get: function () { return db_tools_1.DEFAULT_DATA_TOKEN_SKEW_MS; } });
+Object.defineProperty(exports, "getHost", { enumerable: true, get: function () { return db_tools_1.getHost; } });

package/index.d.ts

@@ -1,10 +1,17 @@
+import { type ToolsHost } from '@agentic-kit/db-tools';
 import type { ExtensionFactory } from '@earendil-works/pi-coding-agent';
-import { type PiToolsHost } from './host';
+/**
+ * The Constructive db tools bound to pi.
+ *
+ * The tools themselves live in `@agentic-kit/db-tools` and know nothing about
+ * pi; this is the binding — `toPiTool` per tool, plus the confirm gate on pi's
+ * `tool_call` event. A sibling adapter writes its own equivalent of this file
+ * and registers the same `constructiveDbTools`.
+ */
 export declare const dbTools: ExtensionFactory;
 /** Configure the host and get the extension in one call. */
-export declare function createDbTools(host: PiToolsHost): ExtensionFactory;
+export declare function createDbTools(host: ToolsHost): ExtensionFactory;
 export { type ConfirmGate, type ConfirmGateDeps, type ConfirmGateOptions, createConfirmGate, } from './confirm-gate';
-export { CONTEXT_ENV_KEYS, CONTEXT_ENV_PREFIX, type ContextEnvKey, type ContextSource, deriveSubdomainEndpoint, fromEnvFile, fromEnvironment, type ModulesClient, type ProjectContext, type ProjectContextFailureCode, resolveDataToken, resolveProjectContext, } from './context';
 export { type ComposedLanes, type ComposedRun, composeRun, type ComposeRunOptions, type GateLane, type MeteringLane, type RunLogLane, } from './embed/lanes';
 export { type CreateResourceLoader, type EmbeddedRun, type PiModule, type ResourceLoaderRequest, startRun, type StartRunOptions, } from './embed/session';
 export { createGateExtension, type GateExtension, type GateExtensionOptions, } from './extensions/gate';
@@ -12,10 +19,11 @@ export { createMeteredModelExtension, type MeteredModelExtension, type MeteredMo
 export { createRunLogExtension, MIRROR_EVENTS, type MirrorEvent, type RunLogExtension, type RunLogExtensionOptions, } from './extensions/run-log';
 export { createUsageReportExtension, type UsageReportExtension, type UsageReportExtensionOptions, } from './extensions/usage-report';
 export { PI_HARNESS_ID, piHarness, type PiHarnessRun } from './harness';
-export { type ActiveDataToken, configureHost, type DataAuthBroker, getHost, type HostAccount, type HostBackendConfig, type HostProvisionOverlay, type PiToolsHost, type PreviewToken, } from './host';
-export { loadProvisionManifest, parseProvisionManifest, PROVISION_MANIFEST_FILE, type ProvisionManifest, } from './provision-database/manifest';
-export { allModulePresets, DEFAULT_PROVISION_PRESET, getModulePreset, type ModulePreset, type ProvisionModule, } from './provision-database/presets';
-export { moduleKey, type ProvisionOverlay, resolveProvisionModules, } from './provision-database/resolve';
-export { toolSchema } from './tool-schema';
-export { createTemplatePreviewTables } from './tools/templates';
+export { toPiTool, toPiTools } from './pi-tool';
+/**
+ * The db tools' own surface, re-exported so a pi host keeps one import. The
+ * package to depend on directly is `@agentic-kit/db-tools`.
+ */
+export { type ActiveDataToken, configureHost, constructiveDbTools, CONTEXT_ENV_KEYS, CONTEXT_ENV_PREFIX, type ContextEnvKey, type ContextSource, createTemplatePreviewTables, type DataAuthBroker, DEFAULT_PROVISION_PRESET, deriveSubdomainEndpoint, fromEnvFile, fromEnvironment, getHost, type HostAccount, type HostBackendConfig, type HostProvisionOverlay, loadProvisionManifest, moduleKey, type ModulePreset, type ModulesClient, parseProvisionManifest, type PreviewToken, type ProjectContext, type ProjectContextFailureCode, PROVISION_MANIFEST_FILE, type ProvisionManifest, type ProvisionModule, type ProvisionOverlay, resolveDataToken, resolveProjectContext, resolveProvisionModules, type SecretDelivery, type StepUpRequest, toolSchema, type ToolsHost, } from '@agentic-kit/db-tools';
+export { allModulePresets, getModulePreset } from '@agentic-kit/db-tools';
 export default dbTools;