@anuma/sdk 5.0.3 → 5.1.0

package/dist/expo/index.d.mts

@@ -407,7 +407,7 @@ type LlmapiResponseReasoning = {
      */
     summary?: string;
 };
-type LlmapiResponseResponse = {
+type LlmapiResponseResponse$1 = {
     /**
      * ClientInjectedTools are tool names the client provided in the original request.
      */
@@ -1234,6 +1234,30 @@ type LlmapiChatCompletionUsage = OpenaiCompletionUsage & {
  * strategies/completions.ts `buildFinalResponse`. See that TODO for the full
  * deprecation plan.
  */
+/**
+ * Add the Responses API's terminal-state fields, which the portal's generated
+ * schema does not declare.
+ *
+ * Without them the two transports are asymmetric: a completions consumer reads
+ * `choices[0].finish_reason` and can see a turn cut off at the output ceiling,
+ * while a Responses consumer has no field to read at all — the truncation the
+ * SDK *did* detect (see the normalization in `strategies/responses.ts`) died at
+ * the stream boundary. `runToolLoop` works around this with `terminalState` on
+ * its own result, but a caller holding only a response object cannot (#805).
+ *
+ * These are standard OpenAI Responses fields, so this widens the type toward
+ * the wire rather than inventing shape: they are optional because a
+ * non-streaming direct call returns only what the portal serializes today.
+ * Drop the override once the portal declares them upstream.
+ */
+type LlmapiResponseResponse = LlmapiResponseResponse$1 & {
+    /** `"completed"` | `"incomplete"` — the turn's own status, not an output item's. */
+    status?: string;
+    /** Present when `status` is `"incomplete"`; `"max_output_tokens"` is a truncation. */
+    incomplete_details?: {
+        reason?: string;
+    };
+};
 type LlmapiChatCompletionResponse = Omit<LlmapiChatCompletionResponse$1, "usage"> & {
     usage?: LlmapiChatCompletionUsage;
     inference_id?: string;
@@ -2428,6 +2452,21 @@ type StepFinishEvent = {
         inputTokens?: number;
         outputTokens?: number;
     };
+    /**
+     * The round's own finish reason, as the provider sent it — `"length"` means
+     * this round hit the output ceiling.
+     *
+     * Per-round, not per-turn: a round can truncate and the loop still recover on
+     * the next one, which is why the loop does not treat it as an error on its
+     * own (see the truncation guard below). Without it a consumer watching steps
+     * cannot tell a round that said everything it meant to from one that was cut
+     * off mid-argument — they differ only in this field (#805).
+     *
+     * Absent when the provider sent no finish reason. Note that no step event
+     * fires for the round that *ends* a turn, so use {@link RunTerminalState} on
+     * the result for the final round.
+     */
+    finishReason?: string;
 };
 /**
  * Terminal state of the LAST model response in the turn, normalized to the
@@ -2435,13 +2474,14 @@ type StepFinishEvent = {
  * specific values). `undefined` when the stream carried no finish reason at all.
  *
  * Exposed because neither response shape reliably carries it out to a caller.
- * The Responses API shape has no field for it — `LlmapiResponseResponse` declares
- * neither `status` nor `incomplete_details` — so `buildFinalResponse` cannot
- * surface truncation there even though the loop detected it (`responses.ts`
- * normalizes it onto the accumulator). Completions does expose
- * `choices[0].finish_reason`, but omits `tool_calls` entirely when there are
- * none, so a caller sniffing the response cannot tell "no tool calls" from
- * "field absent".
+ * The Responses shape now carries `status` / `incomplete_details` — added in
+ * `clientCompat` and emitted by `buildFinalResponse` — but only in the
+ * Responses vocabulary, so a caller reading it has to translate
+ * `incomplete_details.reason === "max_output_tokens"` itself. Completions
+ * exposes `choices[0].finish_reason`, but omits `tool_calls` entirely when
+ * there are none, so a caller sniffing the response cannot tell "no tool calls"
+ * from "field absent". This field answers both questions in one vocabulary,
+ * for either transport.
  *
  * The loop already knows both, unambiguously and identically for either API.
  * Reporting them here means callers and test harnesses stop reverse-engineering
@@ -8017,6 +8057,298 @@ declare function extractAndLinkEntitiesForMemoriesOp(ctx: VaultMemoryOperationsC
     now?: number;
 }): Promise<TopicExtractionRunResult>;
 
+/**
+ * Post-hoc support verification for extracted memories (#707).
+ *
+ * A stored memory's `confidence` is the extractor's own self-report at
+ * extraction time — clamped to [0,1] and filtered at >= 0.7 (see
+ * `validateCandidates` in autoExtract.ts) — and nothing re-checks it
+ * afterwards. So a hallucinated or mis-attributed fact with confidence 0.9 is
+ * byte-for-byte indistinguishable from a well-grounded one. That was tolerable
+ * while memories only fed recall (a wrong fact meant a bad answer). People
+ * Nearby publishes memory TEXT to public profiles and into digital-twin
+ * prompts, where the same wrong fact is user-visible and attributed to the
+ * user.
+ *
+ * This module asks one question per memory, entailment-style: is this fact
+ * stated or clearly implied by the messages it was extracted from? It reads
+ * the provenance already on the row (`source_chunk_ids`, schema v28) and
+ * WRITES NOTHING — it returns verdicts and the caller decides what to do with
+ * them. #707 is explicit that a failing memory is flagged for user review and
+ * never silently deleted; a pass with no write path cannot violate that.
+ *
+ * WHERE IT MOUNTS. Deliberately NOT inside `setMemoryVisibilityOp`. That op
+ * takes a `VaultMemoryOperationsContext` (database + collection + wallet — no
+ * portal auth, no fetch), runs inside WatermelonDB's serialized writer, and is
+ * also the REVOKE path, which must never be gated on a network call. It is
+ * also not the authority on what is published: its own contract says the
+ * server index is (operations.ts). So verification composes BEFORE it — the
+ * caller verifies, decides, and then calls `setMemoryVisibilityOp` for the
+ * memories it is publishing. The only thing that seam presupposes is "verify
+ * runs before publish"; it assumes nothing about a client publish flow, which
+ * does not exist yet.
+ *
+ * FOUR OUTCOMES, NOT TWO. "Could not be verified" is not the same claim as
+ * "failed verification", and neither is "the verifier itself was unavailable".
+ * Collapsing them would let a broken judge, a deleted conversation, or a
+ * manually-written memory all read as "unsupported" — i.e. would surface a
+ * scary review flag for something that was never even in question. The three
+ * ways provenance can be unusable are kept distinct and are all decided
+ * LOCALLY, before any content leaves the device:
+ *
+ *   1. `not-auto-extracted` — `source` is manual/capsule/legacy-null, so this
+ *      device's extractor did not write the row and there is no local chat
+ *      turn it was derived from. Entailment against local history is
+ *      inapplicable, not merely unavailable. Note the narrower claim: only
+ *      `manual` is reliably the user's own words. `source` records how the
+ *      LOCAL row was created, and a `capsule` import can carry content that
+ *      was auto-extracted somewhere else — its chunk ids could not resolve
+ *      here either way, but it is not "the user wrote this", so UI copy must
+ *      not say so. Nothing about these memories is sent to the portal.
+ *   2. `no-provenance` — auto-extracted but `sourceChunkIds` is null/empty: the
+ *      H4 case where extraction found no usable source ids and no fallback
+ *      message either (retain.ts only writes the column when the array is
+ *      non-empty). Not pre-v28 rows: v28 added `source` and `source_chunk_ids`
+ *      in the same migration and nothing backfills `source`, so a legacy row
+ *      has no label to be auto-extracted BY and lands in bucket 1 instead.
+ *   3. `sources-missing` — the ids are there but none of them resolve. Chat
+ *      messages are hard-deleted (`destroyPermanently`), so provenance
+ *      routinely outlives the evidence; the same bucket also catches a client
+ *      whose message ids were never chat-row ids, since the extraction
+ *      pipeline stores whatever ids the caller passed to `processTurn`.
+ *
+ * A source read that FAILS is none of those three. It is transient, so it goes
+ * to `unchecked`/`sources-unavailable` alongside the judge being down —
+ * "sources are gone" and "the database was locked for a second" must not land
+ * a user in the same place, since only one of them is worth retrying.
+ *
+ * PARTIAL resolution is not a further failure: the memory is verified against
+ * the sources that survive, and `droppedSourceCount` reports the rest so a
+ * caller can caveat the verdict.
+ *
+ * KNOWN SOURCE OF FALSE FLAGS. Extraction's H4 fallback attributes a candidate
+ * with missing/mangled source ids to the last user message in the window and
+ * persists no marker that it did so (autoExtract.ts). A genuine fact whose
+ * evidence lives in some other message will therefore come back `unsupported`,
+ * and post-hoc there is no way to tell that apart from a real miss. The verdict
+ * is still literally true — the fact is not supported by its recorded
+ * provenance — and #707's flag-for-review semantics absorb it. Evidence
+ * truncation (see `maxEvidenceChars`) can do the same thing on very long source
+ * messages. Both cost a review tap; neither can delete anything.
+ *
+ * SECURITY. This is a NEW portal egress surface for memory content, and unlike
+ * the injection classifier it also sends raw CONVERSATION text as evidence, so
+ * it is strictly wider — treat enabling it as such. Mitigations, in order:
+ *   - Nothing is sent for a memory that can be bucketed locally (above), so a
+ *     manual or imported memory never leaves the device on this path at all.
+ *   - Content is PII-redacted with the same redactor class as the extraction
+ *     and injection-classifier paths, and redaction here is OPT-OUT rather
+ *     than opt-in. Those paths inherit `extract.piiRedaction` from the caller
+ *     that runs them; this one has no such parent, so defaulting it off would
+ *     mean the SDK's widest memory egress ships raw whenever a client forgets
+ *     a flag. One shared instance per call, so a value redacted in the fact
+ *     gets the SAME placeholder in the evidence and entailment still lines up.
+ *   - The response is item numbers only, so nothing needs de-anonymizing.
+ *   - Judge injection: both slots carry text an attacker can reach — evidence
+ *     is raw user conversation, and a fact is whatever the extractor wrote
+ *     about a poisoned turn — so the framing is built so content cannot forge
+ *     either of the two things the prompt reasons over. STRUCTURE: facts
+ *     collapse to one line and every evidence line is indented, which leaves
+ *     the left margin — item headers, the MESSAGES: label, the truncation note,
+ *     our own framing lines — unreachable from content. ATTRIBUTION: the
+ *     resolver labels every evidence LINE with its speaker, because "support
+ *     must come from the USER's own words" is the prompt's load-bearing rule and
+ *     one label per MESSAGE would let a line break inside an assistant turn
+ *     render a forged `user:` line byte-identically to a real one. That second
+ *     invariant lives in `VerificationSources` rather than here: this module
+ *     indents text it cannot attribute, so a custom resolver owns its half.
+ *     Both halves treat a lone `\r` as a break (see `LINE_BREAK`), since the
+ *     question is what can start a VISUAL line, not what `split("\n")` sees.
+ *     Beyond structure, persuasion remains possible, and the output shape bounds
+ *     the blast radius both ways: a swayed "supported" leaves us exactly where
+ *     we are today with no verification at all, and a swayed "unsupported" costs
+ *     a review tap. Neither can write, publish, or delete.
+ */
+
+/**
+ * The row fields verification reads. A `StoredVaultMemory` satisfies this
+ * structurally, so callers pass their rows straight through; deriving it with
+ * `Pick` keeps the field names and types tied to the row rather than
+ * re-declared next to it.
+ * @public
+ */
+type MemoryToVerify = Pick<StoredVaultMemory, "uniqueId" | "content" | "source" | "sourceChunkIds">;
+/**
+ * Why a memory could not be checked against its sources at all. Distinct from
+ * a failed check — see this module's header.
+ * @public
+ */
+type UnverifiableReason = 
+/** `source` is not "auto-extracted" — written by hand or imported, so no
+ * local chat turn produced it and entailment does not apply. NOT a claim
+ * that the user authored the text: an imported capsule may hold content
+ * extracted elsewhere (see this module's header). */
+"not-auto-extracted"
+/** Auto-extracted but the row carries no source ids. */
+ | "no-provenance"
+/** Source ids are recorded but none of them resolve any more. */
+ | "sources-missing";
+/**
+ * Why a memory that COULD have been checked wasn't. Never conflate with
+ * `unsupported`: this says the verifier didn't run, not that the fact failed.
+ * @public
+ */
+type UncheckedReason = 
+/** The portal call failed (no auth, network, non-2xx, exhausted retries). */
+"llm-unavailable"
+/** The batch exceeded `maxItems`, so this memory was never sent. */
+ | "over-budget"
+/** At least one source read FAILED (locked DB, adapter error) rather than
+ * coming back empty. Transient, so retryable — deliberately not
+ * `sources-missing`, which claims the evidence is gone for good. */
+ | "sources-unavailable";
+/**
+ * One memory's verdict.
+ *
+ * Note what `unsupported` claims: the fact is not entailed by the provenance
+ * RECORDED on the row, which is a weaker statement than "the fact is wrong".
+ * Extraction's H4 fallback attributes a candidate with missing ids to the last
+ * user message and persists no marker that it guessed, so a well-grounded fact
+ * whose evidence lives in some other message lands here too, and post-hoc
+ * nothing distinguishes it from a real miss (see this module's header). Review
+ * copy should read as "we could not confirm this", not as an accusation.
+ * @public
+ */
+type MemoryVerification = {
+    /** The memory's `uniqueId`, so results can be joined back to the input. */
+    uniqueId: string;
+    /** Source ids that resolved to real message text and were sent as evidence. */
+    resolvedSourceCount: number;
+    /** Source ids that produced no evidence — deleted messages, ids that were
+     * never chat rows, or (on `sources-unavailable`) reads that failed. Adds up
+     * with `resolvedSourceCount` to the memory's distinct source ids on every
+     * status where resolution actually ran, and the status says which kind of
+     * not-resolving happened. Both are 0 on the two statuses decided before any
+     * read — `not-auto-extracted` and `no-provenance` — including for a
+     * `not-auto-extracted` row that does carry ids (an import's ids belong to
+     * another device, so they are never resolved here): 0/0 there means "we did
+     * not look", not "the row had no sources". Non-zero alongside
+     * `supported`/`unsupported` means the verdict rests on partial evidence. */
+    droppedSourceCount: number;
+} & ({
+    status: "supported" | "unsupported";
+} | {
+    status: "unverifiable";
+    reason: UnverifiableReason;
+} | {
+    status: "unchecked";
+    reason: UncheckedReason;
+});
+/**
+ * How verification turns a stored source id into text to judge against.
+ * Injected rather than assumed so this module stays storage-agnostic (and
+ * testable without a database) — {@link createMessageSourceResolver} is the
+ * default wiring over the chat store.
+ * @public
+ */
+interface VerificationSources {
+    /**
+     * Resolve one `sourceChunkIds` entry.
+     *
+     * Return null only when the id DEFINITIVELY resolves to nothing — the
+     * message was deleted, or the id was never a message. That is a permanent
+     * fact about the provenance and produces `unverifiable`/`sources-missing`.
+     *
+     * THROW when the read itself failed (locked database, adapter error, network
+     * store). That is transient and produces `unchecked`/`sources-unavailable`,
+     * so the caller can retry instead of telling a user their evidence is gone.
+     * Verification catches the throw per id; it never propagates.
+     *
+     * An implementation that labels speakers — as
+     * {@link createMessageSourceResolver} does, because the verifier weighs the
+     * user's words differently from the assistant's — must label EVERY line of a
+     * multi-line message, counting a lone `\r` as a break the way verification's
+     * indentation does. Verification indents evidence but cannot see roles, so a
+     * single leading label lets a break in the body forge a second speaker.
+     */
+    getSourceText(chunkId: string): Promise<string | null>;
+}
+/**
+ * Auth + tuning for {@link verifyMemoriesForPublish}. Auth is the dual pattern
+ * — one of `apiKey` / `getToken` is required at runtime (see
+ * {@link PortalLlmAuth}); without it nothing is verified.
+ * @public
+ */
+interface VerifyMemoriesForPublishOptions extends PortalLlmAuth {
+    baseUrl?: string;
+    model?: string;
+    /** Override fetch (tests). */
+    fetchFn?: typeof fetch;
+    /** Max portal attempts on a TRANSIENT failure. Default 2. */
+    maxAttempts?: number;
+    /** Absolute wall-clock budget across attempts. Default 20s. */
+    totalTimeoutMs?: number;
+    /** Backoff before each retry (ms). Tests pass `() => 0`. */
+    backoffMs?: (attempt: number) => number;
+    /**
+     * PII redaction for the outbound fact + evidence.
+     *
+     * OPT-OUT: defaults to ON (a fresh per-call redactor) when omitted, the same
+     * posture as the LLM decay classifier. This is a standalone entry point — there
+     * is no `extract.piiRedaction` upstream of it to inherit from the way the
+     * injection classifier and consolidation inherit theirs — so an off-by-
+     * default switch would mean the widest memory egress in the SDK (fact text
+     * PLUS raw conversation) shipping raw unless a client remembered a flag.
+     * Pass `false` to deliberately disable it.
+     *
+     * Pass a shared {@link PiiRedactor} to keep placeholder numbering consistent
+     * with other calls in the same session. Either way ONE instance covers a
+     * whole call, so the same value redacts to the same placeholder in the fact
+     * and in the evidence — with two instances entailment would break on every
+     * redacted value.
+     */
+    piiRedaction?: boolean | PiiRedactor;
+    /** Max memories verified in one call; the rest come back `unchecked`
+     * (`over-budget`). Default 20. */
+    maxItems?: number;
+    /** Per-memory cap on joined evidence characters. Default 2000. */
+    maxEvidenceChars?: number;
+}
+/**
+ * Verify each memory against the messages it was extracted from, in input
+ * order. Makes at most ONE portal call, and none at all when every memory can
+ * be bucketed locally.
+ *
+ * Writes nothing and publishes nothing — the caller reads the verdicts,
+ * decides (per #707: flag the failures for user review, never delete), and
+ * calls `setMemoryVisibilityOp` for whatever it goes on to publish.
+ *
+ * @public
+ */
+declare function verifyMemoriesForPublish(memories: readonly MemoryToVerify[], sources: VerificationSources, options: VerifyMemoriesForPublishOptions): Promise<MemoryVerification[]>;
+/**
+ * Default {@link VerificationSources} over the chat store: resolves a source id
+ * to its message text, role-prefixed per LINE so the verifier can apply the same
+ * "the USER must have said it" rule the extractor does without the message body
+ * being able to forge a speaker. Decryption is the ops layer's job — pass the
+ * same `StorageOperationsContext` the rest of the chat reads go through.
+ *
+ * Returns null for an id that no longer resolves, which is the common case
+ * rather than an error: messages are hard-deleted, and the ids on a memory are
+ * whatever the client handed `processTurn`, which the SDK never required to be
+ * chat rows.
+ *
+ * Storage failures are deliberately NOT swallowed here. `getMessageOp` already
+ * separates the two — null for "not found", a throw for a locked DB or adapter
+ * failure — and flattening that would report a broken read as permanently
+ * missing evidence. The throw propagates into verification, which catches it
+ * per id and returns `unchecked`/`sources-unavailable`; nothing reaches the
+ * caller as an exception.
+ *
+ * @public
+ */
+declare function createMessageSourceResolver(ctx: StorageOperationsContext): VerificationSources;
+
 /**
  * Text Chunking Utilities
  *
@@ -9393,4 +9725,4 @@ declare function refreshNotionAccessToken(params: NotionRefreshTokenParams): Pro
  */
 declare function createNotionTools(getAccessToken: () => string | null, requestNotionAccess: () => Promise<string>): ToolConfig[];
 
-export { type AutoExtractMessage, type AutoExtractor, type Budget, type CachedChunkVectors, type CachedServerTools, Conversation as ChatConversation, Message as ChatMessage, type ChatRole, type ChunkVectorCache, type ChunkingOptions, type ConsolidationFallbackReason, type ConversationMemoryInput, ConversationMemory as ConversationMemoryModel, type ConversationMemoryOperationsContext, type CreateAutoExtractorOptions, type CreateConversationOptions, type CreateDecaySweeperOptions, type CreateMessageOptions, type CreateVaultFolderOptions, type CreateVaultMemoryOptions, type CryptoPriceClassification, type CryptoPricePreProcessorOptions, DEFAULT_CACHE_EXPIRATION_MS, DEFAULT_CHUNK_CACHE_SIZE, DEFAULT_CHUNK_OVERLAP, DEFAULT_CHUNK_SIZE, DEFAULT_DECAY_POLICY, DEFAULT_MAX_CLASSIFIER_CALLS_PER_SWEEP, DEFAULT_MIN_CHUNK_SIZE, DEFAULT_PROFILE_FACETS, DEFAULT_PROFILE_FACT_TYPE_WEIGHTS, DEFAULT_PROFILE_PROOF_ALPHA, DEFAULT_PROFILE_TREND_MULTIPLIERS, DEFAULT_VAULT_CACHE_SIZE, DatabaseManager, type DatabaseManagerLogger, type DatabaseManagerOptions, type DecayCandidateRaw, type DecayClassifier, type DecayInput, type DecayPolicy, type DecaySweepResult, type DecaySweeper, type DecayVerdict, ENTITY_FANOUT, type EmbeddedWalletSignerFn, EncryptionKeyMissingError, type ExtractFactsOptions, type ExtractOutcome, type ExtractedCandidate, type ExtractedEntity, type ExtractionCursorStore, type FactType, type FileMetadata, type FlushResult, type GetConversationsPageOptions, type GetMessagesPageOptions, type GraphTraversalOptions, HARD_DELETE_WINDOW_MS, INFERENCE_ID_HEADER, type InjectionClassifierOptions, type InjectionReason, type LazyStoredConversation, type LlmDecayClassifierOptions, type LlmNeighborRefinerOptions, type Logger, LoggerProvider, type LoggerProviderProps, MAX_HOPS, MEDIUM_TTL_MS, type MemoriesNeedingTopicExtraction, type EmbeddingOptions as MemoryEngineEmbeddingOptions, type MemoryEngineResult, type MemoryEngineSearchOptions, type MemoryExtractedEvent, type MemoryKind, type MemoryQuarantinedEvent, type MemoryVaultSearchOptions, type MemoryVaultToolOptions, type MessageRedactionResult, type MessageSkeleton, NEVER_TTL_MS, NODE_BUDGET, NOTION_OAUTH_CONFIG, type NeighborRefiner, type NotionAuthUrlParams, type NotionClientRegistration, type NotionExchangeCodeParams, type NotionOAuthEndpoints, type NotionPKCEChallenge, type NotionRefreshTokenParams, type NotionTokenResponse, type NowSource, type ObservationTrend, type ObservationTrendInput, PAST_EVENT_GRACE_MS, PII_PATTERNS, PROFILE_DOC_VERSION, type PiiCategory, type PiiMatch, type PiiPattern, PiiRedactor, type PiiRedactorOptions, type PlatformStorage, type PortalLlmAuth, type ProfileConfigFingerprint, type ProfileDoc, type ProfileFacet, type ProfileFacetKey, type ProfileSalienceInput, type ProfileSection, type PromptPreProcessor, type PromptPreProcessorContext, type QuantizedEmbedding, type QuarantinedMemoryInfo, QueueManager, type QueueStatus, RECALL_MAX_LIMIT, RECALL_TOOL_NAME, type RankedMemory, type RankedProfileCandidate, type RecallContext, type RecallDegradation, type RecallDiagnostics, type RecallOptions, type RecallResult, type RecallToolCallbacks, type RecallToolOptions, type RecencyOptions, type RedactionResult, type ReflectOptions, type ReflectResult, type RequestEncryptionKeyOptions, RerankerUnavailableError, type ResumeStreamOptions, type ResumeStreamResult, type ResumeStreamWithStorageResult, type RetainAction, type RetainContext, type RetainOptions, type RetainResult, type RetainSource, SDK_SCHEMA_VERSION, SHORT_TTL_MS, STREAM_RESUMABLE_HEADER, type ScoreBreakdown, type ScoreProfileSalienceOptions, type ScreenResult, type ScreenedCandidate, type SearchSource, type SendMessageWithStorageArgs, type SendMessageWithStorageDetachedResult, type SendMessageWithStorageResult, type ServerToolsOptions, type ServerToolsResponse, type SignMessageFn, type StockPriceClassification, type StockPricePreProcessorOptions, type ChatCompletionUsage as StoredChatCompletionUsage, type StoredConversation, type StoredConversationMemory, type StoredMessage, type StoredMessageWithSimilarity, type StoredVaultFolder, VaultFolder as StoredVaultFolderModel, type StoredVaultMemory, VaultMemory as StoredVaultMemoryModel, StreamExpiredError, type StreamMetaEvent, type StreamResumeHandle, type SynthesizeProfileOptions, TOPICS_EXTRACTION_VERSION, TOPIC_EXTRACTION_BATCH_SIZE, TREND_RECENT_WINDOW_DAYS, TREND_STALE_WINDOW_DAYS, type TextChunk, type TopicExtractOptions, type TopicExtractionInput, type TopicExtractionRunResult, type TurnCompleteEvent, type TurnSkippedEvent, type UpdateVaultFolderOptions, type UpdateVaultMemoryOptions, type UseChatStorageOptions, type UseChatStorageResult, type UseCreditsOptions, type UseCreditsResult, type UseModelsOptions, type UseModelsResult, VAULT_SIZE_HOP_CAP, type VaultEmbeddingCache, type VaultFolderOperationsContext, type VaultMemoryOperationsContext, type VaultMemoryVisibility, type VaultSaveOperation, type VaultSearchResult, WalletPoller, type WeatherClassification, type WeatherPreProcessorOptions, type WebSearchClassification, type WebSearchPreProcessorOptions, addConversationMemoriesOp, archiveVaultMemoryOp, backfillMemoryTopicsOp, buildNotionAuthUrl, capHopsForDensity, chatStorageMigrations, chatStorageSchema, chunkAndEmbedAllMessages, chunkAndEmbedMessage, chunkText, classifyCryptoPrice, classifyCryptoPriceBatch, classifyDecay, classifyInjectionCandidates, classifyObservationTrend, classifyStockPrice, classifyStockPriceBatch, classifyWeather, classifyWeatherBatch, classifyWebSearch, classifyWebSearchBatch, clearAllEncryptionKeys, clearAllEncryptionState, clearConversationMemoriesOp, clearEncryptionKey, clearLazyTitleCache, clearServerToolsCache, consoleLogger, conversationMemoryToStored, cosineInt8, createAutoExtractor, createChunkVectorCache, createCryptoPricePreProcessor, createDecaySweeper, createLlmDecayClassifier, createLlmNeighborRefiner, createMemoryEngineTool, createMemoryVaultSearchTool, createMemoryVaultTool, createNotionTools, createPlatformCursorStore, createRecallTool, createStockPricePreProcessor, createStreamingDeAnonymizer, createVaultEmbeddingCache, createVaultFolderOp, createVaultMemoriesBatchOp, createVaultMemoryOp, createWeatherPreProcessor, createWebSearchPreProcessor, decryptConversationTitle, deleteAllVaultMemoriesForUserOp, deleteVaultFolderOp, deleteVaultMemoryOp, dequantizeEmbedding, discoverNotionOAuthEndpoints, eagerEmbedContent, embedAllMessages, embedMessage, ensureDefaultFoldersOp, exchangeNotionCode, extractAndLinkEntitiesForMemoriesOp, extractAndRetain, extractEntitiesForMemories, extractFacts, generateConversationId, generateEmbedding, generateEmbeddings, generateNotionPKCE, getAllVaultFoldersOp, getAllVaultMemoriesOp, getAllVaultMemoryContentsOp, getCachedServerTools, getConversationMemoriesOp, getConversationsByProjectLazyOp, getConversationsLazyOp, getConversationsPageOp, getDecayCandidatesRawOp, getLogger, getMemoriesNeedingTopicExtractionOp, getServerTools, getUnfiledVaultMemoriesOp, getVaultFolderMemoryCountOp, getVaultMemoryOp, hardDeleteDecayedOp, hasEncryptionKey, injectionSignatureCatalog, isPiiRedactor, isRerankerAvailable, moveMemoriesToFolderOp, noopLogger, onKeyAvailable, preEmbedVaultMemories, quantizeEmbedding, queueManager, rankProfileCandidates, recall, reflect, refreshEncryptionKeyIfMatches, refreshNotionAccessToken, registerNotionClient, relinkMemoryTopicsOp, requestEncryptionKey, resolvePiiRedactor, restoreVaultMemoryOp, resumeStream, retain, scoreProfileSalience, screenCandidatesForInjection, sdkMigrations, sdkModelClasses, sdkSchema, searchVaultMemories, seedEncryptionKeys, setLogger, setMemoryVisibilityOp, shouldChunkMessage, stampTopicsExtractedAtOp, streamCancelPath, streamReplayPath, summarizeObservationTrends, supersedeVaultMemoryOp, synthesizeProfile, traverseGraphLane, ttlForType, updateVaultFolderContextOp, updateVaultFolderOp, updateVaultMemoryEmbeddingOp, updateVaultMemoryOp, upsertMessageOp, useChat, useChatStorage, useCredits, useEncryption, useModels, xhrTransport };
+export { type AutoExtractMessage, type AutoExtractor, type Budget, type CachedChunkVectors, type CachedServerTools, Conversation as ChatConversation, Message as ChatMessage, type ChatRole, type ChunkVectorCache, type ChunkingOptions, type ConsolidationFallbackReason, type ConversationMemoryInput, ConversationMemory as ConversationMemoryModel, type ConversationMemoryOperationsContext, type CreateAutoExtractorOptions, type CreateConversationOptions, type CreateDecaySweeperOptions, type CreateMessageOptions, type CreateVaultFolderOptions, type CreateVaultMemoryOptions, type CryptoPriceClassification, type CryptoPricePreProcessorOptions, DEFAULT_CACHE_EXPIRATION_MS, DEFAULT_CHUNK_CACHE_SIZE, DEFAULT_CHUNK_OVERLAP, DEFAULT_CHUNK_SIZE, DEFAULT_DECAY_POLICY, DEFAULT_MAX_CLASSIFIER_CALLS_PER_SWEEP, DEFAULT_MIN_CHUNK_SIZE, DEFAULT_PROFILE_FACETS, DEFAULT_PROFILE_FACT_TYPE_WEIGHTS, DEFAULT_PROFILE_PROOF_ALPHA, DEFAULT_PROFILE_TREND_MULTIPLIERS, DEFAULT_VAULT_CACHE_SIZE, DatabaseManager, type DatabaseManagerLogger, type DatabaseManagerOptions, type DecayCandidateRaw, type DecayClassifier, type DecayInput, type DecayPolicy, type DecaySweepResult, type DecaySweeper, type DecayVerdict, ENTITY_FANOUT, type EmbeddedWalletSignerFn, EncryptionKeyMissingError, type ExtractFactsOptions, type ExtractOutcome, type ExtractedCandidate, type ExtractedEntity, type ExtractionCursorStore, type FactType, type FileMetadata, type FlushResult, type GetConversationsPageOptions, type GetMessagesPageOptions, type GraphTraversalOptions, HARD_DELETE_WINDOW_MS, INFERENCE_ID_HEADER, type InjectionClassifierOptions, type InjectionReason, type LazyStoredConversation, type LlmDecayClassifierOptions, type LlmNeighborRefinerOptions, type Logger, LoggerProvider, type LoggerProviderProps, MAX_HOPS, MEDIUM_TTL_MS, type MemoriesNeedingTopicExtraction, type EmbeddingOptions as MemoryEngineEmbeddingOptions, type MemoryEngineResult, type MemoryEngineSearchOptions, type MemoryExtractedEvent, type MemoryKind, type MemoryQuarantinedEvent, type MemoryToVerify, type MemoryVaultSearchOptions, type MemoryVaultToolOptions, type MemoryVerification, type MessageRedactionResult, type MessageSkeleton, NEVER_TTL_MS, NODE_BUDGET, NOTION_OAUTH_CONFIG, type NeighborRefiner, type NotionAuthUrlParams, type NotionClientRegistration, type NotionExchangeCodeParams, type NotionOAuthEndpoints, type NotionPKCEChallenge, type NotionRefreshTokenParams, type NotionTokenResponse, type NowSource, type ObservationTrend, type ObservationTrendInput, PAST_EVENT_GRACE_MS, PII_PATTERNS, PROFILE_DOC_VERSION, type PiiCategory, type PiiMatch, type PiiPattern, PiiRedactor, type PiiRedactorOptions, type PlatformStorage, type PortalLlmAuth, type ProfileConfigFingerprint, type ProfileDoc, type ProfileFacet, type ProfileFacetKey, type ProfileSalienceInput, type ProfileSection, type PromptPreProcessor, type PromptPreProcessorContext, type QuantizedEmbedding, type QuarantinedMemoryInfo, QueueManager, type QueueStatus, RECALL_MAX_LIMIT, RECALL_TOOL_NAME, type RankedMemory, type RankedProfileCandidate, type RecallContext, type RecallDegradation, type RecallDiagnostics, type RecallOptions, type RecallResult, type RecallToolCallbacks, type RecallToolOptions, type RecencyOptions, type RedactionResult, type ReflectOptions, type ReflectResult, type RequestEncryptionKeyOptions, RerankerUnavailableError, type ResumeStreamOptions, type ResumeStreamResult, type ResumeStreamWithStorageResult, type RetainAction, type RetainContext, type RetainOptions, type RetainResult, type RetainSource, SDK_SCHEMA_VERSION, SHORT_TTL_MS, STREAM_RESUMABLE_HEADER, type ScoreBreakdown, type ScoreProfileSalienceOptions, type ScreenResult, type ScreenedCandidate, type SearchSource, type SendMessageWithStorageArgs, type SendMessageWithStorageDetachedResult, type SendMessageWithStorageResult, type ServerToolsOptions, type ServerToolsResponse, type SignMessageFn, type StockPriceClassification, type StockPricePreProcessorOptions, type ChatCompletionUsage as StoredChatCompletionUsage, type StoredConversation, type StoredConversationMemory, type StoredMessage, type StoredMessageWithSimilarity, type StoredVaultFolder, VaultFolder as StoredVaultFolderModel, type StoredVaultMemory, VaultMemory as StoredVaultMemoryModel, StreamExpiredError, type StreamMetaEvent, type StreamResumeHandle, type SynthesizeProfileOptions, TOPICS_EXTRACTION_VERSION, TOPIC_EXTRACTION_BATCH_SIZE, TREND_RECENT_WINDOW_DAYS, TREND_STALE_WINDOW_DAYS, type TextChunk, type TopicExtractOptions, type TopicExtractionInput, type TopicExtractionRunResult, type TurnCompleteEvent, type TurnSkippedEvent, type UncheckedReason, type UnverifiableReason, type UpdateVaultFolderOptions, type UpdateVaultMemoryOptions, type UseChatStorageOptions, type UseChatStorageResult, type UseCreditsOptions, type UseCreditsResult, type UseModelsOptions, type UseModelsResult, VAULT_SIZE_HOP_CAP, type VaultEmbeddingCache, type VaultFolderOperationsContext, type VaultMemoryOperationsContext, type VaultMemoryVisibility, type VaultSaveOperation, type VaultSearchResult, type VerificationSources, type VerifyMemoriesForPublishOptions, WalletPoller, type WeatherClassification, type WeatherPreProcessorOptions, type WebSearchClassification, type WebSearchPreProcessorOptions, addConversationMemoriesOp, archiveVaultMemoryOp, backfillMemoryTopicsOp, buildNotionAuthUrl, capHopsForDensity, chatStorageMigrations, chatStorageSchema, chunkAndEmbedAllMessages, chunkAndEmbedMessage, chunkText, classifyCryptoPrice, classifyCryptoPriceBatch, classifyDecay, classifyInjectionCandidates, classifyObservationTrend, classifyStockPrice, classifyStockPriceBatch, classifyWeather, classifyWeatherBatch, classifyWebSearch, classifyWebSearchBatch, clearAllEncryptionKeys, clearAllEncryptionState, clearConversationMemoriesOp, clearEncryptionKey, clearLazyTitleCache, clearServerToolsCache, consoleLogger, conversationMemoryToStored, cosineInt8, createAutoExtractor, createChunkVectorCache, createCryptoPricePreProcessor, createDecaySweeper, createLlmDecayClassifier, createLlmNeighborRefiner, createMemoryEngineTool, createMemoryVaultSearchTool, createMemoryVaultTool, createMessageSourceResolver, createNotionTools, createPlatformCursorStore, createRecallTool, createStockPricePreProcessor, createStreamingDeAnonymizer, createVaultEmbeddingCache, createVaultFolderOp, createVaultMemoriesBatchOp, createVaultMemoryOp, createWeatherPreProcessor, createWebSearchPreProcessor, decryptConversationTitle, deleteAllVaultMemoriesForUserOp, deleteVaultFolderOp, deleteVaultMemoryOp, dequantizeEmbedding, discoverNotionOAuthEndpoints, eagerEmbedContent, embedAllMessages, embedMessage, ensureDefaultFoldersOp, exchangeNotionCode, extractAndLinkEntitiesForMemoriesOp, extractAndRetain, extractEntitiesForMemories, extractFacts, generateConversationId, generateEmbedding, generateEmbeddings, generateNotionPKCE, getAllVaultFoldersOp, getAllVaultMemoriesOp, getAllVaultMemoryContentsOp, getCachedServerTools, getConversationMemoriesOp, getConversationsByProjectLazyOp, getConversationsLazyOp, getConversationsPageOp, getDecayCandidatesRawOp, getLogger, getMemoriesNeedingTopicExtractionOp, getServerTools, getUnfiledVaultMemoriesOp, getVaultFolderMemoryCountOp, getVaultMemoryOp, hardDeleteDecayedOp, hasEncryptionKey, injectionSignatureCatalog, isPiiRedactor, isRerankerAvailable, moveMemoriesToFolderOp, noopLogger, onKeyAvailable, preEmbedVaultMemories, quantizeEmbedding, queueManager, rankProfileCandidates, recall, reflect, refreshEncryptionKeyIfMatches, refreshNotionAccessToken, registerNotionClient, relinkMemoryTopicsOp, requestEncryptionKey, resolvePiiRedactor, restoreVaultMemoryOp, resumeStream, retain, scoreProfileSalience, screenCandidatesForInjection, sdkMigrations, sdkModelClasses, sdkSchema, searchVaultMemories, seedEncryptionKeys, setLogger, setMemoryVisibilityOp, shouldChunkMessage, stampTopicsExtractedAtOp, streamCancelPath, streamReplayPath, summarizeObservationTrends, supersedeVaultMemoryOp, synthesizeProfile, traverseGraphLane, ttlForType, updateVaultFolderContextOp, updateVaultFolderOp, updateVaultMemoryEmbeddingOp, updateVaultMemoryOp, upsertMessageOp, useChat, useChatStorage, useCredits, useEncryption, useModels, verifyMemoriesForPublish, xhrTransport };