comisai 1.0.44 → 1.0.46

package/node_modules/@comis/core/dist/api-contracts/media.d.ts

@@ -419,12 +419,12 @@ export declare const MediaProvidersContract: import("./types.js").ApiContract<z.
  * delivery (via `adapter.sendAttachment`) OR base64 fallback when no
  * channel context is present.
  *
- * Request: `prompt`/`size` plus the optional CFG-02 fields `model` (a
+ * Request: `prompt`/`size` plus the optional fields `model` (a
  * provider-default override, validated by the handler against the provider's
- * model list — IN-02) and `reference_image` (a workspace path / url / data-uri
- * STRING for edit/img2img, resolved by the handler — IN-01). The fields are
+ * model list) and `reference_image` (a workspace path / url / data-uri
+ * STRING for edit/img2img, resolved by the handler). The fields are
  * additive (prompt-only callers are unaffected) and exist on the parsed request
- * so the handler sees them typed (Pitfall 5).
+ * so the handler sees them typed.
  *
  * Bespoke pre-Zod validation (handler returns `{ success: false, error }`-
  * shape — does NOT throw):
@@ -450,16 +450,16 @@ export declare const ImageGenerateContract: import("./types.js").ApiContract<z.Z
  * `video.generate` — generate a video via the agent's main provider's video
  * backend (or explicit FAL), through one `VideoGenerationPort` whose inline
  * `execute()` does submit→poll→download. Applies a per-agent rate limit + a
- * PRE-submit worst-case cost ceiling (SEC-02, I6) + direct channel delivery
+ * PRE-submit worst-case cost ceiling + direct channel delivery
  * (via `adapter.sendAttachment` with `AttachmentPayload.type:"video"`) OR a
- * size-capped base64 fallback when no channel context is present (DEL-04).
+ * size-capped base64 fallback when no channel context is present.
  *
  * Request: `prompt` plus the optional fields `duration` / `aspect_ratio` /
  * `resolution` / `audio` / `negative_prompt` / `seed` / `image_url`
  * (SSRF-guarded workspace path / url / data-uri for image-to-video) / `model`
  * (a provider-default endpoint override). The fields are additive (prompt-only
  * callers are unaffected) and exist on the parsed request so the handler
- * (Plan 04) sees them typed. Only the allowlisted request shapes
+ * sees them typed. Only the allowlisted request shapes
  * (z.string()/z.number()/z.boolean()/.optional()) are used — NO `.url()` /
  * `.regex()` refinements (the 12-shape contract allowlist; the handler enforces
  * SSRF on `image_url`).
