@prismer/runtime 2.0.6 → 2.0.7

package/dist/index.d.cts

@@ -130,6 +130,15 @@ interface TaskDispatchRequestPayload {
     }>;
     /** Wave-8 W1: assets cloud wants daemon to fold into agent context. */
     assetRefs?: AssetRef[];
+    /**
+     * release201/09 Phase 2 — task project scope. NULL = workspace-level
+     * (`_unscoped` sentinel on disk). Daemon uses this together with
+     * `agentImUserId` / `profile.workspaceId` to compose the per-task
+     * scratch path: `workspaces/<wid>/projects/<pid|_unscoped>/tasks/<tid>/`.
+     * Also forwarded into the spawned agent process as `PRISMER_ACTIVE_PROJECT_ID`
+     * (when non-null) so built-in skill --project flag defaults work.
+     */
+    projectId?: string | null;
 }
 interface TaskDispatchProgressPayload {
     taskId: string;
@@ -155,6 +164,20 @@ interface AssetDispatchObservation {
     /** L5: end-to-end fetch duration in ms (DNS + connect + body read). */
     durationMs?: number;
 }
+/**
+ * P1-2 (2026-05-25): per-file outbox rejection record. Surfaced when daemon's
+ * `outbox-watcher` rejects an artifact because its magic bytes don't match
+ * the file extension (e.g. agent wrote `report.pdf` with markdown content).
+ * Cloud persists these on `IMTask.metadata.outboxRejections` and prepends a
+ * warning section to the next dispatch prompt so the agent can self-correct.
+ */
+interface OutboxRejectionRecord {
+    filename: string;
+    reason: string;
+    inferredMime: string;
+    detectedMime: string;
+    rejectedAt: string;
+}
 interface TaskDispatchReplyPayload {
     taskId: string;
     ok: boolean;
@@ -170,6 +193,13 @@ interface TaskDispatchReplyPayload {
     };
     /** Wave-8 W1: per-asset handling report. */
     assetObservability?: AssetDispatchObservation[];
+    /**
+     * P1-2 (2026-05-25): files quarantined locally by outbox-watcher's
+     * magic-bytes check during this turn. Cloud writes them onto
+     * `IMTask.metadata.outboxRejections` so the next dispatch prompt can warn
+     * the agent.
+     */
+    outboxRejections?: OutboxRejectionRecord[];
 }
 interface TaskCancelPayload {
     taskId: string;
@@ -677,12 +707,6 @@ declare const HermesProfileConfigSchema: z.ZodObject<{
      * native state key directly and records the exact bridge result on the task.
      */
     mirrorNativeGoals: z.ZodDefault<z.ZodBoolean>;
-    /**
-     * Optional checkout path for Hermes Agent source. Used only as a fallback
-     * when the installed `hermes` binary is older than the native Kanban CLI
-     * surface but the local source tree contains hermes_cli/kanban_db.py.
-     */
-    hermesSourceDir: z.ZodOptional<z.ZodString>;
     nativeMirrorTimeoutMs: z.ZodDefault<z.ZodNumber>;
     /** Task authority level: executor (default) or orchestrator. */
     taskAuthority: z.ZodDefault<z.ZodOptional<z.ZodEnum<["executor", "orchestrator"]>>>;
@@ -782,7 +806,6 @@ declare const HermesProfileConfigSchema: z.ZodObject<{
     hermesProfileName?: string | undefined;
     prismerMcpServerPath?: string | undefined;
     prismerProviderBaseUrl?: string | undefined;
-    hermesSourceDir?: string | undefined;
     mcpAllowlist?: string[] | null | undefined;
     operatingPrinciples?: string | Record<string, string> | z.objectOutputType<{
         source: z.ZodString;
@@ -823,7 +846,6 @@ declare const HermesProfileConfigSchema: z.ZodObject<{
     prismerApiKeyEnv?: string | undefined;
     mirrorNativeKanban?: boolean | undefined;
     mirrorNativeGoals?: boolean | undefined;
-    hermesSourceDir?: string | undefined;
     nativeMirrorTimeoutMs?: number | undefined;
     taskAuthority?: "executor" | "orchestrator" | undefined;
     approvalPolicy?: "strict" | "auto-low-risk" | "autonomous" | undefined;
@@ -994,7 +1016,7 @@ type LocalDb = Database.Database;
 declare function openLocalDb(path: string): LocalDb;
 declare function runMigrations(db: LocalDb): void;
 declare function currentSchemaVersion(db: LocalDb): number;
-declare const TARGET_SCHEMA_VERSION = 4;
+declare const TARGET_SCHEMA_VERSION = 5;
 
 type SyncResourceType = 'workspace' | 'agent' | 'agent_profile';
 type SyncOperation = 'create' | 'update' | 'delete';
@@ -1191,11 +1213,28 @@ interface ConfigPaths {
     cacheDir: string;
     logsDir: string;
     /**
-     * Per-task run scratch dirs. Each chat-mention dispatch creates
-     * `${runsDir}/${taskId}/_outbox/` for adapter-produced files; the
-     * OutboxWatcher uploads from there into IMAssets.
+     * Legacy per-task run scratch dirs (pre-release201/09).
+     *
+     * Pre-09: `${runsDir}/${taskId}/_outbox|workdir/`.
+     * 09 Phase 2: dispatch.ts now writes to
+     *   `${root}/workspaces/<wid>/projects/<pid|_unscoped>/tasks/<tid>/{result,workdir}`
+     * via `resolveTaskWorkdir()`. `runsDir` is kept as a fallback for tests + a
+     * once-off startup migration helper (`runs/<tid>/` → new path; symlink 兜底
+     * 90 天兼容期, §9.3.1).
      */
     runsDir: string;
+    /**
+     * release201/09 Phase 2 root for workspace × project × task scoped scratch:
+     * `${root}/workspaces/`. resolveTaskWorkdir() composes the per-task path
+     * underneath. Cache GC + project archive scan this root.
+     */
+    workspacesDir: string;
+    /**
+     * release201/09 Phase 2 root for device × agent role layer:
+     * `${root}/devices/`. v2.0.7 Phase 2 不主动创建,Phase 3 (agent transfer)
+     * 才落盘 `profile.json` / `skills/<slug>/` 等内容,本 helper 只解析路径。
+     */
+    devicesDir: string;
 }
 /**
  * Resolve paths for the prismer home directory. Honors `PRISMER_HOME` env var;
@@ -1883,6 +1922,13 @@ interface DispatchDeps {
     outboxWatcher?: OutboxWatcher;
     /** Daemon paths — used to derive the per-task outbox dir. */
     paths?: ConfigPaths;
+    /**
+     * release201/09 §9.9 — Stable device identifier from `config.toml`. Surfaced
+     * to the spawned agent process as `PRISMER_DAEMON_ID` env for metric-outbox
+     * emission + transfer manifest authoring. Optional so existing tests can
+     * omit it; production runner always provides.
+     */
+    daemonId?: string;
     /**
      * Multi-workspace asset metadata indexes for #filename resolution.
      * Keyed by workspaceId. If absent, #ref resolution is skipped entirely.
@@ -2085,6 +2131,40 @@ interface LocalServerOptions {
      * When set, /healthz reports `assetReady: true`.
      */
     attachAsset?: (req: IncomingMessage, res: ServerResponse) => Promise<boolean>;
+    /**
+     * Optional first-pass handler for `/v1/hooks/*` routes (v2.1 §9.5
+     * daemon-as-hook-intake). Returns true if the request was handled
+     * (response written); false to let the normal route table fall through.
+     * Wired by the daemon runner from `attachHookServer()` in
+     * `daemon/memory/hook-server.ts` whenever both memory + run-session
+     * registry are available. When set, /healthz reports `hooksReady: true`.
+     */
+    attachHooks?: (req: IncomingMessage, res: ServerResponse) => Promise<boolean>;
+    /**
+     * Optional first-pass handler for `/v1/checkpoints/*` routes
+     * (release201/09 §9.4a.7 task product self-check). Independent of
+     * `attachHooks` — checkpoints fire on SDK status-transition only, while
+     * hooks fire per LLM call. Wired by the runner from
+     * `attachCheckpointServer()` in `daemon/checkpoint-server.ts`. When set,
+     * /healthz reports `checkpointsReady: true`.
+     */
+    attachCheckpoints?: (req: IncomingMessage, res: ServerResponse) => Promise<boolean>;
+    /**
+     * Optional snapshot getter for the eval-session capability
+     * (release201/08 §7.2). When provided, /healthz reports `evalSessions`
+     * with the current active count + per-run summaries. The runner wires
+     * this from `EvalSessionRunner.getState()`.
+     */
+    getEvalSessions?: () => {
+        active: number;
+        queued: number;
+        maxConcurrent: number;
+        runs: Array<{
+            runId: string;
+            skillId: string;
+            startedAt: string;
+        }>;
+    };
 }
 interface AssetWriteHandlerResult {
     status: 200 | 400 | 502;
@@ -2299,6 +2379,7 @@ declare class Runner extends EventEmitter {
     private localServer?;
     private outboxWatcher?;
     private memoryWiring?;
+    private runSessionRegistry?;
     private assetMetadataIndexes;
     private workspaceMirrors;
     private assetOriginOutbox?;
@@ -2321,10 +2402,21 @@ declare class Runner extends EventEmitter {
     private taskReaperTimer?;
     private skillResyncTimer?;
     private skillSyncInFlight;
+    private resumeInFlightTimer?;
+    private resumeInFlightDone;
     private pendingReplyCache;
     private pendingReplyRecoveryDone;
     constructor(opts?: RunnerOptions);
     start(): Promise<void>;
+    /**
+     * v2.1 §9.5 — build a ProfileResolver backed by the daemon's local
+     * `agent_profiles` mirror. Used by the hook server to translate
+     * `?profile=<name>` query into agentImUserId + workspaceId + role slug
+     * when the run-session registry doesn't yet have the run mapping
+     * (e.g. for the very first pre_llm_call of a session, before the
+     * adapter has had a chance to call register()).
+     */
+    private buildProfileResolver;
     /**
      * F16 (2026-05-20) — enumerate every non-deleted local agent_profile and
      * fan-out `syncInstalledSkillsForDispatch` via `syncAllAgentSkills`.
@@ -2334,6 +2426,33 @@ declare class Runner extends EventEmitter {
     private syncAllSkillsBackground;
     /** F16 — read all live agent_profiles from local DB → AgentProfile[]. */
     private loadAllProfiles;
+    /**
+     * P0-2 (2026-05-25) — daemon cold-start sweep.
+     *
+     * Pulls `IMTaskRun.status='running'` rows where the bound daemon (via
+     * `IMAgentBinding.boundDaemonId`) is this daemon, then re-enqueues each
+     * via the same `onTaskDispatch` handler the ws path uses. Replaces the
+     * slow (~5min) cloud-side `sweepTimedOut()` fallback for pod restarts.
+     *
+     * Idempotent on the daemon side: `onTaskDispatch` dedupes by taskId
+     * against `runningTasks`, so any task that happened to be redispatched
+     * from cloud immediately after our reconnect (via redispatchPending on
+     * the agent.host.declare path) won't double-trigger here.
+     *
+     * Caveat: if the agent was mid-LLM-call when the daemon crashed, the
+     * resumed dispatch starts the call from scratch — token cost duplicated.
+     * We accept that vs the alternative (5min of silence + cloud marks the
+     * run `failed` without any retry).
+     */
+    private resumeInFlightTasks;
+    /**
+     * Rebuild a `task.dispatch.request` payload from an in-flight IMTaskRun
+     * row + its parent IMTask. Mirrors what cloud-side
+     * v19x-helpers.buildTaskDispatchRequest does, with one extra field:
+     * `metadata.resumed = true` so downstream prompt injection can note
+     * this is a recovery dispatch.
+     */
+    private reconstructDispatchPayload;
     stop(): Promise<void>;
     isRunning(): boolean;
     /**
@@ -2552,13 +2671,13 @@ declare const CCConfigSchema: z.ZodObject<{
         args: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
         env: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
     }, "strip", z.ZodTypeAny, {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }, {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }>, "many">>;
@@ -2573,8 +2692,8 @@ declare const CCConfigSchema: z.ZodObject<{
     maxTurns: number;
     route: "default" | "prismer" | "omniroute";
     mcpServers?: {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }[] | undefined;
@@ -2587,8 +2706,8 @@ declare const CCConfigSchema: z.ZodObject<{
     cwd: string;
     model?: string | undefined;
     mcpServers?: {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }[] | undefined;

package/dist/index.d.ts

@@ -130,6 +130,15 @@ interface TaskDispatchRequestPayload {
     }>;
     /** Wave-8 W1: assets cloud wants daemon to fold into agent context. */
     assetRefs?: AssetRef[];
+    /**
+     * release201/09 Phase 2 — task project scope. NULL = workspace-level
+     * (`_unscoped` sentinel on disk). Daemon uses this together with
+     * `agentImUserId` / `profile.workspaceId` to compose the per-task
+     * scratch path: `workspaces/<wid>/projects/<pid|_unscoped>/tasks/<tid>/`.
+     * Also forwarded into the spawned agent process as `PRISMER_ACTIVE_PROJECT_ID`
+     * (when non-null) so built-in skill --project flag defaults work.
+     */
+    projectId?: string | null;
 }
 interface TaskDispatchProgressPayload {
     taskId: string;
@@ -155,6 +164,20 @@ interface AssetDispatchObservation {
     /** L5: end-to-end fetch duration in ms (DNS + connect + body read). */
     durationMs?: number;
 }
+/**
+ * P1-2 (2026-05-25): per-file outbox rejection record. Surfaced when daemon's
+ * `outbox-watcher` rejects an artifact because its magic bytes don't match
+ * the file extension (e.g. agent wrote `report.pdf` with markdown content).
+ * Cloud persists these on `IMTask.metadata.outboxRejections` and prepends a
+ * warning section to the next dispatch prompt so the agent can self-correct.
+ */
+interface OutboxRejectionRecord {
+    filename: string;
+    reason: string;
+    inferredMime: string;
+    detectedMime: string;
+    rejectedAt: string;
+}
 interface TaskDispatchReplyPayload {
     taskId: string;
     ok: boolean;
@@ -170,6 +193,13 @@ interface TaskDispatchReplyPayload {
     };
     /** Wave-8 W1: per-asset handling report. */
     assetObservability?: AssetDispatchObservation[];
+    /**
+     * P1-2 (2026-05-25): files quarantined locally by outbox-watcher's
+     * magic-bytes check during this turn. Cloud writes them onto
+     * `IMTask.metadata.outboxRejections` so the next dispatch prompt can warn
+     * the agent.
+     */
+    outboxRejections?: OutboxRejectionRecord[];
 }
 interface TaskCancelPayload {
     taskId: string;
@@ -677,12 +707,6 @@ declare const HermesProfileConfigSchema: z.ZodObject<{
      * native state key directly and records the exact bridge result on the task.
      */
     mirrorNativeGoals: z.ZodDefault<z.ZodBoolean>;
-    /**
-     * Optional checkout path for Hermes Agent source. Used only as a fallback
-     * when the installed `hermes` binary is older than the native Kanban CLI
-     * surface but the local source tree contains hermes_cli/kanban_db.py.
-     */
-    hermesSourceDir: z.ZodOptional<z.ZodString>;
     nativeMirrorTimeoutMs: z.ZodDefault<z.ZodNumber>;
     /** Task authority level: executor (default) or orchestrator. */
     taskAuthority: z.ZodDefault<z.ZodOptional<z.ZodEnum<["executor", "orchestrator"]>>>;
@@ -782,7 +806,6 @@ declare const HermesProfileConfigSchema: z.ZodObject<{
     hermesProfileName?: string | undefined;
     prismerMcpServerPath?: string | undefined;
     prismerProviderBaseUrl?: string | undefined;
-    hermesSourceDir?: string | undefined;
     mcpAllowlist?: string[] | null | undefined;
     operatingPrinciples?: string | Record<string, string> | z.objectOutputType<{
         source: z.ZodString;
@@ -823,7 +846,6 @@ declare const HermesProfileConfigSchema: z.ZodObject<{
     prismerApiKeyEnv?: string | undefined;
     mirrorNativeKanban?: boolean | undefined;
     mirrorNativeGoals?: boolean | undefined;
-    hermesSourceDir?: string | undefined;
     nativeMirrorTimeoutMs?: number | undefined;
     taskAuthority?: "executor" | "orchestrator" | undefined;
     approvalPolicy?: "strict" | "auto-low-risk" | "autonomous" | undefined;
@@ -994,7 +1016,7 @@ type LocalDb = Database.Database;
 declare function openLocalDb(path: string): LocalDb;
 declare function runMigrations(db: LocalDb): void;
 declare function currentSchemaVersion(db: LocalDb): number;
-declare const TARGET_SCHEMA_VERSION = 4;
+declare const TARGET_SCHEMA_VERSION = 5;
 
 type SyncResourceType = 'workspace' | 'agent' | 'agent_profile';
 type SyncOperation = 'create' | 'update' | 'delete';
@@ -1191,11 +1213,28 @@ interface ConfigPaths {
     cacheDir: string;
     logsDir: string;
     /**
-     * Per-task run scratch dirs. Each chat-mention dispatch creates
-     * `${runsDir}/${taskId}/_outbox/` for adapter-produced files; the
-     * OutboxWatcher uploads from there into IMAssets.
+     * Legacy per-task run scratch dirs (pre-release201/09).
+     *
+     * Pre-09: `${runsDir}/${taskId}/_outbox|workdir/`.
+     * 09 Phase 2: dispatch.ts now writes to
+     *   `${root}/workspaces/<wid>/projects/<pid|_unscoped>/tasks/<tid>/{result,workdir}`
+     * via `resolveTaskWorkdir()`. `runsDir` is kept as a fallback for tests + a
+     * once-off startup migration helper (`runs/<tid>/` → new path; symlink 兜底
+     * 90 天兼容期, §9.3.1).
      */
     runsDir: string;
+    /**
+     * release201/09 Phase 2 root for workspace × project × task scoped scratch:
+     * `${root}/workspaces/`. resolveTaskWorkdir() composes the per-task path
+     * underneath. Cache GC + project archive scan this root.
+     */
+    workspacesDir: string;
+    /**
+     * release201/09 Phase 2 root for device × agent role layer:
+     * `${root}/devices/`. v2.0.7 Phase 2 不主动创建,Phase 3 (agent transfer)
+     * 才落盘 `profile.json` / `skills/<slug>/` 等内容,本 helper 只解析路径。
+     */
+    devicesDir: string;
 }
 /**
  * Resolve paths for the prismer home directory. Honors `PRISMER_HOME` env var;
@@ -1883,6 +1922,13 @@ interface DispatchDeps {
     outboxWatcher?: OutboxWatcher;
     /** Daemon paths — used to derive the per-task outbox dir. */
     paths?: ConfigPaths;
+    /**
+     * release201/09 §9.9 — Stable device identifier from `config.toml`. Surfaced
+     * to the spawned agent process as `PRISMER_DAEMON_ID` env for metric-outbox
+     * emission + transfer manifest authoring. Optional so existing tests can
+     * omit it; production runner always provides.
+     */
+    daemonId?: string;
     /**
      * Multi-workspace asset metadata indexes for #filename resolution.
      * Keyed by workspaceId. If absent, #ref resolution is skipped entirely.
@@ -2085,6 +2131,40 @@ interface LocalServerOptions {
      * When set, /healthz reports `assetReady: true`.
      */
     attachAsset?: (req: IncomingMessage, res: ServerResponse) => Promise<boolean>;
+    /**
+     * Optional first-pass handler for `/v1/hooks/*` routes (v2.1 §9.5
+     * daemon-as-hook-intake). Returns true if the request was handled
+     * (response written); false to let the normal route table fall through.
+     * Wired by the daemon runner from `attachHookServer()` in
+     * `daemon/memory/hook-server.ts` whenever both memory + run-session
+     * registry are available. When set, /healthz reports `hooksReady: true`.
+     */
+    attachHooks?: (req: IncomingMessage, res: ServerResponse) => Promise<boolean>;
+    /**
+     * Optional first-pass handler for `/v1/checkpoints/*` routes
+     * (release201/09 §9.4a.7 task product self-check). Independent of
+     * `attachHooks` — checkpoints fire on SDK status-transition only, while
+     * hooks fire per LLM call. Wired by the runner from
+     * `attachCheckpointServer()` in `daemon/checkpoint-server.ts`. When set,
+     * /healthz reports `checkpointsReady: true`.
+     */
+    attachCheckpoints?: (req: IncomingMessage, res: ServerResponse) => Promise<boolean>;
+    /**
+     * Optional snapshot getter for the eval-session capability
+     * (release201/08 §7.2). When provided, /healthz reports `evalSessions`
+     * with the current active count + per-run summaries. The runner wires
+     * this from `EvalSessionRunner.getState()`.
+     */
+    getEvalSessions?: () => {
+        active: number;
+        queued: number;
+        maxConcurrent: number;
+        runs: Array<{
+            runId: string;
+            skillId: string;
+            startedAt: string;
+        }>;
+    };
 }
 interface AssetWriteHandlerResult {
     status: 200 | 400 | 502;
@@ -2299,6 +2379,7 @@ declare class Runner extends EventEmitter {
     private localServer?;
     private outboxWatcher?;
     private memoryWiring?;
+    private runSessionRegistry?;
     private assetMetadataIndexes;
     private workspaceMirrors;
     private assetOriginOutbox?;
@@ -2321,10 +2402,21 @@ declare class Runner extends EventEmitter {
     private taskReaperTimer?;
     private skillResyncTimer?;
     private skillSyncInFlight;
+    private resumeInFlightTimer?;
+    private resumeInFlightDone;
     private pendingReplyCache;
     private pendingReplyRecoveryDone;
     constructor(opts?: RunnerOptions);
     start(): Promise<void>;
+    /**
+     * v2.1 §9.5 — build a ProfileResolver backed by the daemon's local
+     * `agent_profiles` mirror. Used by the hook server to translate
+     * `?profile=<name>` query into agentImUserId + workspaceId + role slug
+     * when the run-session registry doesn't yet have the run mapping
+     * (e.g. for the very first pre_llm_call of a session, before the
+     * adapter has had a chance to call register()).
+     */
+    private buildProfileResolver;
     /**
      * F16 (2026-05-20) — enumerate every non-deleted local agent_profile and
      * fan-out `syncInstalledSkillsForDispatch` via `syncAllAgentSkills`.
@@ -2334,6 +2426,33 @@ declare class Runner extends EventEmitter {
     private syncAllSkillsBackground;
     /** F16 — read all live agent_profiles from local DB → AgentProfile[]. */
     private loadAllProfiles;
+    /**
+     * P0-2 (2026-05-25) — daemon cold-start sweep.
+     *
+     * Pulls `IMTaskRun.status='running'` rows where the bound daemon (via
+     * `IMAgentBinding.boundDaemonId`) is this daemon, then re-enqueues each
+     * via the same `onTaskDispatch` handler the ws path uses. Replaces the
+     * slow (~5min) cloud-side `sweepTimedOut()` fallback for pod restarts.
+     *
+     * Idempotent on the daemon side: `onTaskDispatch` dedupes by taskId
+     * against `runningTasks`, so any task that happened to be redispatched
+     * from cloud immediately after our reconnect (via redispatchPending on
+     * the agent.host.declare path) won't double-trigger here.
+     *
+     * Caveat: if the agent was mid-LLM-call when the daemon crashed, the
+     * resumed dispatch starts the call from scratch — token cost duplicated.
+     * We accept that vs the alternative (5min of silence + cloud marks the
+     * run `failed` without any retry).
+     */
+    private resumeInFlightTasks;
+    /**
+     * Rebuild a `task.dispatch.request` payload from an in-flight IMTaskRun
+     * row + its parent IMTask. Mirrors what cloud-side
+     * v19x-helpers.buildTaskDispatchRequest does, with one extra field:
+     * `metadata.resumed = true` so downstream prompt injection can note
+     * this is a recovery dispatch.
+     */
+    private reconstructDispatchPayload;
     stop(): Promise<void>;
     isRunning(): boolean;
     /**
@@ -2552,13 +2671,13 @@ declare const CCConfigSchema: z.ZodObject<{
         args: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
         env: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
     }, "strip", z.ZodTypeAny, {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }, {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }>, "many">>;
@@ -2573,8 +2692,8 @@ declare const CCConfigSchema: z.ZodObject<{
     maxTurns: number;
     route: "default" | "prismer" | "omniroute";
     mcpServers?: {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }[] | undefined;
@@ -2587,8 +2706,8 @@ declare const CCConfigSchema: z.ZodObject<{
     cwd: string;
     model?: string | undefined;
     mcpServers?: {
-        name: string;
         command: string;
+        name: string;
         env?: Record<string, string> | undefined;
         args?: string[] | undefined;
     }[] | undefined;