@agentproto/adapter-mastra-agent 0.5.5 → 0.7.0

package/dist/cli.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { runAcpOverStdio, makeAgentFactory } from './chunk-6ILIPWNM.mjs';
+import { runAcpOverStdio, makeAgentFactory } from './chunk-2FKFITFT.mjs';
 
 /**
  * @agentproto/adapter-mastra-agent v0.1.0-alpha

package/dist/index.d.ts

@@ -2,6 +2,7 @@ import { AgentCliHandle, AgentCliRuntime } from '@agentproto/driver-agent-cli';
 export { AgentCliHandle, AgentCliRuntime } from '@agentproto/driver-agent-cli';
 import { MastraToolLike } from '@agentproto/mastra';
 import { BuiltinToolId, AgentController, PermissionRules, AgentControllerEvent } from '@mastra/core/agent-controller';
+import { Client } from '@modelcontextprotocol/sdk/client/index.js';
 import { Agent, AgentSideConnection, InitializeRequest, InitializeResponse, AuthenticateRequest, NewSessionRequest, NewSessionResponse, LoadSessionRequest, LoadSessionResponse, PromptRequest, PromptResponse, CancelNotification, SetSessionConfigOptionRequest, SetSessionConfigOptionResponse, SetSessionModeRequest, SessionUpdate, ToolKind } from '@agentclientprotocol/sdk';
 import { LanguageModelV3 } from '@ai-sdk/provider';
 import { ModelRef, MemoryConfig } from '@agentproto/agent';
@@ -9,6 +10,184 @@ import { createTool } from '@mastra/core/tools';
 import { LibSQLStore } from '@mastra/libsql';
 import { Memory } from '@mastra/memory';
 
+/**
+ * Zero-dependency HTTP client for the agentproto daemon.
+ *
+ * The adapter is spawned as an ACP child with `AGENTPROTO_SESSION_ID` /
+ * `AGENTPROTO_PARENT_SESSION_ID` in its env, but no daemon URL/token — unlike
+ * the CLI (`packages/cli/src/commands/_daemon-helpers.ts`, read as reference),
+ * this package cannot import `@agentproto/runtime` or `@agentproto/cli`
+ * (would pull the whole daemon runtime into an agent process). So this is a
+ * deliberately smaller reimplementation of that discovery order:
+ *
+ *   1. `AGENTPROTO_DAEMON_URL` env (+ optional `AGENTPROTO_DAEMON_TOKEN`)
+ *   2. `<cwd>/.agentproto/runtime.json`
+ *   3. `~/.agentproto/runtime.json`
+ *   4. central registry `~/.agentproto/daemons/*.json`, newest-mtime-first
+ *
+ * Unlike the CLI helper, this skips the `workspaces.json` walk (needs
+ * `@agentproto/runtime`'s config loader) and the declared-port preference
+ * in the central registry (needs `loadConfig()`). Good enough for an agent
+ * process discovering the daemon that spawned it or one on the same host.
+ *
+ * A runtime.json / registry entry whose `pid` is dead (`process.kill(pid, 0)`
+ * throwing anything but `EPERM`) is never trusted — same footgun the CLI
+ * helper guards against (a crashed daemon's stale token 401ing a fresh one
+ * on the same port).
+ */
+interface DaemonEndpoint {
+    url: string;
+    token?: string;
+    /** Path of the runtime.json / registry file the endpoint came from.
+     *  Undefined when the endpoint came from env vars. */
+    sourcePath?: string;
+}
+/** Thrown when no daemon endpoint can be discovered. */
+declare class DaemonNotFoundError extends Error {
+    constructor(message?: string);
+}
+/** Thrown on a non-2xx daemon HTTP response. */
+declare class DaemonHttpError extends Error {
+    readonly status: number;
+    readonly body: string;
+    constructor(message: string, status: number, body: string);
+}
+interface DiscoverDaemonOptions {
+    cwd?: string;
+    env?: NodeJS.ProcessEnv;
+    /** Override `homedir()` for BOTH `~/.agentproto/runtime.json` and the
+     *  central registry dir (unless `registryDir` also overrides the latter
+     *  separately) — test hook, so discovery never has to touch a real
+     *  developer machine's `~/.agentproto`. */
+    homeDir?: string;
+    /** Override the central registry directory — test hook. Wins over `homeDir`. */
+    registryDir?: string;
+    /** Override the liveness check for a runtime.json / registry entry's
+     *  `pid` — test hook. Defaults to a real `process.kill(pid, 0)` probe. */
+    isPidAlive?: (pid: number) => boolean;
+}
+/**
+ * Resolve the first live daemon endpoint, in the order documented above.
+ * Returns undefined when nothing live is found.
+ */
+declare function discoverDaemonEndpoint(opts?: DiscoverDaemonOptions): Promise<DaemonEndpoint | undefined>;
+interface StartAgentInput {
+    adapter: string;
+    cwd?: string;
+    model?: string;
+    prompt?: string;
+    label?: string;
+}
+interface PromptAgentOptions {
+    /** Cancel the in-flight turn and deliver this prompt instead. Default false. */
+    interrupt?: boolean;
+    /** `false` returns as soon as the prompt is queued/validated, without
+     *  waiting for the turn to drain. Default true (blocking). */
+    wait?: boolean;
+}
+interface ListSessionsOptions {
+    includeArchived?: boolean;
+    kind?: string;
+}
+interface ReadOutputOptions {
+    format?: "markdown" | "json";
+}
+interface PollEventsOptions {
+    /** Cursor from a prior call's `nextSeq`. Omit to start from the beginning. */
+    since?: number;
+    /** Client-side filter on each record's `kind` field. Omit → all kinds. */
+    types?: string[];
+    limit?: number;
+}
+interface PollEventsResult {
+    sessionId: string;
+    events: Array<Record<string, unknown>>;
+    nextSeq: number;
+    complete: boolean;
+}
+interface DaemonClientOptions {
+    cwd?: string;
+    env?: NodeJS.ProcessEnv;
+    /** Injectable fetch — test hook. Defaults to the global `fetch`. */
+    fetchImpl?: typeof fetch;
+    /** Pre-resolved endpoint — skips discovery, mainly a test hook. */
+    endpoint?: DaemonEndpoint;
+    /** Test hooks forwarded to {@link discoverDaemonEndpoint}. */
+    homeDir?: string;
+    registryDir?: string;
+    isPidAlive?: (pid: number) => boolean;
+}
+/**
+ * Thin HTTP client over the daemon's REST surface (`packages/runtime/src/http-server.ts`,
+ * read-only reference — this package never imports it). Discovers the daemon
+ * endpoint lazily on first call and caches it; a connection failure triggers
+ * one re-discovery attempt (covers a daemon restart on the same well-known
+ * runtime.json / registry path but a new port/token).
+ */
+declare class DaemonClient {
+    private readonly cwd;
+    private readonly env;
+    private readonly fetchImpl;
+    private readonly homeDir;
+    private readonly registryDir;
+    private readonly isPidAlive;
+    private cachedEndpoint;
+    constructor(opts?: DaemonClientOptions);
+    private resolveEndpoint;
+    private request;
+    /**
+     * Spawn a child session — `POST /sessions/agent`. `parentSessionId` is
+     * derived from `AGENTPROTO_SESSION_ID` (set by the daemon on every
+     * ACP-spawned adapter) when present, so session lineage is recorded
+     * without the caller having to thread it through.
+     */
+    startAgent(input: StartAgentInput): Promise<Record<string, unknown>>;
+    /** Send a follow-up turn to a live session — `POST /sessions/:id/prompt`. */
+    promptAgent(sessionId: string, text: string, opts?: PromptAgentOptions): Promise<Record<string, unknown>>;
+    /** List sessions — `GET /sessions`. */
+    listSessions(opts?: ListSessionsOptions): Promise<{
+        sessions: Array<Record<string, unknown>>;
+    }>;
+    /**
+     * Read a session's transcript — `GET /sessions/:id/export`. Chosen over
+     * `/sessions/:id/conversation` (needs a provider-native store registered
+     * for the adapter; not every adapter has one) and `/sessions/:id/preview`
+     * (a raw ring-buffer snapshot, not a rendered transcript): `/export`
+     * works for ANY agent-cli session, falling back to the daemon's own
+     * `events.jsonl` capture when no provider-native reader is registered
+     * (`source: "auto"`, see `transcript-export.ts`) — the one built for
+     * programmatic reads of "what did this session say".
+     */
+    readOutput(sessionId: string, opts?: ReadOutputOptions): Promise<Record<string, unknown>>;
+    /**
+     * Cursor-based poll of a session's structured event log —
+     * `GET /sessions/:id/events`. NOT the same event source as the MCP
+     * `session_events_poll` tool: that tool reads the daemon's in-memory,
+     * cross-session `EventRing` (turn-end/awaiting-input/exited/... lifecycle
+     * events, `packages/runtime/src/orchestration-tools.ts:528`), which has no
+     * plain-HTTP equivalent — it's only reachable over the MCP JSON-RPC
+     * transport, which this zero-dependency client doesn't speak. This route
+     * is the per-SESSION structured `events.jsonl` transcript instead
+     * (`packages/runtime/src/transcript-writer.ts`): cursor-based via
+     * `since`/`nextSeq` same as the MCP tool, and its records DO carry many of
+     * the same `kind`s (`turn-end`, `error`, `permission-resolved`, ...) — but
+     * it has no `exited` / `session:spawned` records (those are registry
+     * state changes, not transcript writes) and no cross-session fan-in
+     * (`sessionIds` filter). `types` is therefore filtered client-side here
+     * against each record's `kind`, not sent as a query param.
+     *
+     * WP-6 (`AgentprotoSignalProvider`, polling every 5s): this is a
+     * non-blocking snapshot read, so it's a direct fit for a poll loop. If
+     * WP-6 needs the actual cross-session lifecycle events (`exited`,
+     * `session:spawned`, multi-session fan-in), it either needs its own
+     * light MCP JSON-RPC client to call `session_events_poll` directly, or
+     * per-session `GET /sessions/:id/wait?since=&event=` (a blocking
+     * long-poll over the SAME EventRing `session_events_poll` reads, but
+     * scoped to one session and one event name at a time — no `types` array).
+     */
+    pollEvents(sessionId: string, opts?: PollEventsOptions): Promise<PollEventsResult>;
+}
+
 /**
  * Builds a runnable Mastra `AgentController` from an AIP-42 AGENT.md — either
  * a caller's file or a zero-config built-in default — wiring the model, the
@@ -47,6 +226,31 @@ interface AgentSourceOptions {
      * — see this WP's report).
      */
     modes?: false | "default";
