bunnyquery 1.7.0 → 1.8.1

package/dist/engine.d.mts

@@ -312,18 +312,44 @@ declare function isAuthExpiredError(input: any): boolean;
 
 declare var CONTEXT_WINDOW_DEFAULT: Record<string, number>;
 declare var CONTEXT_WINDOW_BY_MODEL: Record<string, number>;
+/**
+ * Record context windows from a provider models listing. Accepts the raw list
+ * items and reads `max_input_tokens` (Anthropic); items without it are skipped,
+ * so passing an OpenAI listing is a no-op rather than an error.
+ */
+declare function registerModelContextWindows(models: Array<{
+    id?: string;
+    max_input_tokens?: number;
+}> | null | undefined): void;
+declare function setProjectContextWindow(serviceId: string, tokens: number | null | undefined): void;
+declare function getProjectContextWindow(serviceId: string): number | null;
 declare var OUTPUT_TOKEN_RESERVE: number;
 declare var TOOL_AND_RESPONSE_BUFFER: number;
 declare var MIN_INPUT_TOKEN_BUDGET: number;
 declare var CLAUDE_PER_REQUEST_INPUT_CAP: number;
 declare var MAX_HISTORY_MESSAGES: number;
 declare var HISTORY_TOKEN_BUDGET: number;
+declare var CLAUDE_INPUT_CAP_RATIO: number;
+declare var HISTORY_BUDGET_RATIO: number;
 declare function estimateTextTokens(text: string): number;
 declare function estimateMessageTokens(msg: {
     role: string;
     content: string;
 }): number;
