@remnic/core 9.3.648 → 9.3.650

package/dist/access-cli.js

@@ -1,6 +1,6 @@
 import {
   Orchestrator
-} from "./chunk-TWVRDGTX.js";
+} from "./chunk-23RYLGYA.js";
 import "./chunk-DDRNDPX4.js";
 import "./chunk-7HYPN2GC.js";
 import "./chunk-666A3MOW.js";
@@ -79,7 +79,7 @@ import "./chunk-UMKPSD35.js";
 import "./chunk-W4RVMTHR.js";
 import "./chunk-4BISW7RX.js";
 import "./chunk-ZRWB5D4H.js";
-import "./chunk-XUGQQPGO.js";
+import "./chunk-AGRPGAKR.js";
 import "./chunk-S4DDLTPX.js";
 import "./chunk-SFQ6QNL7.js";
 import "./chunk-D6WVJIS3.js";
@@ -122,7 +122,7 @@ import "./chunk-OADWQ5CR.js";
 import "./chunk-7WV3F5DQ.js";
 import {
   EngramAccessService
-} from "./chunk-5ETA6OAS.js";
+} from "./chunk-YAFSTKTH.js";
 import "./chunk-GDASG7NC.js";
 import "./chunk-GDB4J2H3.js";
 import "./chunk-NT5TINK5.js";
@@ -131,7 +131,7 @@ import "./chunk-SOBJ6NEY.js";
 import "./chunk-BT7NVCML.js";
 import "./chunk-H7XKCNR6.js";
 import "./chunk-UMTG2BN2.js";
-import "./chunk-6GIKAUTN.js";
+import "./chunk-MMJANTJX.js";
 import "./chunk-5RIRL3XL.js";
 import "./chunk-JGSKJHF7.js";
 import "./chunk-FF4KLI5W.js";

package/dist/access-http.d.ts

@@ -1,5 +1,5 @@
 import { IncomingMessage } from 'node:http';
-import { E as EngramAccessService } from './access-service-DFXIlGvZ.js';
+import { E as EngramAccessService } from './access-service-DIZRHQ7Q.js';
 import { ResolvedIdentity } from './adapters/types.js';
 import { AdapterRegistry } from './adapters/registry.js';
 import './storage.js';
@@ -21,7 +21,7 @@ import './user-model.js';
 import './recall-audit-anomaly.js';
 import './recall-audit.js';
 import './explicit-capture.js';
-import './orchestrator-DEQW9j0Z.js';
+import './orchestrator-CX-oqwJq.js';
 import './briefing.js';
 import './buffer.js';
 import './search/port.js';

package/dist/access-http.js

@@ -1,6 +1,6 @@
 import {
   EngramAccessHttpServer
-} from "./chunk-CNRZ6WJU.js";
+} from "./chunk-3IJEQWQX.js";
 import "./chunk-SEDEKFYQ.js";
 import "./chunk-RKNJBZ55.js";
 import "./chunk-J64TK33U.js";
@@ -9,10 +9,10 @@ import "./chunk-42NQ7AVG.js";
 import "./chunk-TMSXWOBZ.js";
 import "./chunk-7RXCMVFQ.js";
 import "./chunk-7WV3F5DQ.js";
-import "./chunk-FUXV6HSO.js";
+import "./chunk-TVOPSKOK.js";
 import "./chunk-T4WDJPEZ.js";
 import "./chunk-D24OXEPB.js";
-import "./chunk-5ETA6OAS.js";
+import "./chunk-YAFSTKTH.js";
 import "./chunk-GDASG7NC.js";
 import "./chunk-GDB4J2H3.js";
 import "./chunk-NT5TINK5.js";
@@ -21,7 +21,7 @@ import "./chunk-SOBJ6NEY.js";
 import "./chunk-BT7NVCML.js";
 import "./chunk-H7XKCNR6.js";
 import "./chunk-UMTG2BN2.js";
-import "./chunk-6GIKAUTN.js";
+import "./chunk-MMJANTJX.js";
 import "./chunk-5RIRL3XL.js";
 import "./chunk-JGSKJHF7.js";
 import "./chunk-FF4KLI5W.js";

package/dist/access-mcp.d.ts

@@ -1,5 +1,5 @@
 import { Readable, Writable } from 'node:stream';
-import { E as EngramAccessService } from './access-service-DFXIlGvZ.js';
+import { E as EngramAccessService } from './access-service-DIZRHQ7Q.js';
 import './storage.js';
 import './page-versioning.js';
 import './consolidation-operator.js';
@@ -19,7 +19,7 @@ import './user-model.js';
 import './recall-audit-anomaly.js';
 import './recall-audit.js';
 import './explicit-capture.js';
-import './orchestrator-DEQW9j0Z.js';
+import './orchestrator-CX-oqwJq.js';
 import './briefing.js';
 import './buffer.js';
 import './search/port.js';

package/dist/access-mcp.js