+    /** Auto-injected into `app_*` daemon tool calls that omit `appId` (see
+     *  `daemon-mcp-tools.ts`'s `injectAppId`). Defaults to
+     *  `AGENTPROTO_APP_ID` — an explicit value here is mainly a test hook. */
+    appId?: string;
+    /**
+     * Exact absolute paths OUTSIDE `cwd` the read-only workspace tools may
+     * also read — the daemon's AGENTS.md pointer contract grant. Defaults to
+     * parsing `AGENTPROTO_ADDITIONAL_READ_PATHS` (a JSON array, set by the
+     * driver when the spawn carries the grant); malformed values are ignored
+     * (the grant is advisory — a bad payload must never break a spawn) and an
+     * explicit value here is mainly a test hook. See
+     * `WorkspaceToolsOptions.additionalReadPaths`.
+     */
+    additionalReadPaths?: string[];
+    /** Test hook: skip discovering + connecting to a real daemon MCP endpoint.
+     *  `client` injects an already-connected client outright (e.g. one wired
+     *  to an in-memory fake server); `discoverOptions` isolates
+     *  `discoverDaemonEndpoint` (homeDir/registryDir/env) from a real
+     *  developer machine's `~/.agentproto` without faking a whole client.
+     *  Neither set ⇒ production behaviour (real discovery + connect, lazily,
+     *  only if an AGENT.md ref needs it). */
+    daemonMcp?: {
+        client?: Client;
+        discoverOptions?: DiscoverDaemonOptions;
+    };
 }
 /** The built-in AGENT.md used when no file is supplied. */
 declare function defaultAgentManifest(model: string): string;