@@ -481,19 +481,19 @@ export declare const VideoGenerateContract: import("./types.js").ApiContract<z.Z
 /**
  * `video.status` — read the status/progress/result of a video-generation job
  * by its opaque job handle (the `jobId` `video.generate` returned at submit),
- * SCOPED to the calling agent. The Phase-189 async lifecycle: `video.generate`
+ * SCOPED to the calling agent. The async lifecycle: `video.generate`
  * submits + returns a handle; the background poller drives the render to
  * completion off-turn; `video.status{job_id}` reports the durable terminal state.
  *
- * AGENT-SCOPED (JOB-04 / TARGET-01): the handler resolves the agent explicitly
+ * AGENT-SCOPED: the handler resolves the agent explicitly
  * and reads `videoJobStore.get(job_id, agentId)` — a job belonging to ANOTHER
  * agent returns not-found (`{state:"failed", error:"No video job <id> for this
- * agent"}`), NEVER the other agent's mediaPath/cost (threat T-189-10).
+ * agent"}`), NEVER the other agent's mediaPath/cost (cross-agent job probing).
  *
- * Request: `job_id` (the opaque, secret-free provider request id — T-189-12;
+ * Request: `job_id` (the opaque, secret-free provider request id;
  * echoing an unknown id in the not-found error leaks nothing).
  *
- * Response: `state` is a CLOSED `z.enum(["pending","done","failed"])` (O4 — the
+ * Response: `state` is a CLOSED `z.enum(["pending","done","failed"])` (the
  * enum tightens the contract over the loose-record `video.generate` handle);
  * `progress` / `mediaPath` / `costUsd` / `error` are present per terminal state.
  * Only the allowlisted request/response shapes are used (z.string()/z.number()/
@@ -519,11 +519,6 @@ export declare const VideoStatusContract: import("./types.js").ApiContract<z.Zod
  * PropertyAssignment order. The order within this array is documentation-only;
  * the bidirectional 1:1 architecture test treats `MEDIA_CONTRACTS` as an
  * unordered set.
- *
- * NOTE: `video.status`'s daemon handler (`createVideoStatusHandlers`) lands in
- * Phase 189 Plan 03 in the SAME wave the contract is declared, so the
- * bidirectional handler-parity gate and the web codegen drift gate both see it
- * closed within this plan (no cross-wave strand — the 188 BLOCKER-1 class).
  */
 export declare const MEDIA_CONTRACTS: readonly [import("./types.js").ApiContract<z.ZodObject<{
     source_type: z.ZodOptional<z.ZodString>;

package/node_modules/@comis/core/dist/api-contracts/media.js

@@ -550,12 +550,12 @@ export const MediaProvidersContract = defineContract({
  * delivery (via `adapter.sendAttachment`) OR base64 fallback when no
  * channel context is present.
  *
- * Request: `prompt`/`size` plus the optional CFG-02 fields `model` (a
+ * Request: `prompt`/`size` plus the optional fields `model` (a
  * provider-default override, validated by the handler against the provider's
- * model list — IN-02) and `reference_image` (a workspace path / url / data-uri
- * STRING for edit/img2img, resolved by the handler — IN-01). The fields are
+ * model list) and `reference_image` (a workspace path / url / data-uri
+ * STRING for edit/img2img, resolved by the handler). The fields are
  * additive (prompt-only callers are unaffected) and exist on the parsed request
- * so the handler sees them typed (Pitfall 5).
+ * so the handler sees them typed.
  *
  * Bespoke pre-Zod validation (handler returns `{ success: false, error }`-
  * shape — does NOT throw):
@@ -576,10 +576,10 @@ export const ImageGenerateContract = defineContract({
     request: z.object({
         prompt: z.string().optional(),
         size: z.string().optional(),
-        // CFG-02 (Pitfall 5): the handler `.parse`s this request — without growing
-        // it, `params.model`/`params.reference_image` are typed `undefined` to the
-        // handler even though Zod would pass unknown keys through at runtime. Plan 03
-        // consumes these typed fields (IN-01 reference resolution + IN-02 model
+        // The handler `.parse`s this request — without declaring these fields,
+        // `params.model`/`params.reference_image` are typed `undefined` to the
+        // handler even though Zod would pass unknown keys through at runtime. The
+        // handler consumes these typed fields (reference resolution + model
         // validation). Additive: existing prompt/size callers are unaffected.
         model: z.string().optional(),
         // A workspace file path / url / data-uri STRING (resolved by the handler).
@@ -595,16 +595,16 @@ export const ImageGenerateContract = defineContract({
  * `video.generate` — generate a video via the agent's main provider's video
  * backend (or explicit FAL), through one `VideoGenerationPort` whose inline
  * `execute()` does submit→poll→download. Applies a per-agent rate limit + a
- * PRE-submit worst-case cost ceiling (SEC-02, I6) + direct channel delivery
+ * PRE-submit worst-case cost ceiling + direct channel delivery
  * (via `adapter.sendAttachment` with `AttachmentPayload.type:"video"`) OR a
- * size-capped base64 fallback when no channel context is present (DEL-04).
+ * size-capped base64 fallback when no channel context is present.
  *
  * Request: `prompt` plus the optional fields `duration` / `aspect_ratio` /
  * `resolution` / `audio` / `negative_prompt` / `seed` / `image_url`
  * (SSRF-guarded workspace path / url / data-uri for image-to-video) / `model`
  * (a provider-default endpoint override). The fields are additive (prompt-only
  * callers are unaffected) and exist on the parsed request so the handler
- * (Plan 04) sees them typed. Only the allowlisted request shapes
+ * sees them typed. Only the allowlisted request shapes
  * (z.string()/z.number()/z.boolean()/.optional()) are used — NO `.url()` /
  * `.regex()` refinements (the 12-shape contract allowlist; the handler enforces
  * SSRF on `image_url`).
@@ -631,19 +631,19 @@ export const VideoGenerateContract = defineContract({
 /**
  * `video.status` — read the status/progress/result of a video-generation job
  * by its opaque job handle (the `jobId` `video.generate` returned at submit),
- * SCOPED to the calling agent. The Phase-189 async lifecycle: `video.generate`
+ * SCOPED to the calling agent. The async lifecycle: `video.generate`
  * submits + returns a handle; the background poller drives the render to
  * completion off-turn; `video.status{job_id}` reports the durable terminal state.
  *
- * AGENT-SCOPED (JOB-04 / TARGET-01): the handler resolves the agent explicitly
+ * AGENT-SCOPED: the handler resolves the agent explicitly
  * and reads `videoJobStore.get(job_id, agentId)` — a job belonging to ANOTHER
  * agent returns not-found (`{state:"failed", error:"No video job <id> for this
- * agent"}`), NEVER the other agent's mediaPath/cost (threat T-189-10).
+ * agent"}`), NEVER the other agent's mediaPath/cost (cross-agent job probing).
  *
- * Request: `job_id` (the opaque, secret-free provider request id — T-189-12;
+ * Request: `job_id` (the opaque, secret-free provider request id;
  * echoing an unknown id in the not-found error leaks nothing).
  *
- * Response: `state` is a CLOSED `z.enum(["pending","done","failed"])` (O4 — the
+ * Response: `state` is a CLOSED `z.enum(["pending","done","failed"])` (the
  * enum tightens the contract over the loose-record `video.generate` handle);
  * `progress` / `mediaPath` / `costUsd` / `error` are present per terminal state.
  * Only the allowlisted request/response shapes are used (z.string()/z.number()/
@@ -671,11 +671,6 @@ export const VideoStatusContract = defineContract({
  * PropertyAssignment order. The order within this array is documentation-only;
  * the bidirectional 1:1 architecture test treats `MEDIA_CONTRACTS` as an
  * unordered set.
- *
- * NOTE: `video.status`'s daemon handler (`createVideoStatusHandlers`) lands in
- * Phase 189 Plan 03 in the SAME wave the contract is declared, so the
- * bidirectional handler-parity gate and the web codegen drift gate both see it
- * closed within this plan (no cross-wave strand — the 188 BLOCKER-1 class).
  */
 export const MEDIA_CONTRACTS = [
     // media-handlers.ts (15)

package/node_modules/@comis/core/dist/api-contracts/memory-diagnostics.d.ts

@@ -8,19 +8,13 @@
  * of the memory domain and are re-exported from `memory.ts`, so every existing
  * `from "./memory.js"` import (and the api-contracts barrel) still resolves.
  *
- * CROSS-WAVE SEAM (now closed): these are grouped in their OWN
- * `MEMORY_DIAGNOSTIC_CONTRACTS` array below. They were initially held OUT of
- * `MEMORY_CONTRACTS` (which feeds `API_CONTRACTS` via index.ts) — and tagged
- * each with `// @contract-deferred-handler` — because the
- * `api-contracts-bidirectional.test.ts` + `contract-handler-parity.test.ts`
- * gates require every `API_CONTRACTS` entry to have a MIGRATED
- * (`[Contract.method]:` computed-key) daemon handler, and registering them
- * before the handlers existed would have turned those gates RED between waves.
- * The four daemon handlers later landed in
- * `packages/daemon/src/api/memory-handlers.ts`, spread
- * `...MEMORY_DIAGNOSTIC_CONTRACTS` into `MEMORY_CONTRACTS`, AND removed the
- * four `@contract-deferred-handler` annotations — all in one diff — so the
- * registry↔handler set is 1:1 again.
+ * These are grouped in their OWN `MEMORY_DIAGNOSTIC_CONTRACTS` array below and
+ * spread into `MEMORY_CONTRACTS` (which feeds `API_CONTRACTS` via index.ts).
+ * The `api-contracts-bidirectional.test.ts` + `contract-handler-parity.test.ts`
+ * gates require every `API_CONTRACTS` entry to have a daemon handler registered
+ * under a `[Contract.method]:` computed key — the four handlers live in
+ * `packages/daemon/src/api/memory-handlers.ts`, so a contract added here must
+ * land in the same diff as its handler to keep the registry↔handler set 1:1.
  *
  * @module
  */
@@ -84,7 +78,7 @@ export declare const MemoryObservationsContract: import("./types.js").ApiContrac
 }, z.core.$strip>>;
 /**
  * `memory.entities` — list the entity graph for the scope, ordered
- * most-mentioned-first (admin-only). The handler calls the new
+ * most-mentioned-first (admin-only). The handler calls the
  * `MemoryEntityStore.listEntities(agentId, tenantId, limit)` scoped read
  * (defined in `ports/memory-entity-store.ts`).
  *
@@ -142,11 +136,9 @@ export declare const MemoryRecallStatsContract: import("./types.js").ApiContract
     recallHitRate: z.ZodNumber;
 }, z.core.$strip>>;
 /**
- * Admin-scoped diagnostic contracts. Originally defined here but held
- * OUT of `MEMORY_CONTRACTS` until the matching daemon handlers landed —
- * see the cross-wave-seam note at the top of this file. They are now folded
- * into `MEMORY_CONTRACTS` (`...MEMORY_DIAGNOSTIC_CONTRACTS`) in the same
- * diff as the handlers.
+ * Admin-scoped diagnostic contracts, folded into `MEMORY_CONTRACTS`
+ * (`...MEMORY_DIAGNOSTIC_CONTRACTS`). Every entry must have a matching daemon
+ * handler — see the registry↔handler note at the top of this file.
  */
 export declare const MEMORY_DIAGNOSTIC_CONTRACTS: readonly [import("./types.js").ApiContract<z.ZodObject<{
     session_key: z.ZodOptional<z.ZodString>;

package/node_modules/@comis/core/dist/api-contracts/memory-diagnostics.js

@@ -9,19 +9,13 @@
  * of the memory domain and are re-exported from `memory.ts`, so every existing
  * `from "./memory.js"` import (and the api-contracts barrel) still resolves.
  *
- * CROSS-WAVE SEAM (now closed): these are grouped in their OWN
- * `MEMORY_DIAGNOSTIC_CONTRACTS` array below. They were initially held OUT of
- * `MEMORY_CONTRACTS` (which feeds `API_CONTRACTS` via index.ts) — and tagged
- * each with `// @contract-deferred-handler` — because the
- * `api-contracts-bidirectional.test.ts` + `contract-handler-parity.test.ts`
- * gates require every `API_CONTRACTS` entry to have a MIGRATED
- * (`[Contract.method]:` computed-key) daemon handler, and registering them
- * before the handlers existed would have turned those gates RED between waves.
- * The four daemon handlers later landed in
- * `packages/daemon/src/api/memory-handlers.ts`, spread
- * `...MEMORY_DIAGNOSTIC_CONTRACTS` into `MEMORY_CONTRACTS`, AND removed the
- * four `@contract-deferred-handler` annotations — all in one diff — so the
- * registry↔handler set is 1:1 again.
+ * These are grouped in their OWN `MEMORY_DIAGNOSTIC_CONTRACTS` array below and
+ * spread into `MEMORY_CONTRACTS` (which feeds `API_CONTRACTS` via index.ts).
+ * The `api-contracts-bidirectional.test.ts` + `contract-handler-parity.test.ts`
+ * gates require every `API_CONTRACTS` entry to have a daemon handler registered
+ * under a `[Contract.method]:` computed key — the four handlers live in
+ * `packages/daemon/src/api/memory-handlers.ts`, so a contract added here must
+ * land in the same diff as its handler to keep the registry↔handler set 1:1.
  *
  * @module
  */
@@ -56,19 +50,19 @@ export const MemoryRecallTraceContract = defineContract({
         tenant_id: z.string().optional(),
         agent_id: z.string().optional(),
         // Bound the limit at parse time — positive integer with a sane cap.
-        // An unbounded/negative/fractional limit used to flow straight into the
-        // file-scan guard (`records.length >= limit`), so reject malformed bounds
-        // here (defense-in-depth + clearer UX), consistent with Comis's other
-        // `.int().positive()` contracts.
+        // An unbounded/negative/fractional limit would otherwise flow straight
+        // into the file-scan guard (`records.length >= limit`), so reject
+        // malformed bounds here (defense-in-depth + clearer UX), consistent with
+        // Comis's other `.int().positive()` contracts.
         limit: z.number().int().positive().max(1000).optional(),
     }),
     response: z.object({
         records: z.array(z.record(z.string(), z.unknown())),
-        // Live finding 2026-06-11: the handler returned a bare `{records: []}`
-        // when the recorder was simply disabled (diagnostics.recallTrace.enabled
-        // defaults false) — a silent empty in the very tool that exists to
-        // diagnose recall. tracingEnabled reports the recorder gate; hint (only
-        // when records is empty) says WHY it is empty and which knob enables it.
+        // A bare `{records: []}` when the recorder is simply disabled
+        // (diagnostics.recallTrace.enabled defaults false) would be a silent
+        // empty in the very tool that exists to diagnose recall. tracingEnabled
+        // reports the recorder gate; hint (only when records is empty) says WHY
+        // it is empty and which knob enables it.
         tracingEnabled: z.boolean().optional(),
         hint: z.string().optional(),
     }),
@@ -116,7 +110,7 @@ export const MemoryObservationsContract = defineContract({
 // ---------------------------------------------------------------------------
 /**
  * `memory.entities` — list the entity graph for the scope, ordered
- * most-mentioned-first (admin-only). The handler calls the new
+ * most-mentioned-first (admin-only). The handler calls the
  * `MemoryEntityStore.listEntities(agentId, tenantId, limit)` scoped read
  * (defined in `ports/memory-entity-store.ts`).
  *
@@ -188,11 +182,9 @@ export const MemoryRecallStatsContract = defineContract({
     scopes: ["admin"],
 });
 /**
- * Admin-scoped diagnostic contracts. Originally defined here but held
- * OUT of `MEMORY_CONTRACTS` until the matching daemon handlers landed —
- * see the cross-wave-seam note at the top of this file. They are now folded
- * into `MEMORY_CONTRACTS` (`...MEMORY_DIAGNOSTIC_CONTRACTS`) in the same
- * diff as the handlers.
+ * Admin-scoped diagnostic contracts, folded into `MEMORY_CONTRACTS`
+ * (`...MEMORY_DIAGNOSTIC_CONTRACTS`). Every entry must have a matching daemon
+ * handler — see the registry↔handler note at the top of this file.
  */
 export const MEMORY_DIAGNOSTIC_CONTRACTS = [
     MemoryRecallTraceContract,

package/node_modules/@comis/core/dist/api-contracts/memory-pinning.d.ts

@@ -6,11 +6,6 @@
  *   - `memory.pin`   — mark a memory entry as always-injected in recall.
  *   - `memory.unpin` — remove the always-inject mark.
  *
- * Seam closed in plan 03-03 (same diff as handler creation): the
- * `@contract-deferred-handler` annotations were removed, the spread into
- * MEMORY_CONTRACTS was added to memory.ts, and pnpm contracts:generate was run —
- * mirroring the memory-diagnostics pattern.
- *
  * @module
  */
 import { z } from "zod";

package/node_modules/@comis/core/dist/api-contracts/memory-pinning.js

@@ -7,11 +7,6 @@
  *   - `memory.pin`   — mark a memory entry as always-injected in recall.
  *   - `memory.unpin` — remove the always-inject mark.
  *
- * Seam closed in plan 03-03 (same diff as handler creation): the
- * `@contract-deferred-handler` annotations were removed, the spread into
- * MEMORY_CONTRACTS was added to memory.ts, and pnpm contracts:generate was run —
- * mirroring the memory-diagnostics pattern.
- *
  * @module
  */
 import { z } from "zod";
@@ -25,7 +20,7 @@ export const MemoryPinContract = defineContract({
     }),
     response: z.object({
         pinned: z.literal(true),
-        // IN-02: `found` surfaces whether the memory row existed in the caller's scope.
+        // `found` surfaces whether the memory row existed in the caller's scope.
         // found=true: row found and pinned. found=false: id not found (pin was a no-op).
         // Callers that only inspect `pinned` are unaffected (additive field).
         found: z.boolean(),

package/node_modules/@comis/core/dist/api-contracts/memory-portability.js

@@ -75,9 +75,9 @@ export const MemoryPortabilityImportContract = defineContract({
         imported: z.number(),
         blocked: z.number(),
         downgraded: z.number(),
-        /** MEM-IMPORT-DUP (30uc-20260624 UC-22): entries skipped because their content already
-         *  exists in the target scope (idempotent re-import — re-importing an export does not
-         *  duplicate; a deleted memory is still restored since its content is absent). */
+        /** Entries skipped because their content already exists in the target scope
+         *  (idempotent re-import — re-importing an export does not duplicate; a deleted
+         *  memory is still restored since its content is absent). */
         deduped: z.number(),
         total: z.number(),
         dryRun: z.boolean(),

package/node_modules/@comis/core/dist/api-contracts/memory.d.ts

@@ -4,11 +4,6 @@
  *
  *   - `packages/daemon/src/api/memory-handlers.ts`  (8 methods)
  *
- * NOTE (v2.12, Phase 126): the sibling `context-handlers.ts` (7 `context.*`
- * methods) and its 7 `Context*Contract` definitions were REMOVED with the DAG
- * context engine. The governed context-expansion RPC surface is reintroduced
- * fresh by the LCD engine (Phase 131).
- *
  * The aggregator below preserves per-handler grouping via
  * `// --- xxx-handlers.ts ---` comment blocks; the order within the array is
  * documentation-only (the bidirectional 1:1 test treats it as an unordered
@@ -25,12 +20,11 @@
  *                                     intended trust model.
  *   - `memory.get_file`     (rpc) — agent-level file read via safePath.
  *                                     Registered via agent tool dispatch.
- *   - `memory.store`        (rpc) — AGENT-REACHABLE (MD-02): the agent
+ *   - `memory.store`        (rpc) — AGENT-REACHABLE: the agent
  *                                      `memory_store` tool is the primary caller.
  *                                      The handler routes on `_trustLevel` — admin
  *                                      (operator) vs the agent path (defaults to
  *                                      `learned` trust + agent attribution).
- *                                      (Was `admin`, which deny-by-origin blocked.)
  *   - `memory.stats`        (admin) — setup-gateway-api.ts line 234.
  *   - `memory.browse`       (admin) — setup-gateway-api.ts line 234.
  *   - `memory.delete`       (admin) — setup-gateway-api.ts line 234.
@@ -51,14 +45,6 @@
  *   - `memory.export.response.entries[]` — similar nested-record shape;
  *     `source` is `Record<string, unknown>` at the leaf.
  *
- * **CLI memory search/inspect (v2.12).** The CLI's
- * `packages/cli/src/commands/memory.ts` previously borrowed the (now-removed)
- * `context.search` / `context.inspect` RPCs for its `memory search` /
- * `memory inspect` subcommands. With the DAG context engine demolished those
- * commands fail closed (explicit not-available message + non-zero exit) — there
- * is no `memory.search` / `memory.inspect` handler. Full-text context search +
- * entry inspection return with the LCD engine (Phase 131).
- *
  * @module
  */
 import { z } from "zod";
@@ -110,16 +96,6 @@ export declare const MemorySearchFilesContract: import("./types.js").ApiContract
  *
  * Registered via agent tool dispatch (the `memory_ask` tool); contract scope
  * `["rpc"]` documents the intended trust model.
- *
- * CROSS-WAVE SEAM (now closed): the contract SHAPE shipped first with a
- * deferred-handler annotation and was kept OUT of `MEMORY_CONTRACTS` until its
- * daemon handler existed (registering it before the handler would RED-gate
- * contract-handler-parity + bidirectional 1:1). The
- * `[MemoryAskContract.method]:` handler later landed in `memory-handlers.ts` and,
- * in the SAME diff, this contract was spread into `MEMORY_CONTRACTS`
- * (8 + 4 + 7 + 1 = 20) and that annotation removed — so the registry ↔ handler
- * set is 1:1 by construction. (Mirrors the diagnostic cross-wave seam closed
- * earlier.)
  */
 export declare const MemoryAskContract: import("./types.js").ApiContract<z.ZodObject<{
     question: z.ZodString;
@@ -152,14 +128,13 @@ export declare const MemoryGetFileContract: import("./types.js").ApiContract<z.Z
 /**
  * `memory.store` — write a memory entry. `scopes:["rpc"]` — AGENT-REACHABLE:
  * the agent `memory_store` tool is the primary caller, where the trust level
- * defaults to `learned`. (Was `scopes:["admin"]`, the MD-02 deny-by-origin
- * regression: `["admin"]` put it in `ADMIN_METHODS` so the `assertNotAgentOrigin`
- * chokepoint threw "Control-plane method memory.store is not reachable from an
+ * defaults to `learned`. The scope must NOT be `["admin"]`: that would place
+ * the method in `ADMIN_METHODS`, and the `assertNotAgentOrigin` chokepoint
+ * would throw "Control-plane method memory.store is not reachable from an
  * agent origin" for the agent's `_agentId`-bearing call — the `memory_store`
- * tool could not store anything. Re-scoped admin→rpc 2026-06-24, matching the
- * earlier `message.send`/`skills.*`/`session.list` fixes; guarded by
- * `test/architecture/agent-memory-tools-deny-by-origin.test.ts`.) The handler
- * still routes on the dispatcher-injected `_trustLevel`:
+ * tool could not store anything (guarded by
+ * `test/architecture/agent-memory-tools-deny-by-origin.test.ts`). The handler
+ * routes on the dispatcher-injected `_trustLevel`:
  *   - `_trustLevel === "admin"` (operator path): operator-attributed (channel: web-console), may override trust to learned/external.
  *   - Otherwise (agent path): agent-attributed (channel: agent-tool), trust defaults to `learned` (never `system`).
  *
@@ -188,10 +163,8 @@ export declare const MemoryStoreContract: import("./types.js").ApiContract<z.Zod
  * embeddedEntries, dbSizeBytes, etc.) and is modelled with a loose
  * record to avoid pinning the underlying impl's wire format.
  *
- * The CLI's `memory stats` subcommand currently invokes the
- * gateway-adapter `memory.inspect` (which fans out to a different code
- * path), NOT this handler — see the gateway-adapter shim caveat in the
- * file header.
+ * The CLI's `memory stats` subcommand routes through this contract
+ * (via `callTyped`), folding recall counters into the same view.
  */
 export declare const MemoryStatsContract: import("./types.js").ApiContract<z.ZodObject<{
     tenant_id: z.ZodOptional<z.ZodString>;
@@ -300,17 +273,9 @@ export { MEMORY_DIAGNOSTIC_CONTRACTS };
  * The grouping below is documentation-only (the bidirectional 1:1 test
  * treats the tuple as an unordered set).
  *
- * `MEMORY_DIAGNOSTIC_CONTRACTS` (the four diagnostic
- * contracts) is now spread in — in the SAME wave that landed the matching
- * `[Contract.method]:` daemon handlers in `memory-handlers.ts` — so the
- * `API_CONTRACTS` registry ↔ handler set stays 1:1 (the cross-wave seam is
- * closed; the `@contract-deferred-handler` annotations were
- * removed in the same diff).
- *
- * `MemoryAskContract` (the dialectic memory.ask surface) is
- * now spread in — in the SAME diff that landed its `[MemoryAskContract.method]:`
- * handler in `memory-handlers.ts` — so the registry ↔ handler set stays 1:1 and
- * the `@contract-deferred-handler` tag was removed in the same diff.
+ * Every contract spread in here has a matching `[Contract.method]:` daemon
+ * handler in `memory-handlers.ts`, so the `API_CONTRACTS` registry ↔ handler
+ * set stays 1:1.
  */
 export declare const MEMORY_CONTRACTS: readonly [import("./types.js").ApiContract<z.ZodObject<{
     query: z.ZodString;

package/node_modules/@comis/core/dist/api-contracts/memory.js

@@ -5,11 +5,6 @@
  *
  *   - `packages/daemon/src/api/memory-handlers.ts`  (8 methods)
  *
- * NOTE (v2.12, Phase 126): the sibling `context-handlers.ts` (7 `context.*`
- * methods) and its 7 `Context*Contract` definitions were REMOVED with the DAG
- * context engine. The governed context-expansion RPC surface is reintroduced
- * fresh by the LCD engine (Phase 131).
- *
  * The aggregator below preserves per-handler grouping via
  * `// --- xxx-handlers.ts ---` comment blocks; the order within the array is
  * documentation-only (the bidirectional 1:1 test treats it as an unordered
@@ -26,12 +21,11 @@
  *                                     intended trust model.
  *   - `memory.get_file`     (rpc) — agent-level file read via safePath.
  *                                     Registered via agent tool dispatch.
- *   - `memory.store`        (rpc) — AGENT-REACHABLE (MD-02): the agent
+ *   - `memory.store`        (rpc) — AGENT-REACHABLE: the agent
  *                                      `memory_store` tool is the primary caller.
  *                                      The handler routes on `_trustLevel` — admin
  *                                      (operator) vs the agent path (defaults to
  *                                      `learned` trust + agent attribution).
- *                                      (Was `admin`, which deny-by-origin blocked.)
  *   - `memory.stats`        (admin) — setup-gateway-api.ts line 234.
  *   - `memory.browse`       (admin) — setup-gateway-api.ts line 234.
  *   - `memory.delete`       (admin) — setup-gateway-api.ts line 234.
@@ -52,14 +46,6 @@
  *   - `memory.export.response.entries[]` — similar nested-record shape;
  *     `source` is `Record<string, unknown>` at the leaf.
  *
- * **CLI memory search/inspect (v2.12).** The CLI's
- * `packages/cli/src/commands/memory.ts` previously borrowed the (now-removed)
- * `context.search` / `context.inspect` RPCs for its `memory search` /
- * `memory inspect` subcommands. With the DAG context engine demolished those
- * commands fail closed (explicit not-available message + non-zero exit) — there
- * is no `memory.search` / `memory.inspect` handler. Full-text context search +
- * entry inspection return with the LCD engine (Phase 131).
- *
  * @module
  */
 import { z } from "zod";
@@ -73,8 +59,8 @@ export { MemoryPortabilityExportContract, MemoryPortabilityImportContract, MEMOR
 // Only the array is needed as a local value (spread into MEMORY_CONTRACTS below);
 // the two contract objects are re-exported via the `export { ... } from` above.
 import { MEMORY_PORTABILITY_CONTRACTS } from "./memory-portability.js";
-// Pinning contracts extracted to memory-pinning.ts (file-size cap §4.1).
-// @contract-deferred-handler annotations removed in plan 03-03 (same diff as handler creation).
+// Pinning contracts extracted to memory-pinning.ts to keep this file within
+// the 800-line architecture cap.
 export { MemoryPinContract, MemoryUnpinContract, MEMORY_PINNING_CONTRACTS, } from "./memory-pinning.js";
 import { MEMORY_PINNING_CONTRACTS } from "./memory-pinning.js";
 // ===========================================================================
@@ -136,16 +122,6 @@ export const MemorySearchFilesContract = defineContract({
  *
  * Registered via agent tool dispatch (the `memory_ask` tool); contract scope
  * `["rpc"]` documents the intended trust model.
- *
- * CROSS-WAVE SEAM (now closed): the contract SHAPE shipped first with a
- * deferred-handler annotation and was kept OUT of `MEMORY_CONTRACTS` until its
- * daemon handler existed (registering it before the handler would RED-gate
- * contract-handler-parity + bidirectional 1:1). The
- * `[MemoryAskContract.method]:` handler later landed in `memory-handlers.ts` and,
- * in the SAME diff, this contract was spread into `MEMORY_CONTRACTS`
- * (8 + 4 + 7 + 1 = 20) and that annotation removed — so the registry ↔ handler
- * set is 1:1 by construction. (Mirrors the diagnostic cross-wave seam closed
- * earlier.)
  */
 export const MemoryAskContract = defineContract({
     method: "memory.ask",
@@ -161,10 +137,10 @@ export const MemoryAskContract = defineContract({
         answer: z.string(),
         citations: z.array(z.string()),
         abstained: z.boolean(),
-        // Live finding 2026-06-11: every abstain branch (dialectic not wired,
-        // empty recall, synthesis abstain) returned the IDENTICAL bare sentinel —
-        // an infrastructure absence was indistinguishable from a genuine "no
-        // data" answer. Present ONLY when abstained:true. Values:
+        // Distinguishes the abstain branches (dialectic not wired, empty recall,
+        // synthesis abstain) — without it every branch would return the IDENTICAL
+        // bare sentinel, making an infrastructure absence indistinguishable from a
+        // genuine "no data" answer. Present ONLY when abstained:true. Values:
         //   "dialectic_unavailable" — seam/recall factory not wired (config/key)
         //   "no_agent_scope"        — no caller agent scope and no default agent
         //   "empty_recall"          — recall ran and returned nothing
@@ -206,14 +182,13 @@ export const MemoryGetFileContract = defineContract({
 /**
  * `memory.store` — write a memory entry. `scopes:["rpc"]` — AGENT-REACHABLE:
  * the agent `memory_store` tool is the primary caller, where the trust level
- * defaults to `learned`. (Was `scopes:["admin"]`, the MD-02 deny-by-origin
- * regression: `["admin"]` put it in `ADMIN_METHODS` so the `assertNotAgentOrigin`
- * chokepoint threw "Control-plane method memory.store is not reachable from an
+ * defaults to `learned`. The scope must NOT be `["admin"]`: that would place
+ * the method in `ADMIN_METHODS`, and the `assertNotAgentOrigin` chokepoint
+ * would throw "Control-plane method memory.store is not reachable from an
  * agent origin" for the agent's `_agentId`-bearing call — the `memory_store`
- * tool could not store anything. Re-scoped admin→rpc 2026-06-24, matching the
- * earlier `message.send`/`skills.*`/`session.list` fixes; guarded by
- * `test/architecture/agent-memory-tools-deny-by-origin.test.ts`.) The handler
- * still routes on the dispatcher-injected `_trustLevel`:
+ * tool could not store anything (guarded by
+ * `test/architecture/agent-memory-tools-deny-by-origin.test.ts`). The handler
+ * routes on the dispatcher-injected `_trustLevel`:
  *   - `_trustLevel === "admin"` (operator path): operator-attributed (channel: web-console), may override trust to learned/external.
  *   - Otherwise (agent path): agent-attributed (channel: agent-tool), trust defaults to `learned` (never `system`).
  *
@@ -250,10 +225,8 @@ export const MemoryStoreContract = defineContract({
  * embeddedEntries, dbSizeBytes, etc.) and is modelled with a loose
  * record to avoid pinning the underlying impl's wire format.
  *
- * The CLI's `memory stats` subcommand currently invokes the
- * gateway-adapter `memory.inspect` (which fans out to a different code
- * path), NOT this handler — see the gateway-adapter shim caveat in the
- * file header.
+ * The CLI's `memory stats` subcommand routes through this contract
+ * (via `callTyped`), folding recall counters into the same view.
  */
 export const MemoryStatsContract = defineContract({
     method: "memory.stats",
@@ -391,16 +364,6 @@ export const MemoryExportContract = defineContract({
     scopes: ["admin"],
 });
 // ===========================================================================
-// --- context-handlers.ts (REMOVED in v2.12) ---
-//
-// The 7 `Context*Contract` definitions (context.search / .inspect / .recall /
-// .expand / .conversations / .tree / .searchByConversation) were removed in
-// v2.12 (Phase 126) along with the DAG context engine + its daemon handlers
-// (Plan 03) + the CLI memory search/inspect rewire (fail-closed, this plan).
-// The governed context-expansion RPC surface is reintroduced fresh by the LCD
-// engine (Phase 131).
-// ===========================================================================
-// ===========================================================================
 // --- memory-handlers.ts (diagnostic surface) ---
 //
 // The four admin-scoped memory-diagnostic contracts (memory.recall_trace /
@@ -410,13 +373,6 @@ export const MemoryExportContract = defineContract({
 // architecture cap (file-size.test.ts). They are re-exported below so every
 // existing `from "./memory.js"` import — and the api-contracts barrel — still
 // resolves, and so they remain part of the memory domain's public surface.
-//
-// CROSS-WAVE SEAM (now closed): the four contracts are now spread into
-// `MEMORY_CONTRACTS` below (`...MEMORY_DIAGNOSTIC_CONTRACTS`), in the SAME wave
-// that landed their daemon handlers in `memory-handlers.ts`, and the
-// `@contract-deferred-handler` annotations were removed from
-// `./memory-diagnostics.ts`. The bidirectional 1:1 + contract-handler-parity
-// gates remain green by construction (registry ↔ handler set is 1:1).
 // ===========================================================================
 export { MemoryRecallTraceContract, MemoryObservationsContract, MemoryEntitiesContract, MemoryRecallStatsContract, } from "./memory-diagnostics.js";
 // Re-export the locally-imported (for the spread below) diagnostics array so
@@ -432,17 +388,9 @@ export { MEMORY_DIAGNOSTIC_CONTRACTS };
  * The grouping below is documentation-only (the bidirectional 1:1 test
  * treats the tuple as an unordered set).
  *
- * `MEMORY_DIAGNOSTIC_CONTRACTS` (the four diagnostic
- * contracts) is now spread in — in the SAME wave that landed the matching
- * `[Contract.method]:` daemon handlers in `memory-handlers.ts` — so the
- * `API_CONTRACTS` registry ↔ handler set stays 1:1 (the cross-wave seam is
- * closed; the `@contract-deferred-handler` annotations were
- * removed in the same diff).
- *
- * `MemoryAskContract` (the dialectic memory.ask surface) is
- * now spread in — in the SAME diff that landed its `[MemoryAskContract.method]:`
- * handler in `memory-handlers.ts` — so the registry ↔ handler set stays 1:1 and
- * the `@contract-deferred-handler` tag was removed in the same diff.
+ * Every contract spread in here has a matching `[Contract.method]:` daemon
+ * handler in `memory-handlers.ts`, so the `API_CONTRACTS` registry ↔ handler
+ * set stays 1:1.
  */
 export const MEMORY_CONTRACTS = [
     // --- memory-handlers.ts ---
@@ -461,6 +409,4 @@ export const MEMORY_CONTRACTS = [
     ...MEMORY_PINNING_CONTRACTS,
     // --- memory-handlers.ts (diagnostic surface) ---
     ...MEMORY_DIAGNOSTIC_CONTRACTS,
-    // NOTE: the 7 context.* contracts (context-handlers.ts) were removed in v2.12
-    // (Phase 126) with the DAG context engine; reintroduced fresh by LCD (Phase 131).
 ];