-declare function getContextWindow(platform: string, model?: string): number;
+/**
+ * Resolve a model's context window, most specific source first:
+ *   1. per-project override (project settings)
+ *   2. the provider's own models listing (Anthropic `max_input_tokens`)
+ *   3. an exact entry in CONTEXT_WINDOW_BY_MODEL
+ *   4. a family entry, by dropping trailing '-' segments off the id
+ *   5. the platform default
+ *
+ * Step 4 is why a new or suffixed id no longer drops straight to the platform
+ * default: 'gpt-5.6-luna' resolves via 'gpt-5.6', and a dated Claude snapshot
+ * such as 'claude-opus-4-7-20260101' resolves via 'claude-opus-4-7'. The walk
+ * stops at the first hit, so a more specific entry always wins over its family.
+ */
+declare function getContextWindow(platform: string, model?: string, serviceId?: string): number;
 declare function stripFileBlocksFromHistory(content: string): string;
 type BoundedChatOptions = {
     platform: string;
@@ -423,6 +449,21 @@ declare function isHttpUrlLike(target: string): boolean;
  *     space in it, and deleting it points at a file that does not exist.
  */
 declare function repairUrlWhitespace(href: string): string;
+/**
+ * A model reproducing a URL sometimes HTML-escapes its `&` query separators as
+ * `&amp;` (or the numeric `&#38;` / `&#x26;`). Left in the href that escaping
+ * survives the client's own escapeAttr -> v-html/innerHTML decode round-trip and
+ * reaches the browser LITERALLY, so a presigned S3 URL is navigated with its
+ * parameters named `amp;Signature`, `amp;Expires`, `amp;response-content-type`,
+ * ... — the real params vanish, the signature can't be located, and S3 rejects
+ * it (the "링크가 안되" dead export link). Undo just that entity escaping.
+ *
+ * This is a no-op on a clean URL: a valid link carries a raw `&` between params
+ * and percent-encodes (`%26`) any literal ampersand that is data, so a real URL
+ * never contains `&amp;` to begin with. Mirrors repairUrlWhitespace: it repairs
+ * model damage, not the URL. The loop collapses a doubly-escaped `&amp;amp;` too.
+ */
+declare function repairUrlEntities(href: string): string;
 /**
  * Trim punctuation and unmatched wrappers that cling to a token in prose.
  * `src::a/b.pdf).` -> `src::a/b.pdf`, while a balanced `file (v2).pdf` is kept.
@@ -466,9 +507,78 @@ declare function classifyInlineLink(full: string, groups: Array<string | undefin
 } | null;
 declare function truncateLabelForDisplay(label: string): string;
 
+/**
+ * Chat timestamp formatting, shared so agent.vue and the widget render an
+ * identical "small text under the bubble". Pure and locale-aware: it formats a
+ * given epoch-ms value, it never reads the current time, so it stays testable and
+ * DOM-free.
+ */
+/** Wall-clock epoch ms. Separate from the engine's monotonic nowMs() (which is
+ *  performance.now() when available and therefore NOT epoch): a displayed
+ *  timestamp must be wall time. */
+declare function wallClockNow(): number;
+/**
+ * "Jul 24, 2026, 3:42:07 PM" (locale-formatted). Empty string for a missing or
+ * non-finite value, so a caller can gate rendering on the result being truthy and
+ * a pending bubble (no timestamp yet) simply shows nothing.
+ */
+declare function formatChatTimestamp(ms?: number): string;
+
+/**
+ * The `ai_agent` service option, parsed and serialized in ONE place.
+ *
+ * Stored on the skapi service record as up to three '#'-delimited segments:
+ *
+ *   none                                  AI chat disabled
+ *   claude                                platform chosen, no model saved yet
+ *   claude#claude-sonnet-4-6              platform + model
+ *   claude#claude-sonnet-4-6#400000       platform + model + context-window override
+ *
+ * The third segment is new and optional, so every value written before it
+ * existed parses unchanged with `contextWindow: null`. Nothing writes a third
+ * segment without a model, because the window is meaningless without one.
+ *
+ * This lived as four separate copies (agent.vue, dbfile.vue, service.vue, and
+ * the widget's index.js), which is how the format drifts. New callers should
+ * import from here rather than re-deriving the split.
+ */
+type AiAgentPlatform = 'claude' | 'openai' | null;
+type ParsedAiAgent = {
+    /** null when unset or explicitly 'none'. */
+    platform: AiAgentPlatform;
+    /** '' when no model has been saved. */
+    model: string;
+    /** Per-project context-window override in tokens, or null to use the model's. */
+    contextWindow: number | null;
+    /** True when a real platform is configured (i.e. not unset and not 'none'). */
+    hasPlatform: boolean;
+};
+declare function parseAiAgentValue(value: string | null | undefined): ParsedAiAgent;
+declare function buildAiAgentValue(platform: string | null | undefined, model?: string | null, contextWindow?: number | null): string;
+
 declare function filterListByClearHorizon(list: any[], clearedAt: number): any[];
 declare function normalizeTextContent(content: any): string;
 declare function extractLastUserTextFromRequest(requestBody: any): string;
+/** The two openings an indexing prompt can have. A bg-queue item that starts with
+ *  neither is an ordinary chat that happened to be routed onto that queue. */
+declare function isIndexingRequestText(userText: any): boolean;
+type IndexingRequestRef = {
+    name: string;
+    path?: string;
+    mime?: string;
+    size?: number;
+    /** A CONTINUE pass rather than the run's first. */
+    continued: boolean;
+};
+/**
+ * The file an indexing prompt is about, read back out of the prompt itself.
+ *
+ * The prompt is the only description of the pass that survives on the server, so
+ * this is how BOTH a history rebuild and a worker-minted pass the client never
+ * dispatched (ChatSession._adoptWorkerIndexingPasses) recover the file. Shared so
+ * the two produce the same `_indexFile`, which is what makes them group together.
+ */
+declare function parseIndexingRequestText(userText: any): IndexingRequestRef | null;
 type MapHistoryOptions = {
     clearedAt: number;
     serviceId: string;
@@ -681,11 +791,20 @@ type BgTaskEntry = {
     /** How many CONTINUE passes have already run for this file (resume-across-passes). */
     resumePass?: number;
 };
+/**
+ * `queue` narrows the fetch to one processing chain; `status` narrows it to items
+ * in one state. Passing both is how the client asks "is there still unresolved
+ * work on the background-indexing queue?" without pulling a page of chat history
+ * (see ChatSession._adoptWorkerIndexingPasses) — the server answers that from a
+ * status-keyed index, so the reply carries only the live items, not the bodies of
+ * everything already finished.
+ */
 declare function getChatHistory(params: {
     service?: string;
     owner?: string;
     platform: 'claude' | 'openai';
     queue?: string;
+    status?: 'pending' | 'running' | 'resolved' | 'failed';
 }, fetchOptions: Record<string, any>): Promise<any>;
 
 /**
@@ -753,6 +872,12 @@ interface ChatMessage {
     _localId?: string;
     _cancelling?: boolean;
     _cancelError?: string;
+    /** Epoch ms shown as small text under the bubble. From the request history a
+     *  USER bubble carries the request's `created` time and an ASSISTANT bubble the
+     *  `updated` (response) time; a live bubble is stamped with the wall clock when
+     *  it is created, then reconciled to the server value on the next history load.
+     *  Absent while a turn is still pending, so no time shows on a "Thinking" bubble. */
+    _ts?: number;
     _ownerKey?: string;
 }
 interface ChatState {
@@ -845,12 +970,34 @@ interface ChatHost {
  * repeating forever, and any real question the user asks in between gets buried.
  *
  * buildChatDisplayList turns the flat message array into a DISPLAY list in which
- * every message belonging to one file (however far apart they sit, and whatever
- * else is interleaved between them) is represented by a single group entry,
- * rendered at the position of that file's NEWEST turn. Newest, not oldest, so:
- *   - a running index sits at the bottom, where the activity is, and
- *   - paging older history in never moves a row that is already on screen
- *     (older passes simply join the group they already belong to).
+ * every message belonging to one run of one file (however far apart the passes
+ * sit, and whatever else is interleaved between them) is represented by a single
+ * group entry, rendered at the position of that run's FIRST loaded pass.
+ *
+ * First, not newest. The message array is ordered by request CREATION time, and
+ * a run's later passes are created one at a time as the previous one resolves —
+ * by the client for the paged text path, and by the WORKER itself for the
+ * rendered-page (PDF) path, which the client only learns about on its next
+ * first-page history fetch. So a pass is routinely created minutes after the
+ * upload, on a queue that runs in parallel with the foreground chat. Anchoring
+ * at the newest pass meant one such late pass dragged the whole run — every
+ * earlier pass with it — below any question the user had asked in the meantime,
+ * and made a run that had visibly finished before the question render after it.
+ * Anchoring at the first pass puts the row where the run actually began, which
+ * is a position no later pass can change:
+ *   - a new pass never relocates the row, so nothing under the reader shifts;
+ *   - a question asked after the upload always renders below the row, which is
+ *     the order it happened in.
+ * The cost is that a long-running index does not follow the conversation to the
+ * bottom: once the user has chatted past the upload, the spinner and the Stop
+ * button sit above their newest turns. That is a scroll away, and the row no
+ * longer lies about when the work started.
+ *
+ * Paging older history is the one thing that CAN move the row: an older page
+ * carrying earlier passes of a run already on screen moves it up into that page.
+ * That happens at most once per run, only for a run whose start was never
+ * loaded (`mayHaveOlder`), and it is the same event that already re-derives
+ * `runKey` — so the view treats it as a new row either way.
  *
  * The group deliberately reports no authoritative pass TOTAL. History is paged
  * newest-first, so any total computed from loaded messages is a lower bound that
@@ -873,9 +1020,10 @@ type IndexingGroup = {
      *  Monday and re-indexed on Wednesday is two runs, and collapsing them into
      *  one row erased Monday's from Monday's place in the conversation, claimed
      *  its passes for Wednesday, and let Monday's failure be overwritten by
-     *  Wednesday's success. Numbered from the NEWEST run backwards (`#0` is the
-     *  newest) so paging in older history never renames a row already on screen.
-     *  This is the render key and the expansion key. */
+     *  Wednesday's success. Named after the run's FIRST loaded pass (see where it
+     *  is assigned below), so passes appended to the run and other runs appearing
+     *  on either side of it never rename a row already on screen. This is the
+     *  render key and the expansion key. */
     runKey: string;
     name: string;
     path?: string;
@@ -904,8 +1052,16 @@ type IndexingGroup = {
     /** The file's first pass is not among the loaded messages, so earlier passes
      *  exist in history that has not been paged in yet. */
     mayHaveOlder: boolean;
-    /** Position in the source array this collapsed row renders at. */
+    /** Position in the source array this collapsed row renders at: the index of
+     *  the run's FIRST loaded pass (see the file docstring for why not the last). */
     anchorIndex: number;
+    /** Identity of the turn at `anchorIndex` — its server item id, or its local id
+     *  while it has none, or `''` when it has neither. The views stamp this on the
+     *  row (`data-row-pos`) so the scroll anchor can tell a row that RELOCATED (an
+     *  older page moved the run's start) from one that merely gained a pass. They
+     *  must not re-derive it from `members`: which member the row renders at is
+     *  this module's decision, and the two silently disagreed once already. */
+    anchorId: string;
 };
 type DisplayEntry = {
     kind: 'message';
@@ -1083,6 +1239,9 @@ declare class ChatSession {
     _clearPendingUserBubble(itemId: string): void;
     resumePendingRequest(token: number): Promise<void>;
     handleHistoryItemResolution(itemId: string, response: any, platform: string): void;
+    /** The file an already-rendered background pass is about, off its request
+     *  bubble. Null for an ordinary turn, which is most of them. */
+    private _indexRefOfItem;
     applyHistoryItemResolution(itemId: string, response: any, platform: string): void;
     /** How a bg task maps onto a collapsed row: the row's own key (storage path
      *  when known, else the filename), scoped to the chat it belongs to. A storage
@@ -1114,6 +1273,49 @@ declare class ChatSession {
      * Runs from drainBgTaskQueue, which both clients call after a history load.
      */
     private _sweepCancelledIndexing;
+    /**
+     * True when the WORKER, not this client, drives the rest of this file's chain.
+     * The mirror image of the early returns in maybeResumeIndexing: whatever that
+     * refuses to continue is exactly what nothing client-side is tracking.
+     */
+    private _isWorkerDrivenIndexing;
+    /**
+     * Pick up indexing passes the WORKER minted, which no client ever dispatched.
+     *
+     * For a PDF (and for text/grid when windowed indexing is on) the worker writes
+     * pass N+1's row itself, inside pass N's invocation, right after saving pass
+     * N's result. That row reaches this client through nothing at all: it is not in
+     * bgTaskQueue (the client never asked for it) and it is not in state.messages
+     * (only a first-page history load maps it in, which happens on mount, project
+     * switch or tab return). So between two worker passes every pass the client
+     * knows about is settled, and the collapsed row renders "Indexed  N passes"
+     * with no spinner and no Stop, for a file that is still being read. A user who
+     * believes that then asks questions against a half-indexed file — which is what
+     * this exists to prevent.
+     *
+     * So when a background indexing pass settles, ask the bg queue what is still
+     * unresolved on it and adopt anything unknown as an ordinary BgTaskEntry.
+     * drainBgTaskQueue then treats it exactly like a pass this client dispatched:
+     * same bubble, same `_indexFile` (so it joins the file's collapsed row), same
+     * poll — and that poll settling runs this again, so the chain is followed to
+     * its end. `status`-scoped so the reply carries the live items only, never a
+     * page of finished ones with their bodies.
+     *
+     * Termination: the only trigger is a pass SETTLING, which happens once per
+     * pass. An adopted item that is still running is not re-adopted (its id is
+     * already polled), and when the queue holds nothing unknown the chain stops on
+     * its own. Nothing here is periodic — a timer that re-reads history is the
+     * shape that previously looped fetchHistoryPage after an already-DONE index.
+     */
+    private _adoptingWorkerPasses;
+    private _adoptWorkerIndexingPasses;
+    /** Any of these ids still queued or still polled, i.e. surviving work. */
+    private _isTrackingAny;
+    /** One live bg-queue item -> a BgTaskEntry, if it is an indexing pass this
+     *  client is not already tracking. Returns whether it was adopted. */
+    private _adoptWorkerIndexingItem;
+    /** Follow the chain on from a background indexing pass that just settled. */
+    private _followWorkerIndexingChain;
     /** Best-effort server-side cancel of a bg-queue item that has no bubble (so
      *  cancelQueuedMessage, which drives one, has nothing to act on). */
     private _cancelServerItem;
@@ -1134,4 +1336,4 @@ declare class ChatSession {
     bumpGate(): void;
 }
 
-export { type AttachmentFailureGroup, type AttachmentParser, type AttachmentSaveInfo, BG_INDEXING_QUEUE_SUFFIX, type BgTaskEntry, type BoundedChatOptions, type BuildDisplayListOptions, type BuildIndexingUserMessageOptions, CLAUDE_PER_REQUEST_INPUT_CAP, CONTEXT_WINDOW_BY_MODEL, CONTEXT_WINDOW_DEFAULT, type CallClaudeWithMcpParams, type ChatEngineConfig, type ChatHost, type ChatIdentity, type ChatMessage, ChatSession, type ChatState, type ChatSystemPromptParams, type ClaudeMcpServerRequest, type ClaudeMcpToolConfig, type ClaudeMessage, type ClaudeRole, type ComposedUserMessage, DEFAULT_CLAUDE_MODEL, DEFAULT_OPENAI_MODEL, type DisplayEntry, EXPIRED_ATTACHMENT_URL_HOST, EXPIRED_ATTACHMENT_URL_ORIGIN, EXPIRED_LINK_REFRESH_EXPIRES_SECONDS, type ExtractDirective, type FillHistoryViewportOptions, HISTORY_FILL_SLACK_PX, HISTORY_TOKEN_BUDGET, type IndexingAttachmentInfo, type IndexingFileRef, type IndexingGroup, type IndexingGroupStatus, type IndexingSystemPromptParams, type InlineLinkContext, type InlineLinkPart, LINK_LABEL_MAX_DISPLAY_CHARS, LINK_REFRESH_WINDOW_MS, MAX_HISTORY_FILL_PAGES, MAX_HISTORY_MESSAGES, MAX_PARSED_CONTENT_CHARS, MCP_NAME, MIN_INPUT_TOKEN_BUDGET, type MapHistoryOptions, OUTPUT_TOKEN_RESERVE, type OpenAIMessage, POLL_INTERVAL, type PinnedDispatchContext, RENDER_FROM_TOKEN, TOOL_AND_RESPONSE_BUFFER, buildBoundedChatMessages, buildChatDisplayList, buildChatSystemPrompt, buildDisplayExpiredAttachmentHref, buildIndexingContinueMessage, buildIndexingRenderContinueTemplate, buildIndexingRenderMessage, buildIndexingSystemPrompt, buildIndexingUserMessage, buildIndexingWindowMessage, callClaudeWithMcp, callClaudeWithPublicMcp, callOpenAIWithPublicMcp, chatEngineConfig, classifyInlineLink, clearAttachmentParsers, composeUserMessage, configureChatEngine, createHistoryFiller, createInlineLinkRegex, encodePathSegments, estimateMessageTokens, estimateTextTokens, extractClaudeText, extractLastUserTextFromRequest, extractOpenAIText, extractRemotePathFromAttachmentHref, fillHistoryViewport, filterListByClearHorizon, findAttachmentParser, getAttachmentParsers, getChatHistory, getContextWindow, getErrorMessage, getExpiredAttachmentVisiblePath, groupAttachmentFailures, isAuthExpiredError, isBgIndexingQueue, isErrorResponseBody, isHttpUrlLike, isNonRetryableRequestError, isOfficeFile, isServerExtractable, isServiceDbAttachmentHref, listClaudeModels, listOpenAIModels, makeExtractPlaceholder, mapHistoryListToMessages, normalizeAttachmentPathCandidate, normalizeTextContent, normalizeTrailingInlineToken, notifyAgentSaveAttachment, parseAttachmentContent, parseIndexingLabel, readExpiredAttachmentHref, registerAttachmentParser, repairUrlWhitespace, safeDecodeURIComponent, sanitizeAttachmentLinksForHistory, stripFileBlocksFromHistory, transformContentWithImages, transformContentWithOpenAIImages, truncateLabelForDisplay };
+export { type AiAgentPlatform, type AttachmentFailureGroup, type AttachmentParser, type AttachmentSaveInfo, BG_INDEXING_QUEUE_SUFFIX, type BgTaskEntry, type BoundedChatOptions, type BuildDisplayListOptions, type BuildIndexingUserMessageOptions, CLAUDE_INPUT_CAP_RATIO, CLAUDE_PER_REQUEST_INPUT_CAP, CONTEXT_WINDOW_BY_MODEL, CONTEXT_WINDOW_DEFAULT, type CallClaudeWithMcpParams, type ChatEngineConfig, type ChatHost, type ChatIdentity, type ChatMessage, ChatSession, type ChatState, type ChatSystemPromptParams, type ClaudeMcpServerRequest, type ClaudeMcpToolConfig, type ClaudeMessage, type ClaudeRole, type ComposedUserMessage, DEFAULT_CLAUDE_MODEL, DEFAULT_OPENAI_MODEL, type DisplayEntry, EXPIRED_ATTACHMENT_URL_HOST, EXPIRED_ATTACHMENT_URL_ORIGIN, EXPIRED_LINK_REFRESH_EXPIRES_SECONDS, type ExtractDirective, type FillHistoryViewportOptions, HISTORY_BUDGET_RATIO, HISTORY_FILL_SLACK_PX, HISTORY_TOKEN_BUDGET, type IndexingAttachmentInfo, type IndexingFileRef, type IndexingGroup, type IndexingGroupStatus, type IndexingRequestRef, type IndexingSystemPromptParams, type InlineLinkContext, type InlineLinkPart, LINK_LABEL_MAX_DISPLAY_CHARS, LINK_REFRESH_WINDOW_MS, MAX_HISTORY_FILL_PAGES, MAX_HISTORY_MESSAGES, MAX_PARSED_CONTENT_CHARS, MCP_NAME, MIN_INPUT_TOKEN_BUDGET, type MapHistoryOptions, OUTPUT_TOKEN_RESERVE, type OpenAIMessage, POLL_INTERVAL, type ParsedAiAgent, type PinnedDispatchContext, RENDER_FROM_TOKEN, TOOL_AND_RESPONSE_BUFFER, buildAiAgentValue, buildBoundedChatMessages, buildChatDisplayList, buildChatSystemPrompt, buildDisplayExpiredAttachmentHref, buildIndexingContinueMessage, buildIndexingRenderContinueTemplate, buildIndexingRenderMessage, buildIndexingSystemPrompt, buildIndexingUserMessage, buildIndexingWindowMessage, callClaudeWithMcp, callClaudeWithPublicMcp, callOpenAIWithPublicMcp, chatEngineConfig, classifyInlineLink, clearAttachmentParsers, composeUserMessage, configureChatEngine, createHistoryFiller, createInlineLinkRegex, encodePathSegments, estimateMessageTokens, estimateTextTokens, extractClaudeText, extractLastUserTextFromRequest, extractOpenAIText, extractRemotePathFromAttachmentHref, fillHistoryViewport, filterListByClearHorizon, findAttachmentParser, formatChatTimestamp, getAttachmentParsers, getChatHistory, getContextWindow, getErrorMessage, getExpiredAttachmentVisiblePath, getProjectContextWindow, groupAttachmentFailures, isAuthExpiredError, isBgIndexingQueue, isErrorResponseBody, isHttpUrlLike, isIndexingRequestText, isNonRetryableRequestError, isOfficeFile, isServerExtractable, isServiceDbAttachmentHref, listClaudeModels, listOpenAIModels, makeExtractPlaceholder, mapHistoryListToMessages, normalizeAttachmentPathCandidate, normalizeTextContent, normalizeTrailingInlineToken, notifyAgentSaveAttachment, parseAiAgentValue, parseAttachmentContent, parseIndexingLabel, parseIndexingRequestText, readExpiredAttachmentHref, registerAttachmentParser, registerModelContextWindows, repairUrlEntities, repairUrlWhitespace, safeDecodeURIComponent, sanitizeAttachmentLinksForHistory, setProjectContextWindow, stripFileBlocksFromHistory, transformContentWithImages, transformContentWithOpenAIImages, truncateLabelForDisplay, wallClockNow };

package/dist/engine.d.ts

@@ -312,18 +312,44 @@ declare function isAuthExpiredError(input: any): boolean;
 
 declare var CONTEXT_WINDOW_DEFAULT: Record<string, number>;
 declare var CONTEXT_WINDOW_BY_MODEL: Record<string, number>;
+/**
+ * Record context windows from a provider models listing. Accepts the raw list
+ * items and reads `max_input_tokens` (Anthropic); items without it are skipped,
+ * so passing an OpenAI listing is a no-op rather than an error.
+ */
+declare function registerModelContextWindows(models: Array<{
+    id?: string;
+    max_input_tokens?: number;
+}> | null | undefined): void;
+declare function setProjectContextWindow(serviceId: string, tokens: number | null | undefined): void;
+declare function getProjectContextWindow(serviceId: string): number | null;
 declare var OUTPUT_TOKEN_RESERVE: number;
 declare var TOOL_AND_RESPONSE_BUFFER: number;
 declare var MIN_INPUT_TOKEN_BUDGET: number;
 declare var CLAUDE_PER_REQUEST_INPUT_CAP: number;
 declare var MAX_HISTORY_MESSAGES: number;
 declare var HISTORY_TOKEN_BUDGET: number;
+declare var CLAUDE_INPUT_CAP_RATIO: number;
+declare var HISTORY_BUDGET_RATIO: number;
 declare function estimateTextTokens(text: string): number;
 declare function estimateMessageTokens(msg: {
     role: string;
     content: string;
 }): number;
-declare function getContextWindow(platform: string, model?: string): number;
+/**
+ * Resolve a model's context window, most specific source first:
+ *   1. per-project override (project settings)
+ *   2. the provider's own models listing (Anthropic `max_input_tokens`)
+ *   3. an exact entry in CONTEXT_WINDOW_BY_MODEL
+ *   4. a family entry, by dropping trailing '-' segments off the id
+ *   5. the platform default
+ *
+ * Step 4 is why a new or suffixed id no longer drops straight to the platform
+ * default: 'gpt-5.6-luna' resolves via 'gpt-5.6', and a dated Claude snapshot
+ * such as 'claude-opus-4-7-20260101' resolves via 'claude-opus-4-7'. The walk
+ * stops at the first hit, so a more specific entry always wins over its family.
+ */
+declare function getContextWindow(platform: string, model?: string, serviceId?: string): number;
 declare function stripFileBlocksFromHistory(content: string): string;
 type BoundedChatOptions = {
     platform: string;
@@ -423,6 +449,21 @@ declare function isHttpUrlLike(target: string): boolean;
  *     space in it, and deleting it points at a file that does not exist.
  */
 declare function repairUrlWhitespace(href: string): string;
+/**
+ * A model reproducing a URL sometimes HTML-escapes its `&` query separators as
+ * `&amp;` (or the numeric `&#38;` / `&#x26;`). Left in the href that escaping
+ * survives the client's own escapeAttr -> v-html/innerHTML decode round-trip and
+ * reaches the browser LITERALLY, so a presigned S3 URL is navigated with its
+ * parameters named `amp;Signature`, `amp;Expires`, `amp;response-content-type`,
+ * ... — the real params vanish, the signature can't be located, and S3 rejects
+ * it (the "링크가 안되" dead export link). Undo just that entity escaping.
+ *
+ * This is a no-op on a clean URL: a valid link carries a raw `&` between params
+ * and percent-encodes (`%26`) any literal ampersand that is data, so a real URL
+ * never contains `&amp;` to begin with. Mirrors repairUrlWhitespace: it repairs
+ * model damage, not the URL. The loop collapses a doubly-escaped `&amp;amp;` too.
+ */
+declare function repairUrlEntities(href: string): string;
 /**
  * Trim punctuation and unmatched wrappers that cling to a token in prose.
  * `src::a/b.pdf).` -> `src::a/b.pdf`, while a balanced `file (v2).pdf` is kept.
@@ -466,9 +507,78 @@ declare function classifyInlineLink(full: string, groups: Array<string | undefin
 } | null;
 declare function truncateLabelForDisplay(label: string): string;
 
+/**
+ * Chat timestamp formatting, shared so agent.vue and the widget render an
+ * identical "small text under the bubble". Pure and locale-aware: it formats a
+ * given epoch-ms value, it never reads the current time, so it stays testable and
+ * DOM-free.
+ */
+/** Wall-clock epoch ms. Separate from the engine's monotonic nowMs() (which is
+ *  performance.now() when available and therefore NOT epoch): a displayed
+ *  timestamp must be wall time. */
+declare function wallClockNow(): number;
+/**
+ * "Jul 24, 2026, 3:42:07 PM" (locale-formatted). Empty string for a missing or
+ * non-finite value, so a caller can gate rendering on the result being truthy and
+ * a pending bubble (no timestamp yet) simply shows nothing.
+ */
+declare function formatChatTimestamp(ms?: number): string;
+
+/**
+ * The `ai_agent` service option, parsed and serialized in ONE place.
+ *
+ * Stored on the skapi service record as up to three '#'-delimited segments:
+ *
+ *   none                                  AI chat disabled
+ *   claude                                platform chosen, no model saved yet
+ *   claude#claude-sonnet-4-6              platform + model
+ *   claude#claude-sonnet-4-6#400000       platform + model + context-window override
+ *
+ * The third segment is new and optional, so every value written before it
+ * existed parses unchanged with `contextWindow: null`. Nothing writes a third
+ * segment without a model, because the window is meaningless without one.
+ *
+ * This lived as four separate copies (agent.vue, dbfile.vue, service.vue, and
+ * the widget's index.js), which is how the format drifts. New callers should
+ * import from here rather than re-deriving the split.
+ */
+type AiAgentPlatform = 'claude' | 'openai' | null;
+type ParsedAiAgent = {
+    /** null when unset or explicitly 'none'. */
+    platform: AiAgentPlatform;
+    /** '' when no model has been saved. */
+    model: string;
+    /** Per-project context-window override in tokens, or null to use the model's. */
+    contextWindow: number | null;
+    /** True when a real platform is configured (i.e. not unset and not 'none'). */
+    hasPlatform: boolean;
+};
+declare function parseAiAgentValue(value: string | null | undefined): ParsedAiAgent;
+declare function buildAiAgentValue(platform: string | null | undefined, model?: string | null, contextWindow?: number | null): string;
+
 declare function filterListByClearHorizon(list: any[], clearedAt: number): any[];
 declare function normalizeTextContent(content: any): string;
 declare function extractLastUserTextFromRequest(requestBody: any): string;
+/** The two openings an indexing prompt can have. A bg-queue item that starts with
+ *  neither is an ordinary chat that happened to be routed onto that queue. */
+declare function isIndexingRequestText(userText: any): boolean;
+type IndexingRequestRef = {
+    name: string;
+    path?: string;
+    mime?: string;
+    size?: number;
+    /** A CONTINUE pass rather than the run's first. */
+    continued: boolean;
+};
+/**
+ * The file an indexing prompt is about, read back out of the prompt itself.
+ *
+ * The prompt is the only description of the pass that survives on the server, so
+ * this is how BOTH a history rebuild and a worker-minted pass the client never
+ * dispatched (ChatSession._adoptWorkerIndexingPasses) recover the file. Shared so
+ * the two produce the same `_indexFile`, which is what makes them group together.
+ */
+declare function parseIndexingRequestText(userText: any): IndexingRequestRef | null;
 type MapHistoryOptions = {
     clearedAt: number;
     serviceId: string;
@@ -681,11 +791,20 @@ type BgTaskEntry = {
     /** How many CONTINUE passes have already run for this file (resume-across-passes). */
     resumePass?: number;
 };
+/**
+ * `queue` narrows the fetch to one processing chain; `status` narrows it to items
+ * in one state. Passing both is how the client asks "is there still unresolved
+ * work on the background-indexing queue?" without pulling a page of chat history
+ * (see ChatSession._adoptWorkerIndexingPasses) — the server answers that from a
+ * status-keyed index, so the reply carries only the live items, not the bodies of
+ * everything already finished.
+ */
 declare function getChatHistory(params: {
     service?: string;
     owner?: string;
     platform: 'claude' | 'openai';
     queue?: string;
+    status?: 'pending' | 'running' | 'resolved' | 'failed';
 }, fetchOptions: Record<string, any>): Promise<any>;
 
 /**
@@ -753,6 +872,12 @@ interface ChatMessage {
     _localId?: string;
     _cancelling?: boolean;
     _cancelError?: string;
+    /** Epoch ms shown as small text under the bubble. From the request history a
+     *  USER bubble carries the request's `created` time and an ASSISTANT bubble the
+     *  `updated` (response) time; a live bubble is stamped with the wall clock when
+     *  it is created, then reconciled to the server value on the next history load.
+     *  Absent while a turn is still pending, so no time shows on a "Thinking" bubble. */
+    _ts?: number;
     _ownerKey?: string;
 }
 interface ChatState {
@@ -845,12 +970,34 @@ interface ChatHost {
  * repeating forever, and any real question the user asks in between gets buried.
  *
  * buildChatDisplayList turns the flat message array into a DISPLAY list in which
- * every message belonging to one file (however far apart they sit, and whatever
- * else is interleaved between them) is represented by a single group entry,
- * rendered at the position of that file's NEWEST turn. Newest, not oldest, so:
- *   - a running index sits at the bottom, where the activity is, and
- *   - paging older history in never moves a row that is already on screen
- *     (older passes simply join the group they already belong to).
+ * every message belonging to one run of one file (however far apart the passes
+ * sit, and whatever else is interleaved between them) is represented by a single
+ * group entry, rendered at the position of that run's FIRST loaded pass.
+ *
+ * First, not newest. The message array is ordered by request CREATION time, and
+ * a run's later passes are created one at a time as the previous one resolves —
+ * by the client for the paged text path, and by the WORKER itself for the
+ * rendered-page (PDF) path, which the client only learns about on its next
+ * first-page history fetch. So a pass is routinely created minutes after the
+ * upload, on a queue that runs in parallel with the foreground chat. Anchoring
+ * at the newest pass meant one such late pass dragged the whole run — every
+ * earlier pass with it — below any question the user had asked in the meantime,
+ * and made a run that had visibly finished before the question render after it.
+ * Anchoring at the first pass puts the row where the run actually began, which
+ * is a position no later pass can change:
+ *   - a new pass never relocates the row, so nothing under the reader shifts;
+ *   - a question asked after the upload always renders below the row, which is
+ *     the order it happened in.
+ * The cost is that a long-running index does not follow the conversation to the
+ * bottom: once the user has chatted past the upload, the spinner and the Stop
+ * button sit above their newest turns. That is a scroll away, and the row no
+ * longer lies about when the work started.
+ *
+ * Paging older history is the one thing that CAN move the row: an older page
+ * carrying earlier passes of a run already on screen moves it up into that page.
+ * That happens at most once per run, only for a run whose start was never
+ * loaded (`mayHaveOlder`), and it is the same event that already re-derives
+ * `runKey` — so the view treats it as a new row either way.
  *
  * The group deliberately reports no authoritative pass TOTAL. History is paged
  * newest-first, so any total computed from loaded messages is a lower bound that
@@ -873,9 +1020,10 @@ type IndexingGroup = {
      *  Monday and re-indexed on Wednesday is two runs, and collapsing them into
      *  one row erased Monday's from Monday's place in the conversation, claimed
      *  its passes for Wednesday, and let Monday's failure be overwritten by
-     *  Wednesday's success. Numbered from the NEWEST run backwards (`#0` is the
-     *  newest) so paging in older history never renames a row already on screen.
-     *  This is the render key and the expansion key. */
+     *  Wednesday's success. Named after the run's FIRST loaded pass (see where it
+     *  is assigned below), so passes appended to the run and other runs appearing
+     *  on either side of it never rename a row already on screen. This is the
+     *  render key and the expansion key. */
     runKey: string;
     name: string;
     path?: string;
@@ -904,8 +1052,16 @@ type IndexingGroup = {
     /** The file's first pass is not among the loaded messages, so earlier passes
      *  exist in history that has not been paged in yet. */
     mayHaveOlder: boolean;
-    /** Position in the source array this collapsed row renders at. */
+    /** Position in the source array this collapsed row renders at: the index of
+     *  the run's FIRST loaded pass (see the file docstring for why not the last). */
     anchorIndex: number;
+    /** Identity of the turn at `anchorIndex` — its server item id, or its local id
+     *  while it has none, or `''` when it has neither. The views stamp this on the
+     *  row (`data-row-pos`) so the scroll anchor can tell a row that RELOCATED (an
+     *  older page moved the run's start) from one that merely gained a pass. They
+     *  must not re-derive it from `members`: which member the row renders at is
+     *  this module's decision, and the two silently disagreed once already. */
+    anchorId: string;
 };
 type DisplayEntry = {
     kind: 'message';
@@ -1083,6 +1239,9 @@ declare class ChatSession {
     _clearPendingUserBubble(itemId: string): void;
     resumePendingRequest(token: number): Promise<void>;
     handleHistoryItemResolution(itemId: string, response: any, platform: string): void;
+    /** The file an already-rendered background pass is about, off its request
+     *  bubble. Null for an ordinary turn, which is most of them. */
+    private _indexRefOfItem;
     applyHistoryItemResolution(itemId: string, response: any, platform: string): void;
     /** How a bg task maps onto a collapsed row: the row's own key (storage path
      *  when known, else the filename), scoped to the chat it belongs to. A storage
@@ -1114,6 +1273,49 @@ declare class ChatSession {
      * Runs from drainBgTaskQueue, which both clients call after a history load.
      */
     private _sweepCancelledIndexing;
+    /**
+     * True when the WORKER, not this client, drives the rest of this file's chain.
+     * The mirror image of the early returns in maybeResumeIndexing: whatever that
+     * refuses to continue is exactly what nothing client-side is tracking.
+     */
+    private _isWorkerDrivenIndexing;
+    /**
+     * Pick up indexing passes the WORKER minted, which no client ever dispatched.
+     *
+     * For a PDF (and for text/grid when windowed indexing is on) the worker writes
+     * pass N+1's row itself, inside pass N's invocation, right after saving pass
+     * N's result. That row reaches this client through nothing at all: it is not in
+     * bgTaskQueue (the client never asked for it) and it is not in state.messages
+     * (only a first-page history load maps it in, which happens on mount, project
+     * switch or tab return). So between two worker passes every pass the client
+     * knows about is settled, and the collapsed row renders "Indexed  N passes"
+     * with no spinner and no Stop, for a file that is still being read. A user who
+     * believes that then asks questions against a half-indexed file — which is what
+     * this exists to prevent.
+     *
+     * So when a background indexing pass settles, ask the bg queue what is still
+     * unresolved on it and adopt anything unknown as an ordinary BgTaskEntry.
+     * drainBgTaskQueue then treats it exactly like a pass this client dispatched:
+     * same bubble, same `_indexFile` (so it joins the file's collapsed row), same
+     * poll — and that poll settling runs this again, so the chain is followed to
+     * its end. `status`-scoped so the reply carries the live items only, never a
+     * page of finished ones with their bodies.
+     *
+     * Termination: the only trigger is a pass SETTLING, which happens once per
+     * pass. An adopted item that is still running is not re-adopted (its id is
+     * already polled), and when the queue holds nothing unknown the chain stops on
+     * its own. Nothing here is periodic — a timer that re-reads history is the
+     * shape that previously looped fetchHistoryPage after an already-DONE index.
+     */
+    private _adoptingWorkerPasses;
+    private _adoptWorkerIndexingPasses;
+    /** Any of these ids still queued or still polled, i.e. surviving work. */
+    private _isTrackingAny;
+    /** One live bg-queue item -> a BgTaskEntry, if it is an indexing pass this
+     *  client is not already tracking. Returns whether it was adopted. */
+    private _adoptWorkerIndexingItem;
+    /** Follow the chain on from a background indexing pass that just settled. */
+    private _followWorkerIndexingChain;
     /** Best-effort server-side cancel of a bg-queue item that has no bubble (so
      *  cancelQueuedMessage, which drives one, has nothing to act on). */
     private _cancelServerItem;
@@ -1134,4 +1336,4 @@ declare class ChatSession {
     bumpGate(): void;
 }
 
-export { type AttachmentFailureGroup, type AttachmentParser, type AttachmentSaveInfo, BG_INDEXING_QUEUE_SUFFIX, type BgTaskEntry, type BoundedChatOptions, type BuildDisplayListOptions, type BuildIndexingUserMessageOptions, CLAUDE_PER_REQUEST_INPUT_CAP, CONTEXT_WINDOW_BY_MODEL, CONTEXT_WINDOW_DEFAULT, type CallClaudeWithMcpParams, type ChatEngineConfig, type ChatHost, type ChatIdentity, type ChatMessage, ChatSession, type ChatState, type ChatSystemPromptParams, type ClaudeMcpServerRequest, type ClaudeMcpToolConfig, type ClaudeMessage, type ClaudeRole, type ComposedUserMessage, DEFAULT_CLAUDE_MODEL, DEFAULT_OPENAI_MODEL, type DisplayEntry, EXPIRED_ATTACHMENT_URL_HOST, EXPIRED_ATTACHMENT_URL_ORIGIN, EXPIRED_LINK_REFRESH_EXPIRES_SECONDS, type ExtractDirective, type FillHistoryViewportOptions, HISTORY_FILL_SLACK_PX, HISTORY_TOKEN_BUDGET, type IndexingAttachmentInfo, type IndexingFileRef, type IndexingGroup, type IndexingGroupStatus, type IndexingSystemPromptParams, type InlineLinkContext, type InlineLinkPart, LINK_LABEL_MAX_DISPLAY_CHARS, LINK_REFRESH_WINDOW_MS, MAX_HISTORY_FILL_PAGES, MAX_HISTORY_MESSAGES, MAX_PARSED_CONTENT_CHARS, MCP_NAME, MIN_INPUT_TOKEN_BUDGET, type MapHistoryOptions, OUTPUT_TOKEN_RESERVE, type OpenAIMessage, POLL_INTERVAL, type PinnedDispatchContext, RENDER_FROM_TOKEN, TOOL_AND_RESPONSE_BUFFER, buildBoundedChatMessages, buildChatDisplayList, buildChatSystemPrompt, buildDisplayExpiredAttachmentHref, buildIndexingContinueMessage, buildIndexingRenderContinueTemplate, buildIndexingRenderMessage, buildIndexingSystemPrompt, buildIndexingUserMessage, buildIndexingWindowMessage, callClaudeWithMcp, callClaudeWithPublicMcp, callOpenAIWithPublicMcp, chatEngineConfig, classifyInlineLink, clearAttachmentParsers, composeUserMessage, configureChatEngine, createHistoryFiller, createInlineLinkRegex, encodePathSegments, estimateMessageTokens, estimateTextTokens, extractClaudeText, extractLastUserTextFromRequest, extractOpenAIText, extractRemotePathFromAttachmentHref, fillHistoryViewport, filterListByClearHorizon, findAttachmentParser, getAttachmentParsers, getChatHistory, getContextWindow, getErrorMessage, getExpiredAttachmentVisiblePath, groupAttachmentFailures, isAuthExpiredError, isBgIndexingQueue, isErrorResponseBody, isHttpUrlLike, isNonRetryableRequestError, isOfficeFile, isServerExtractable, isServiceDbAttachmentHref, listClaudeModels, listOpenAIModels, makeExtractPlaceholder, mapHistoryListToMessages, normalizeAttachmentPathCandidate, normalizeTextContent, normalizeTrailingInlineToken, notifyAgentSaveAttachment, parseAttachmentContent, parseIndexingLabel, readExpiredAttachmentHref, registerAttachmentParser, repairUrlWhitespace, safeDecodeURIComponent, sanitizeAttachmentLinksForHistory, stripFileBlocksFromHistory, transformContentWithImages, transformContentWithOpenAIImages, truncateLabelForDisplay };
+export { type AiAgentPlatform, type AttachmentFailureGroup, type AttachmentParser, type AttachmentSaveInfo, BG_INDEXING_QUEUE_SUFFIX, type BgTaskEntry, type BoundedChatOptions, type BuildDisplayListOptions, type BuildIndexingUserMessageOptions, CLAUDE_INPUT_CAP_RATIO, CLAUDE_PER_REQUEST_INPUT_CAP, CONTEXT_WINDOW_BY_MODEL, CONTEXT_WINDOW_DEFAULT, type CallClaudeWithMcpParams, type ChatEngineConfig, type ChatHost, type ChatIdentity, type ChatMessage, ChatSession, type ChatState, type ChatSystemPromptParams, type ClaudeMcpServerRequest, type ClaudeMcpToolConfig, type ClaudeMessage, type ClaudeRole, type ComposedUserMessage, DEFAULT_CLAUDE_MODEL, DEFAULT_OPENAI_MODEL, type DisplayEntry, EXPIRED_ATTACHMENT_URL_HOST, EXPIRED_ATTACHMENT_URL_ORIGIN, EXPIRED_LINK_REFRESH_EXPIRES_SECONDS, type ExtractDirective, type FillHistoryViewportOptions, HISTORY_BUDGET_RATIO, HISTORY_FILL_SLACK_PX, HISTORY_TOKEN_BUDGET, type IndexingAttachmentInfo, type IndexingFileRef, type IndexingGroup, type IndexingGroupStatus, type IndexingRequestRef, type IndexingSystemPromptParams, type InlineLinkContext, type InlineLinkPart, LINK_LABEL_MAX_DISPLAY_CHARS, LINK_REFRESH_WINDOW_MS, MAX_HISTORY_FILL_PAGES, MAX_HISTORY_MESSAGES, MAX_PARSED_CONTENT_CHARS, MCP_NAME, MIN_INPUT_TOKEN_BUDGET, type MapHistoryOptions, OUTPUT_TOKEN_RESERVE, type OpenAIMessage, POLL_INTERVAL, type ParsedAiAgent, type PinnedDispatchContext, RENDER_FROM_TOKEN, TOOL_AND_RESPONSE_BUFFER, buildAiAgentValue, buildBoundedChatMessages, buildChatDisplayList, buildChatSystemPrompt, buildDisplayExpiredAttachmentHref, buildIndexingContinueMessage, buildIndexingRenderContinueTemplate, buildIndexingRenderMessage, buildIndexingSystemPrompt, buildIndexingUserMessage, buildIndexingWindowMessage, callClaudeWithMcp, callClaudeWithPublicMcp, callOpenAIWithPublicMcp, chatEngineConfig, classifyInlineLink, clearAttachmentParsers, composeUserMessage, configureChatEngine, createHistoryFiller, createInlineLinkRegex, encodePathSegments, estimateMessageTokens, estimateTextTokens, extractClaudeText, extractLastUserTextFromRequest, extractOpenAIText, extractRemotePathFromAttachmentHref, fillHistoryViewport, filterListByClearHorizon, findAttachmentParser, formatChatTimestamp, getAttachmentParsers, getChatHistory, getContextWindow, getErrorMessage, getExpiredAttachmentVisiblePath, getProjectContextWindow, groupAttachmentFailures, isAuthExpiredError, isBgIndexingQueue, isErrorResponseBody, isHttpUrlLike, isIndexingRequestText, isNonRetryableRequestError, isOfficeFile, isServerExtractable, isServiceDbAttachmentHref, listClaudeModels, listOpenAIModels, makeExtractPlaceholder, mapHistoryListToMessages, normalizeAttachmentPathCandidate, normalizeTextContent, normalizeTrailingInlineToken, notifyAgentSaveAttachment, parseAiAgentValue, parseAttachmentContent, parseIndexingLabel, parseIndexingRequestText, readExpiredAttachmentHref, registerAttachmentParser, registerModelContextWindows, repairUrlEntities, repairUrlWhitespace, safeDecodeURIComponent, sanitizeAttachmentLinksForHistory, setProjectContextWindow, stripFileBlocksFromHistory, transformContentWithImages, transformContentWithOpenAIImages, truncateLabelForDisplay, wallClockNow };