@@ -1,9 +1,9 @@
 import {
   EngramMcpServer
-} from "./chunk-FUXV6HSO.js";
+} from "./chunk-TVOPSKOK.js";
 import "./chunk-T4WDJPEZ.js";
 import "./chunk-D24OXEPB.js";
-import "./chunk-5ETA6OAS.js";
+import "./chunk-YAFSTKTH.js";
 import "./chunk-GDASG7NC.js";
 import "./chunk-GDB4J2H3.js";
 import "./chunk-NT5TINK5.js";
@@ -12,7 +12,7 @@ import "./chunk-SOBJ6NEY.js";
 import "./chunk-BT7NVCML.js";
 import "./chunk-H7XKCNR6.js";
 import "./chunk-UMTG2BN2.js";
-import "./chunk-6GIKAUTN.js";
+import "./chunk-MMJANTJX.js";
 import "./chunk-5RIRL3XL.js";
 import "./chunk-JGSKJHF7.js";
 import "./chunk-FF4KLI5W.js";

package/dist/{access-service-DFXIlGvZ.d.ts → access-service-DIZRHQ7Q.d.ts}

@@ -6,7 +6,7 @@ import { AnomalyDetectorResult } from './recall-audit-anomaly.js';
 import { ExplicitCaptureInput } from './explicit-capture.js';
 import { BudgetDecision } from './cross-namespace-budget.js';
 import { readMemoryGovernanceRunArtifact } from './maintenance/memory-governance.js';
-import { O as Orchestrator, I as IntentDebugSnapshot, G as GraphRecallSnapshot, P as PatternReinforcementResult, W as WearablesService } from './orchestrator-DEQW9j0Z.js';
+import { O as Orchestrator, I as IntentDebugSnapshot, G as GraphRecallSnapshot, P as PatternReinforcementResult, W as WearablesService } from './orchestrator-CX-oqwJq.js';
 import { LiveConnectorsRunSummary } from './live-connectors-runner.js';
 import { LastRecallSnapshot } from './recall-state.js';
 import { GraphSnapshotRequest, GraphSnapshotResponse } from './graph-snapshot.js';
@@ -654,6 +654,53 @@ interface CodingScopedWriteInput {
     cwd?: string;
     projectTag?: string;
 }