@@ -318,6 +522,18 @@ interface WorkspaceToolsOptions {
     allowExec?: boolean;
     /** Per-tool execution timeout (ms), enforced on every tool by `withTimeoutGuard`. Default 120_000. */
     execTimeoutMs?: number;
+    /**
+     * Exact absolute paths OUTSIDE `cwd` the READ-ONLY tools (`read_file`,
+     * `file_read`, `file_info`) may additionally access. The daemon hands down
+     * the AGENTS.md file an inherited pointer prompt names
+     * (`AGENTPROTO_ADDITIONAL_READ_PATHS`, see `session-spawn.ts`) so the
+     * agent can actually read the contract it was told to load first.
+     * Deliberately narrow: exact files only (no parent-dir listing), the
+     * write tools (`write_file`, `edit_file`, …) never honour the grant, and
+     * sibling paths stay rejected — `escapes the workspace` still throws for
+     * everything else.
+     */
+    additionalReadPaths?: string[];
     /**
      * Extra tools merged over the built-ins, keyed by id — lets an embedding
      * host add tools the built-in toolset doesn't cover. On id collision, an
@@ -333,184 +549,6 @@ declare function resolveInCwd(cwd: string, p: string): string;
  */
 declare function makeWorkspaceTools(opts: WorkspaceToolsOptions): Record<string, ReturnType<typeof createTool>>;
 
-/**
- * Zero-dependency HTTP client for the agentproto daemon.
- *
- * The adapter is spawned as an ACP child with `AGENTPROTO_SESSION_ID` /
- * `AGENTPROTO_PARENT_SESSION_ID` in its env, but no daemon URL/token — unlike
- * the CLI (`packages/cli/src/commands/_daemon-helpers.ts`, read as reference),
- * this package cannot import `@agentproto/runtime` or `@agentproto/cli`
- * (would pull the whole daemon runtime into an agent process). So this is a
- * deliberately smaller reimplementation of that discovery order:
- *
- *   1. `AGENTPROTO_DAEMON_URL` env (+ optional `AGENTPROTO_DAEMON_TOKEN`)
- *   2. `<cwd>/.agentproto/runtime.json`
- *   3. `~/.agentproto/runtime.json`
- *   4. central registry `~/.agentproto/daemons/*.json`, newest-mtime-first
- *
- * Unlike the CLI helper, this skips the `workspaces.json` walk (needs
- * `@agentproto/runtime`'s config loader) and the declared-port preference
- * in the central registry (needs `loadConfig()`). Good enough for an agent
- * process discovering the daemon that spawned it or one on the same host.
- *
- * A runtime.json / registry entry whose `pid` is dead (`process.kill(pid, 0)`
- * throwing anything but `EPERM`) is never trusted — same footgun the CLI
- * helper guards against (a crashed daemon's stale token 401ing a fresh one
- * on the same port).
- */
-interface DaemonEndpoint {
-    url: string;
-    token?: string;
-    /** Path of the runtime.json / registry file the endpoint came from.
-     *  Undefined when the endpoint came from env vars. */
-    sourcePath?: string;
-}
-/** Thrown when no daemon endpoint can be discovered. */
-declare class DaemonNotFoundError extends Error {
-    constructor(message?: string);
-}
-/** Thrown on a non-2xx daemon HTTP response. */
-declare class DaemonHttpError extends Error {
-    readonly status: number;
-    readonly body: string;
-    constructor(message: string, status: number, body: string);
-}
-interface DiscoverDaemonOptions {
-    cwd?: string;
-    env?: NodeJS.ProcessEnv;
-    /** Override `homedir()` for BOTH `~/.agentproto/runtime.json` and the
-     *  central registry dir (unless `registryDir` also overrides the latter
-     *  separately) — test hook, so discovery never has to touch a real
-     *  developer machine's `~/.agentproto`. */
-    homeDir?: string;
-    /** Override the central registry directory — test hook. Wins over `homeDir`. */
-    registryDir?: string;
-    /** Override the liveness check for a runtime.json / registry entry's
-     *  `pid` — test hook. Defaults to a real `process.kill(pid, 0)` probe. */
-    isPidAlive?: (pid: number) => boolean;
-}
-/**
- * Resolve the first live daemon endpoint, in the order documented above.
- * Returns undefined when nothing live is found.
- */
-declare function discoverDaemonEndpoint(opts?: DiscoverDaemonOptions): Promise<DaemonEndpoint | undefined>;
-interface StartAgentInput {
-    adapter: string;
-    cwd?: string;
-    model?: string;
-    prompt?: string;
-    label?: string;
-}
-interface PromptAgentOptions {
-    /** Cancel the in-flight turn and deliver this prompt instead. Default false. */
-    interrupt?: boolean;
-    /** `false` returns as soon as the prompt is queued/validated, without
-     *  waiting for the turn to drain. Default true (blocking). */
-    wait?: boolean;
-}
-interface ListSessionsOptions {
-    includeArchived?: boolean;
-    kind?: string;
-}
-interface ReadOutputOptions {
-    format?: "markdown" | "json";
-}
-interface PollEventsOptions {
-    /** Cursor from a prior call's `nextSeq`. Omit to start from the beginning. */
-    since?: number;
-    /** Client-side filter on each record's `kind` field. Omit → all kinds. */
-    types?: string[];
-    limit?: number;
-}
-interface PollEventsResult {
-    sessionId: string;
-    events: Array<Record<string, unknown>>;
-    nextSeq: number;
-    complete: boolean;
-}
-interface DaemonClientOptions {
-    cwd?: string;
-    env?: NodeJS.ProcessEnv;
-    /** Injectable fetch — test hook. Defaults to the global `fetch`. */
-    fetchImpl?: typeof fetch;
-    /** Pre-resolved endpoint — skips discovery, mainly a test hook. */
-    endpoint?: DaemonEndpoint;
-    /** Test hooks forwarded to {@link discoverDaemonEndpoint}. */
-    homeDir?: string;
-    registryDir?: string;
-    isPidAlive?: (pid: number) => boolean;
-}
-/**
- * Thin HTTP client over the daemon's REST surface (`packages/runtime/src/http-server.ts`,
- * read-only reference — this package never imports it). Discovers the daemon
- * endpoint lazily on first call and caches it; a connection failure triggers
- * one re-discovery attempt (covers a daemon restart on the same well-known
- * runtime.json / registry path but a new port/token).
- */
-declare class DaemonClient {
-    private readonly cwd;
-    private readonly env;
-    private readonly fetchImpl;
-    private readonly homeDir;
-    private readonly registryDir;
-    private readonly isPidAlive;
-    private cachedEndpoint;
-    constructor(opts?: DaemonClientOptions);
-    private resolveEndpoint;
-    private request;
-    /**
-     * Spawn a child session — `POST /sessions/agent`. `parentSessionId` is
-     * derived from `AGENTPROTO_SESSION_ID` (set by the daemon on every
-     * ACP-spawned adapter) when present, so session lineage is recorded
-     * without the caller having to thread it through.
-     */
-    startAgent(input: StartAgentInput): Promise<Record<string, unknown>>;
-    /** Send a follow-up turn to a live session — `POST /sessions/:id/prompt`. */
-    promptAgent(sessionId: string, text: string, opts?: PromptAgentOptions): Promise<Record<string, unknown>>;
-    /** List sessions — `GET /sessions`. */
-    listSessions(opts?: ListSessionsOptions): Promise<{
-        sessions: Array<Record<string, unknown>>;
-    }>;
-    /**
-     * Read a session's transcript — `GET /sessions/:id/export`. Chosen over
-     * `/sessions/:id/conversation` (needs a provider-native store registered
-     * for the adapter; not every adapter has one) and `/sessions/:id/preview`
-     * (a raw ring-buffer snapshot, not a rendered transcript): `/export`
-     * works for ANY agent-cli session, falling back to the daemon's own
-     * `events.jsonl` capture when no provider-native reader is registered
-     * (`source: "auto"`, see `transcript-export.ts`) — the one built for
-     * programmatic reads of "what did this session say".
-     */
-    readOutput(sessionId: string, opts?: ReadOutputOptions): Promise<Record<string, unknown>>;
-    /**
-     * Cursor-based poll of a session's structured event log —
-     * `GET /sessions/:id/events`. NOT the same event source as the MCP
-     * `session_events_poll` tool: that tool reads the daemon's in-memory,
-     * cross-session `EventRing` (turn-end/awaiting-input/exited/... lifecycle
-     * events, `packages/runtime/src/orchestration-tools.ts:528`), which has no
-     * plain-HTTP equivalent — it's only reachable over the MCP JSON-RPC
-     * transport, which this zero-dependency client doesn't speak. This route
-     * is the per-SESSION structured `events.jsonl` transcript instead
-     * (`packages/runtime/src/transcript-writer.ts`): cursor-based via
-     * `since`/`nextSeq` same as the MCP tool, and its records DO carry many of
-     * the same `kind`s (`turn-end`, `error`, `permission-resolved`, ...) — but
-     * it has no `exited` / `session:spawned` records (those are registry
-     * state changes, not transcript writes) and no cross-session fan-in
-     * (`sessionIds` filter). `types` is therefore filtered client-side here
-     * against each record's `kind`, not sent as a query param.
-     *
-     * WP-6 (`AgentprotoSignalProvider`, polling every 5s): this is a
-     * non-blocking snapshot read, so it's a direct fit for a poll loop. If
-     * WP-6 needs the actual cross-session lifecycle events (`exited`,
-     * `session:spawned`, multi-session fan-in), it either needs its own
-     * light MCP JSON-RPC client to call `session_events_poll` directly, or
-     * per-session `GET /sessions/:id/wait?since=&event=` (a blocking
-     * long-poll over the SAME EventRing `session_events_poll` reads, but
-     * scoped to one session and one event name at a time — no `types` array).
-     */
-    pollEvents(sessionId: string, opts?: PollEventsOptions): Promise<PollEventsResult>;
-}
-
 /**
  * Daemon sub-agent-spawning tools — the Mastra-tool front for
  * {@link DaemonClient}. Lets the agent spawn/prompt/read/list sibling

package/dist/index.mjs

@@ -1,4 +1,4 @@
-export { DEFAULT_MODEL, DEFAULT_MODEL_CATALOG, DEFAULT_TOOL_IDS, DISABLED_BUILTIN_TOOL_IDS, DaemonClient, DaemonHttpError, DaemonNotFoundError, MastraAcpAgent, buildSqliteMemory, buildSqliteStore, createEventMapper, defaultAgentManifest, discoverDaemonEndpoint, makeAgentFactory, makeDaemonTools, makeWorkspaceTools, messageText, modelRefToString, promptContent, promptText, providerOf, resolveInCwd, resolveMastraModel, resolveMemoryDbPath, runAcpOverStdio, toolCallTitle, toolKindFor } from './chunk-6ILIPWNM.mjs';
+export { DEFAULT_MODEL, DEFAULT_MODEL_CATALOG, DEFAULT_TOOL_IDS, DISABLED_BUILTIN_TOOL_IDS, DaemonClient, DaemonHttpError, DaemonNotFoundError, MastraAcpAgent, buildSqliteMemory, buildSqliteStore, createEventMapper, defaultAgentManifest, discoverDaemonEndpoint, makeAgentFactory, makeDaemonTools, makeWorkspaceTools, messageText, modelRefToString, promptContent, promptText, providerOf, resolveInCwd, resolveMastraModel, resolveMemoryDbPath, runAcpOverStdio, toolCallTitle, toolKindFor } from './chunk-2FKFITFT.mjs';
 import { fileURLToPath } from 'url';
 import { defineAgentCli, createAgentCliRuntime } from '@agentproto/driver-agent-cli';
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentproto/adapter-mastra-agent",
-  "version": "0.5.5",
+  "version": "0.7.0",
   "description": "@agentproto/adapter-mastra-agent — first-party agentproto agent. An AIP-42 AGENT.md run as a live Mastra agent behind an AIP-44 ACP server, spawnable by the daemon like any other AGENT-CLI arm AND launchable standalone via `agentproto-mastra acp`. Our own loop, our own models — no external CLI.",
   "keywords": [
     "agentproto",
@@ -53,20 +53,21 @@
     "@mastra/core": "^1.61.0",
     "@mastra/libsql": "~1.21.1",
     "@mastra/memory": "^1.27.0",
+    "@modelcontextprotocol/sdk": "^1.30.0",
     "zod": "^4.5.4",
     "@agentproto/agent": "0.2.2",
-    "@agentproto/driver-agent-cli": "2.4.0",
-    "@agentproto/mastra": "0.2.9",
-    "@agentproto/runtime": "2.10.1"
+    "@agentproto/driver-agent-cli": "2.4.1",
+    "@agentproto/mastra": "0.2.11",
+    "@agentproto/runtime": "2.12.0"
   },
   "devDependencies": {
     "@types/node": "^25.6.2",
     "tsup": "^8.5.1",
     "typescript": "^5.9.3",
     "vitest": "^3.2.4",
-    "@agentproto/app-kit": "0.7.1",
-    "@agentproto/apps": "0.8.2",
-    "@agentproto/tooling": "0.1.0-alpha.0"
+    "@agentproto/app-kit": "1.0.0",
+    "@agentproto/apps": "0.9.1",
+    "@agentproto/tooling": "0.1.0"
   },
   "scripts": {
     "dev": "tsup --watch",