+/**
+ * Internal, single-resolution plan describing the effective memory scope for a
+ * write-producing access request (#1495, seed for epic #1494). One plan is
+ * resolved per request and EVERY side effect (LCM archival, extraction replay,
+ * objective-state snapshot, response) consumes the same `writeNamespace`, so an
+ * observed turn and its extracted memories never drift away from the namespace a
+ * same-session project-scoped recall searches (rule 39 / 42).
+ *
+ * The resolver that produces this is READ-ONLY with respect to namespace
+ * authorization: an explicit namespace is authorized through the existing
+ * `canWriteNamespace` policy path, and a coding overlay is always REBUILT from
+ * the authenticated principal's base — never accepted as a caller string — so a
+ * caller can never reach another principal's overlay by forging an
+ * overlay-shaped namespace (rule 42 / 47 / 48).
+ */
+interface MemoryScopePlan {
+    /** Resolved request principal (auth precedence applied), or undefined. */
+    principal?: string;
+    /** Explicit `namespace` supplied by the caller, if any (already authorized). */
+    explicitNamespace?: string;
+    /** Principal self base namespace before any coding overlay. */
+    baseNamespace: string;
+    /** Effective write namespace — what every side effect must use. */
+    writeNamespace: string;
+    /**
+     * Effective namespace the objective-state snapshot writer must target.
+     *
+     * Objective-state has a STRICTER, pre-#1495 contract than the LCM/extraction
+     * write path (#928): an IMPLICIT (no explicit `namespace`) snapshot is based
+     * on the PRINCIPAL SELF namespace (`defaultNamespaceForPrincipal`) and is
+     * authorized against THAT base (rule 48, least-privilege) — never silently
+     * routed to `config.defaultNamespace`. Only the LCM/extraction/response path
+     * collapses an unqualified write to `config.defaultNamespace` (memory_store
+     * parity, rule 39). With an explicit namespace, or once a coding overlay
+     * applies, both targets converge: `objectiveStateNamespace === writeNamespace`.
+     *
+     * Keeping the two as separate fields of ONE plan preserves rule 22 (single
+     * resolution point) while honoring each consumer's historical contract.
+     */
+    objectiveStateNamespace: string;
+    /** Namespaces a same-session recall would read (cheap subset). */
+    readNamespaces: string[];
+    /** Whether the coding overlay changed the base namespace. */
+    codingOverlayApplied: boolean;
+    /** Non-fatal diagnostics surfaced during resolution. */
+    warnings: string[];
+}
 interface EngramAccessMemoryStoreRequest extends EngramAccessWriteEnvelope, ExplicitCaptureInput, CodingScopedWriteInput {
 }
 interface EngramAccessSuggestionSubmitRequest extends EngramAccessWriteEnvelope, ExplicitCaptureInput, CodingScopedWriteInput {
@@ -697,10 +744,44 @@ interface EngramAccessObserveRequest {
      */
     projectTag?: string;
 }
+/**
+ * Additive diagnostic view of the effective {@link MemoryScopePlan} resolved for
+ * an `observe` request (#1495 / epic #1494). Lets callers and tests inspect
+ * which namespace the operation actually wrote to without changing the
+ * backward-compatible `namespace` field. Purely informational — never gates
+ * authorization.
+ */
+interface EngramAccessScopeDebug {
+    /** Resolved principal, or `undefined` when none could be derived. */
+    principal?: string;
+    /** Explicit `namespace` from the request, if one was supplied. */
+    explicitNamespace?: string;
+    /** Principal self base before any coding overlay. */
+    baseNamespace: string;
+    /** Effective write namespace every side effect of the request uses. */
+    writeNamespace: string;
+    /** Whether the coding (project/branch) overlay changed the base namespace. */
+    codingOverlayApplied: boolean;
+    /** Namespaces a same-session recall would read, when cheap to compute. */
+    readNamespaces?: string[];
+}
 interface EngramAccessObserveResponse {
     accepted: number;
     sessionKey: string;
+    /**
+     * Backward-compatible base writable namespace (pre-#1495 semantics). Kept
+     * unchanged so existing callers/tests are not broken. The namespace the
+     * operation ACTUALLY wrote to is {@link EngramAccessObserveResponse.effectiveNamespace}.
+     */
     namespace: string;
+    /**
+     * Effective write namespace every memory-producing side effect of this
+     * request used (LCM archival, extraction replay, objective-state snapshot).
+     * Equals the namespace a same-session project-scoped recall searches (#1495).
+     */
+    effectiveNamespace: string;
+    /** Additive diagnostic view of the resolved scope plan (#1495). */
+    scopeDebug?: EngramAccessScopeDebug;
     lcmArchived: boolean;
     extractionQueued: boolean;
 }
@@ -825,6 +906,31 @@ declare class EngramAccessService {
      * never fails a write — there is no namespace to "pin".
      */
     private resolveCodingScopedWriteNamespace;
+    /**
+     * Resolve ONE effective memory scope plan for a write-producing request
+     * (#1495 / seed for epic #1494). The returned {@link MemoryScopePlan} is the
+     * single source of truth `observe` (and, later, other write surfaces) consume
+     * so every side effect lands in `plan.writeNamespace`.
+     *
+     * Authorization mirrors {@link resolveCodingScopedWriteNamespace} EXACTLY so
+     * `observe`'s scoping is identical to `memory_store`/`suggestion_submit`
+     * (rule 39 — feature gates identical across code paths):
+     *  - an explicit `namespace` always wins and is authorized strictly through
+     *    `resolveWritableNamespace` → `canWriteNamespace`; an overlay-shaped string
+     *    is never a writable target (rule 42 / 47 / 48);
+     *  - with NO overlay, the base stays on `config.defaultNamespace` (pre-#1434
+     *    behavior), auth-checked;
+     *  - WITH an overlay, the base is the principal self namespace and the overlay
+     *    is REBUILT from that authorized base — never accepted as a caller string.
+     *
+     * READ-ONLY: this never mutates session coding context. Callers that need the
+     * `cwd`/`projectTag` bound to the session (so a later bare recall is scoped)
+     * must attach it via `maybeAttachCodingContext` BEFORE calling this, which
+     * also preserves the no-orphan-context guard (attach only after auth passes).
+     * The overlay here reads the session's attached context first (matching recall
+     * precedence), falling back to the per-call `cwd`/`projectTag`.
+     */
+    private resolveMemoryScopePlan;
     private objectiveStateStoreLocationForNamespace;
     private resolveReadableNamespace;
     private resolveReadableNamespacesForSearch;
@@ -1080,6 +1186,153 @@ declare class EngramAccessService {
     private serializeMemorySummary;
     observe(request: EngramAccessObserveRequest): Promise<EngramAccessObserveResponse>;
     lcmSearch(request: EngramAccessLcmSearchRequest): Promise<EngramAccessLcmSearchResponse>;
+    /**
+     * Resolve the LCM `session_id` a same-session READER (compaction flush/record,
+     * `lcmSearch`, raw-excerpt lookup) must target so it matches the key `observe`
+     * archived under (#1495 thread 2 + #1505 round 3, rule 42). One helper for
+     * EVERY access-surface LCM read so the read key cannot drift from the write key
+     * (rule 22).
+     *
+     * Precedence mirrors `observe`'s effective write namespace:
+     *  - With an explicit `request.namespace`, use the already-authorized
+     *    `resolvedNamespace` (the overlay never applies to an explicit write).
+     *  - With NO explicit namespace, an auto-scoped session was archived under
+     *    its coding-overlay namespace, so overlay the session's bound coding
+     *    context onto the principal self base — the SAME resolution
+     *    `resolveMemoryScopePlan`/recall use. `applyCodingNamespaceOverlay`
+     *    returns the base unchanged when projectScope/namespaces are off or no
+     *    context is bound, so single-store / no-overlay flows collapse to the raw
+     *    sessionKey exactly as before.
+     *
+     * Then encode the `${namespace}:${sessionKey}` prefix via the shared helper
+     * so the read key is byte-for-byte what the LCM write and the recall readers
+     * use.
+     */
+    /**
+     * Resolve the effective LCM NAMESPACE a same-session operation must prefix
+     * with (the namespace half of {@link resolveLcmReadSessionKey}). Split out so
+     * `lcmSearch` can apply ONE namespace to BOTH its `sessionKey` and its
+     * `sessionPrefix` — the prefix is a search fragment, not a real session, so its
+     * own coding context can't be looked up; it must inherit the namespace resolved
+     * from the real session (`sessionKeyForOverlay`).
+     *
+     * `purpose` selects the AUTHORIZATION gate applied before honouring the
+     * coding overlay (#1505 round 3 + round 4, codex P2):
+     *
+     *  - `"read"` (`lcmSearch` / raw-excerpt recall): the overlay rows are only
+     *    visible when the principal SELF base is in the READABLE RECALL SET — the
+     *    same gate the orchestrator's `lcmReadNamespaceForSession` and the recall
+     *    namespace set use (`recallNamespacesForPrincipal`, gated by both
+     *    `defaultRecallNamespaces.includes("self")` AND `canReadNamespace`). A
+     *    caller that passed the default read check must NOT receive
+     *    `<principal>-project-*` rows the policy never granted (cross-tenant read
+     *    leak). When the self base is not readable, keep the just-authorized
+     *    namespace (collapses to the raw key on the default store).
+     *
+     *  - `"write"` (`lcmCompactionFlush` / `lcmCompactionRecord`): these are
+     *    write/maintenance operations on the SAME queue `observe` just wrote, so
+     *    the gate must mirror observe's WRITE authorization (`canWriteNamespace`
+     *    on the self base), NOT readability. A principal that can WRITE but not
+     *    READ its self namespace (or whose `defaultRecallNamespaces` omits `self`)
+     *    archived under the overlay key via `observe`; gating compaction by
+     *    readability would fall back to the default/raw key and leave that queue
+     *    never flushed/recorded (round-4 codex P2). Write-authorized ⇒ overlay
+     *    key, matching the observe write key (rule 42 read/write parity; rule 39
+     *    identical gates across paths).
+     */
+    private resolveLcmReadNamespace;
+    /**
+     * Resolve the namespace the raw-disclosure excerpt lookup
+     * ({@link fetchRawExcerpts}) must prefix its LCM `session_id` with (#1505
+     * thread 2f7). Raw disclosure reads the SAME LCM archive `lcmSearch` and the
+     * in-prompt LCM sections read, so it MUST pass through the identical
+     * read-authorization gate — NOT `snapshot.namespace`, which records the
+     * effective WRITE/overlay namespace (`<principal>-project-*`) even when the
+     * principal can WRITE but not READ its self base (or `defaultRecallNamespaces`
+     * omits `self`). Routing through `resolveLcmReadNamespace(..., "read")` makes
+     * raw disclosure fall back to the default store exactly like normal recall +
+     * `lcmSearch`, so it never attaches overlay transcript rows the read gate
+     * excludes (cross-tenant read leak). Collapses to the default store / raw
+     * sessionKey for single-store / no-overlay / explicit-default flows, so
+     * single-user recall is byte-for-byte unchanged.
+     *
+     * Returns `undefined` when NO readable LCM namespace exists for an IMPLICIT
+     * (no explicit `namespace`) raw recall — i.e. a restrictive `default` READ
+     * policy denies the principal `default` AND no overlay/self namespace is
+     * readable. In that case the caller emits NO excerpts rather than throwing
+     * `namespace is not readable: default` (#1505 thread NBHWz): normal recall
+     * still succeeds via `recallNamespacesForPrincipal`, so `disclosure: "raw"`
+     * must degrade gracefully (empty excerpts), never pre-authorize `default`.
+     *
+     * IMPLICIT-namespace fallback selection derives from the ALREADY
+     * read-authorized recall namespace set (`recallNamespacesForPrincipal` +
+     * `canReadNamespace`) — the principal's self base when it is in the readable
+     * recall set, else `config.defaultNamespace` ONLY when the principal may read
+     * it. It NEVER pre-authorizes `default`. An EXPLICIT `namespace` is still
+     * authorized strictly via `resolveReadableNamespace` (explicit reads must pass
+     * the ACL — no behavior change).
+     */
+    private resolveRawExcerptReadNamespace;
+    /**
+     * The base `resolvedNamespace` an IMPLICIT (no explicit `namespace`)
+     * same-session LCM READER (`resolveRawExcerptReadNamespace`, `lcmSearch`)
+     * passes into {@link resolveLcmReadNamespace} — WITHOUT pre-authorizing
+     * `default` (#1505 thread NBHWz). It decides PROCEED vs SUPPRESS only; the
+     * actual LCM prefix is then resolved by `resolveLcmReadNamespace`, which
+     * mirrors the orchestrator's `lcmReadNamespaceForSession` EXACTLY (rule 39 /
+     * 42): the coding overlay when the principal SELF base is in the readable
+     * recall set, else `config.defaultNamespace` (the raw key).
+     *
+     * Returns `config.defaultNamespace` (PROCEED) whenever the principal has ANY
+     * readable LCM access — either `default` itself is readable, OR a coding
+     * overlay / self base is in the readable recall set. The returned value is
+     * ALWAYS `config.defaultNamespace`, NEVER an arbitrary readable recall
+     * namespace (e.g. `shared`): `resolveLcmReadNamespace` returns this fallback
+     * verbatim only on the overlay-applies-but-self-unreadable branch, where the
+     * orchestrator collapses to the default store — so returning anything but the
+     * default store there would prefix LCM reads with `shared:sessionKey` while
+     * in-prompt recall uses the raw `sessionKey`, diverging the two (cursor
+     * "LCM read gate wrong fallback").
+     *
+     * Returns `undefined` (SUPPRESS) only when NO readable LCM namespace exists —
+     * a restrictive `default` READ policy AND no readable overlay/self — so the
+     * caller emits NO rows instead of throwing `namespace is not readable:
+     * default`. Normal recall still succeeds through the readable self namespace.
+     *
+     * Single-store / namespaces-disabled deployments resolve to
+     * `config.defaultNamespace`, keeping single-user recall byte-for-byte
+     * unchanged.
+     */
+    private resolveImplicitLcmReadFallbackNamespace;
+    private resolveLcmReadSessionKey;
+    /**
+     * Resolve the ORDERED, read-authorized set of LCM `session_id`s a same-session
+     * READER (`lcmSearch`, raw-excerpt disclosure) must query so it matches every
+     * key `observe` archived under across the coding scope (#1505 thread "Include
+     * coding fallback namespaces in LCM reads").
+     *
+     * Mirrors the orchestrator recall path exactly (rule 39): `observe` archives
+     * each turn under `${effectiveNamespace}:${sessionKey}` for whichever namespace
+     * was effective at write time, and normal QMD/file recall searches the primary
+     * coding-overlay namespace AND `codingOverlay.readFallbacks` (project → root).
+     * A single overlay key therefore MISSES rows a branch-scoped session archived at
+     * project/root scope. This returns the primary overlay LCM key first, then one
+     * per read fallback, deduped + ordered so the caller can short-circuit on the
+     * first hit.
+     *
+     * READ-AUTHORIZATION (preserved from the round-3..5 `resolveLcmReadNamespace`
+     * "read" gate; rule 42 / 48): the overlay + fallbacks are `<principal>-project-*`
+     * sub-namespaces authorized transitively by the principal SELF base. They are
+     * included ONLY when the self base is in the readable recall set
+     * (`recallNamespacesForPrincipal`). When the self base is NOT readable (write-
+     * only / self-omitted principal), or when an explicit namespace was supplied,
+     * or no overlay applies, this collapses to the single key
+     * {@link resolveLcmReadSessionKey} returns — byte-for-byte the prior behavior
+     * (single-store / no-overlay flows stay the raw `sessionKey`). No
+     * `<principal>-project-*` key is ever searched for an unauthorized reader (no
+     * cross-tenant read leak).
+     */
+    private resolveLcmReadSessionIds;
     lcmCompactionFlush(request: EngramAccessLcmCompactionFlushRequest): Promise<EngramAccessLcmCompactionFlushResponse>;
     lcmCompactionRecord(request: EngramAccessLcmCompactionRecordRequest): Promise<EngramAccessLcmCompactionRecordResponse>;
     continuityAuditGenerate(request: {
@@ -1582,4 +1835,4 @@ declare class EngramAccessService {
     }): Promise<Awaited<ReturnType<WearablesService["transcriptMemories"]>>>;
 }
 
-export { type EngramAccessReviewDispositionRequest as $, type EngramAccessMemoryBrowseRequest as A, type EngramAccessMemoryBrowseResponse as B, type CodingScopedWriteInput as C, type EngramAccessMemoryRecord as D, EngramAccessService as E, type EngramAccessMemoryResponse as F, type EngramAccessMemoryStoreRequest as G, type EngramAccessMemorySummary as H, type EngramAccessObserveMessage as I, type EngramAccessObserveRequest as J, type EngramAccessObserveResponse as K, type EngramAccessOfflineSyncApplyFileContentRequest as L, type EngramAccessOfflineSyncApplyFileContentResponse as M, type EngramAccessOfflineSyncApplyRequest as N, type EngramAccessOfflineSyncApplyResponse as O, type ProcedureStatsConfigSnapshot as P, type EngramAccessOfflineSyncFileContentRequest as Q, type EngramAccessOfflineSyncFileContentResponse as R, type EngramAccessOfflineSyncFilesRequest as S, type EngramAccessOfflineSyncFilesResponse as T, type EngramAccessOfflineSyncSnapshotRequest as U, type EngramAccessOfflineSyncSnapshotResponse as V, type EngramAccessOfflineSyncSnapshotStreamResponse as W, type EngramAccessQualityResponse as X, type EngramAccessRecallExplainRequest as Y, type EngramAccessRecallExplainResponse as Z, type EngramAccessRecallRequest as _, type EngramAccessRecallResponse as a, type EngramAccessReviewDispositionResponse as a0, type EngramAccessReviewQueueResponse as a1, type EngramAccessSetCodingContextRequest as a2, type EngramAccessSuggestionSubmitRequest as a3, type EngramAccessTimelineResponse as a4, type EngramAccessTrustZoneBrowseRequest as a5, type EngramAccessTrustZoneBrowseResponse as a6, type EngramAccessTrustZoneDemoSeedRequest as a7, type EngramAccessTrustZoneDemoSeedResponse as a8, type EngramAccessTrustZonePromoteRequest as a9, type EngramAccessTrustZonePromoteResponse as aa, type EngramAccessTrustZoneRecordSummary as ab, type EngramAccessTrustZoneStatusResponse as ac, type EngramAccessWriteEnvelope as ad, type EngramAccessWriteResponse as ae, shapeMemorySummary as af, EngramAccessInputError as b, type ProcedureStatsRecent as c, type ProcedureStatsReport as d, type ProcedureStatusCounts as e, computeProcedureStats as f, formatProcedureStatsText as g, ENGRAM_ACCESS_WRITE_SCHEMA_VERSION as h, type EngramAccessActionConfidenceRequest as i, type EngramAccessActionConfidenceResponse as j, type EngramAccessBriefingRequest as k, type EngramAccessBriefingResponse as l, type EngramAccessCapsuleListResponse as m, type EngramAccessDaySummaryRequest as n, type EngramAccessEntityListResponse as o, type EngramAccessEntityResponse as p, type EngramAccessEntitySummary as q, type EngramAccessHealthResponse as r, type EngramAccessLcmCompactionFlushRequest as s, type EngramAccessLcmCompactionFlushResponse as t, type EngramAccessLcmCompactionRecordRequest as u, type EngramAccessLcmCompactionRecordResponse as v, type EngramAccessLcmSearchRequest as w, type EngramAccessLcmSearchResponse as x, type EngramAccessLcmStatusResponse as y, type EngramAccessMaintenanceResponse as z };
+export { type EngramAccessReviewDispositionRequest as $, type EngramAccessMemoryBrowseRequest as A, type EngramAccessMemoryBrowseResponse as B, type CodingScopedWriteInput as C, type EngramAccessMemoryRecord as D, EngramAccessService as E, type EngramAccessMemoryResponse as F, type EngramAccessMemoryStoreRequest as G, type EngramAccessMemorySummary as H, type EngramAccessObserveMessage as I, type EngramAccessObserveRequest as J, type EngramAccessObserveResponse as K, type EngramAccessOfflineSyncApplyFileContentRequest as L, type EngramAccessOfflineSyncApplyFileContentResponse as M, type EngramAccessOfflineSyncApplyRequest as N, type EngramAccessOfflineSyncApplyResponse as O, type ProcedureStatsConfigSnapshot as P, type EngramAccessOfflineSyncFileContentRequest as Q, type EngramAccessOfflineSyncFileContentResponse as R, type EngramAccessOfflineSyncFilesRequest as S, type EngramAccessOfflineSyncFilesResponse as T, type EngramAccessOfflineSyncSnapshotRequest as U, type EngramAccessOfflineSyncSnapshotResponse as V, type EngramAccessOfflineSyncSnapshotStreamResponse as W, type EngramAccessQualityResponse as X, type EngramAccessRecallExplainRequest as Y, type EngramAccessRecallExplainResponse as Z, type EngramAccessRecallRequest as _, type EngramAccessRecallResponse as a, type EngramAccessReviewDispositionResponse as a0, type EngramAccessReviewQueueResponse as a1, type EngramAccessScopeDebug as a2, type EngramAccessSetCodingContextRequest as a3, type EngramAccessSuggestionSubmitRequest as a4, type EngramAccessTimelineResponse as a5, type EngramAccessTrustZoneBrowseRequest as a6, type EngramAccessTrustZoneBrowseResponse as a7, type EngramAccessTrustZoneDemoSeedRequest as a8, type EngramAccessTrustZoneDemoSeedResponse as a9, type EngramAccessTrustZonePromoteRequest as aa, type EngramAccessTrustZonePromoteResponse as ab, type EngramAccessTrustZoneRecordSummary as ac, type EngramAccessTrustZoneStatusResponse as ad, type EngramAccessWriteEnvelope as ae, type EngramAccessWriteResponse as af, type MemoryScopePlan as ag, shapeMemorySummary as ah, EngramAccessInputError as b, type ProcedureStatsRecent as c, type ProcedureStatsReport as d, type ProcedureStatusCounts as e, computeProcedureStats as f, formatProcedureStatsText as g, ENGRAM_ACCESS_WRITE_SCHEMA_VERSION as h, type EngramAccessActionConfidenceRequest as i, type EngramAccessActionConfidenceResponse as j, type EngramAccessBriefingRequest as k, type EngramAccessBriefingResponse as l, type EngramAccessCapsuleListResponse as m, type EngramAccessDaySummaryRequest as n, type EngramAccessEntityListResponse as o, type EngramAccessEntityResponse as p, type EngramAccessEntitySummary as q, type EngramAccessHealthResponse as r, type EngramAccessLcmCompactionFlushRequest as s, type EngramAccessLcmCompactionFlushResponse as t, type EngramAccessLcmCompactionRecordRequest as u, type EngramAccessLcmCompactionRecordResponse as v, type EngramAccessLcmSearchRequest as w, type EngramAccessLcmSearchResponse as x, type EngramAccessLcmStatusResponse as y, type EngramAccessMaintenanceResponse as z };

package/dist/access-service.d.ts

@@ -1,13 +1,13 @@
 import './storage.js';
 import './types-B1VHaf2w.js';
-export { C as CodingScopedWriteInput, h as ENGRAM_ACCESS_WRITE_SCHEMA_VERSION, i as EngramAccessActionConfidenceRequest, j as EngramAccessActionConfidenceResponse, k as EngramAccessBriefingRequest, l as EngramAccessBriefingResponse, m as EngramAccessCapsuleListResponse, n as EngramAccessDaySummaryRequest, o as EngramAccessEntityListResponse, p as EngramAccessEntityResponse, q as EngramAccessEntitySummary, r as EngramAccessHealthResponse, b as EngramAccessInputError, s as EngramAccessLcmCompactionFlushRequest, t as EngramAccessLcmCompactionFlushResponse, u as EngramAccessLcmCompactionRecordRequest, v as EngramAccessLcmCompactionRecordResponse, w as EngramAccessLcmSearchRequest, x as EngramAccessLcmSearchResponse, y as EngramAccessLcmStatusResponse, z as EngramAccessMaintenanceResponse, A as EngramAccessMemoryBrowseRequest, B as EngramAccessMemoryBrowseResponse, D as EngramAccessMemoryRecord, F as EngramAccessMemoryResponse, G as EngramAccessMemoryStoreRequest, H as EngramAccessMemorySummary, I as EngramAccessObserveMessage, J as EngramAccessObserveRequest, K as EngramAccessObserveResponse, L as EngramAccessOfflineSyncApplyFileContentRequest, M as EngramAccessOfflineSyncApplyFileContentResponse, N as EngramAccessOfflineSyncApplyRequest, O as EngramAccessOfflineSyncApplyResponse, Q as EngramAccessOfflineSyncFileContentRequest, R as EngramAccessOfflineSyncFileContentResponse, S as EngramAccessOfflineSyncFilesRequest, T as EngramAccessOfflineSyncFilesResponse, U as EngramAccessOfflineSyncSnapshotRequest, V as EngramAccessOfflineSyncSnapshotResponse, W as EngramAccessOfflineSyncSnapshotStreamResponse, X as EngramAccessQualityResponse, Y as EngramAccessRecallExplainRequest, Z as EngramAccessRecallExplainResponse, _ as EngramAccessRecallRequest, a as EngramAccessRecallResponse, $ as EngramAccessReviewDispositionRequest, a0 as EngramAccessReviewDispositionResponse, a1 as EngramAccessReviewQueueResponse, E as EngramAccessService, a2 as EngramAccessSetCodingContextRequest, a3 as EngramAccessSuggestionSubmitRequest, a4 as EngramAccessTimelineResponse, a5 as EngramAccessTrustZoneBrowseRequest, a6 as EngramAccessTrustZoneBrowseResponse, a7 as EngramAccessTrustZoneDemoSeedRequest, a8 as EngramAccessTrustZoneDemoSeedResponse, a9 as EngramAccessTrustZonePromoteRequest, aa as EngramAccessTrustZonePromoteResponse, ab as EngramAccessTrustZoneRecordSummary, ac as EngramAccessTrustZoneStatusResponse, ad as EngramAccessWriteEnvelope, ae as EngramAccessWriteResponse, af as shapeMemorySummary } from './access-service-DFXIlGvZ.js';
+export { C as CodingScopedWriteInput, h as ENGRAM_ACCESS_WRITE_SCHEMA_VERSION, i as EngramAccessActionConfidenceRequest, j as EngramAccessActionConfidenceResponse, k as EngramAccessBriefingRequest, l as EngramAccessBriefingResponse, m as EngramAccessCapsuleListResponse, n as EngramAccessDaySummaryRequest, o as EngramAccessEntityListResponse, p as EngramAccessEntityResponse, q as EngramAccessEntitySummary, r as EngramAccessHealthResponse, b as EngramAccessInputError, s as EngramAccessLcmCompactionFlushRequest, t as EngramAccessLcmCompactionFlushResponse, u as EngramAccessLcmCompactionRecordRequest, v as EngramAccessLcmCompactionRecordResponse, w as EngramAccessLcmSearchRequest, x as EngramAccessLcmSearchResponse, y as EngramAccessLcmStatusResponse, z as EngramAccessMaintenanceResponse, A as EngramAccessMemoryBrowseRequest, B as EngramAccessMemoryBrowseResponse, D as EngramAccessMemoryRecord, F as EngramAccessMemoryResponse, G as EngramAccessMemoryStoreRequest, H as EngramAccessMemorySummary, I as EngramAccessObserveMessage, J as EngramAccessObserveRequest, K as EngramAccessObserveResponse, L as EngramAccessOfflineSyncApplyFileContentRequest, M as EngramAccessOfflineSyncApplyFileContentResponse, N as EngramAccessOfflineSyncApplyRequest, O as EngramAccessOfflineSyncApplyResponse, Q as EngramAccessOfflineSyncFileContentRequest, R as EngramAccessOfflineSyncFileContentResponse, S as EngramAccessOfflineSyncFilesRequest, T as EngramAccessOfflineSyncFilesResponse, U as EngramAccessOfflineSyncSnapshotRequest, V as EngramAccessOfflineSyncSnapshotResponse, W as EngramAccessOfflineSyncSnapshotStreamResponse, X as EngramAccessQualityResponse, Y as EngramAccessRecallExplainRequest, Z as EngramAccessRecallExplainResponse, _ as EngramAccessRecallRequest, a as EngramAccessRecallResponse, $ as EngramAccessReviewDispositionRequest, a0 as EngramAccessReviewDispositionResponse, a1 as EngramAccessReviewQueueResponse, a2 as EngramAccessScopeDebug, E as EngramAccessService, a3 as EngramAccessSetCodingContextRequest, a4 as EngramAccessSuggestionSubmitRequest, a5 as EngramAccessTimelineResponse, a6 as EngramAccessTrustZoneBrowseRequest, a7 as EngramAccessTrustZoneBrowseResponse, a8 as EngramAccessTrustZoneDemoSeedRequest, a9 as EngramAccessTrustZoneDemoSeedResponse, aa as EngramAccessTrustZonePromoteRequest, ab as EngramAccessTrustZonePromoteResponse, ac as EngramAccessTrustZoneRecordSummary, ad as EngramAccessTrustZoneStatusResponse, ae as EngramAccessWriteEnvelope, af as EngramAccessWriteResponse, ag as MemoryScopePlan, ah as shapeMemorySummary } from './access-service-DIZRHQ7Q.js';
 import './recall-explain-renderer.js';
 import './types-D8yUmSik.js';
 import './recall-audit-anomaly.js';
 import './explicit-capture.js';
 import './cross-namespace-budget.js';
 import './maintenance/memory-governance.js';
-import './orchestrator-DEQW9j0Z.js';
+import './orchestrator-CX-oqwJq.js';
 import './live-connectors-runner.js';
 import './recall-state.js';
 import './graph-snapshot.js';

package/dist/access-service.js

@@ -3,7 +3,7 @@ import {
   EngramAccessInputError,
   EngramAccessService,
   shapeMemorySummary
-} from "./chunk-5ETA6OAS.js";
+} from "./chunk-YAFSTKTH.js";
 import "./chunk-GDASG7NC.js";
 import "./chunk-GDB4J2H3.js";
 import "./chunk-NT5TINK5.js";
@@ -12,7 +12,7 @@ import "./chunk-SOBJ6NEY.js";
 import "./chunk-BT7NVCML.js";
 import "./chunk-H7XKCNR6.js";
 import "./chunk-UMTG2BN2.js";
-import "./chunk-6GIKAUTN.js";
+import "./chunk-MMJANTJX.js";
 import "./chunk-5RIRL3XL.js";
 import "./chunk-JGSKJHF7.js";
 import "./chunk-FF4KLI5W.js";

package/dist/bootstrap.d.ts

@@ -1,5 +1,5 @@
 import { P as PluginConfig } from './types-D8yUmSik.js';
-import { O as Orchestrator } from './orchestrator-DEQW9j0Z.js';
+import { O as Orchestrator } from './orchestrator-CX-oqwJq.js';
 import './types-ByK7T3L6.js';
 import './index-DJ9QWMw-.js';
 import './briefing.js';