@prismshadow/penguin-server 0.2.8 → 0.2.9

package/dist/api/types.d.ts

@@ -615,6 +615,13 @@ interface ModelOAuthStatusResponse {
     status: "pending" | "done" | "error";
     /** The provider group the flow mints a key for. */
     provider: string;
+    /**
+     * How many models the minted key was written to — set on the `done` answer, the way
+     * {@link ModelOAuthCodeResponse} sets it on a redemption. The dialog reports this number, so
+     * it has to be the server's own: the caller's model table can outlive a rejected save and
+     * would otherwise name a count the server never wrote.
+     */
+    applied?: number;
     error?: ModelOAuthErrorCode;
 }
 /**
@@ -1483,7 +1490,7 @@ interface SessionProcessesResponse {
     processes: SessionProcessInfo[];
 }
 /** Messaging channels a Session can bind to. */
-type MessagingChannel = "feishu" | "telegram" | "qq";
+type MessagingChannel = "feishu" | "telegram" | "qq" | "wechat";
 /** Event-connection runtime state of one binding (kept in memory, not persisted). */
 type MessagingRuntimeState = "disconnected" | "connecting" | "connected" | "error";
 /**
@@ -1542,18 +1549,24 @@ interface MessagingRuntimeStatus {
         detail: string;
     };
 }
-/** The stored Feishu config, secret masked (plaintext never leaves the server). */
-interface FeishuBindingInfo {
-    channel: "feishu";
+/**
+ * What a messaging binding carries whatever channel it is: the connection intent, the three
+ * delivery preferences, whether a chat is known, and the row's identity and timestamps.
+ *
+ * Split out because this is the half that grows. Three delivery preferences arrived in one
+ * release, and each would otherwise have been written into three interfaces — the credential
+ * slice is the only thing a channel genuinely differs in, and it is what stays per-channel.
+ *
+ * `channel` is NOT here: a discriminated union discriminates on a literal the member itself
+ * declares, so each interface keeps its own.
+ *
+ * A channel may RE-DECLARE a field below when it has more to say about it — QQ does, for all
+ * three preferences, because the platform's passive-reply budget and its expiring window
+ * change what setting one costs there. The re-declared type must be identical, which the
+ * compiler enforces, so the redeclaration can only add documentation and never a contract.
+ */
+interface MessagingBindingCommon {
     sessionId: string;
-    appId: string;
-    /**
-     * Masked app secret (site-wide mask rule: `***`, or `first4…last4` for long values);
-     * absent when no secret is stored (never entered, or cleared) — the binding cannot be
-     * enabled until one is saved.
-     */
-    appSecretMasked?: string;
-    baseDomain: string;
     /** Connection INTENT (the state toggle's value); new bindings start disabled, and at most one of a Session's channels is enabled. */
     enabled: boolean;
     /**
@@ -1571,23 +1584,35 @@ interface FeishuBindingInfo {
     /**
      * Render a relayed reply's Markdown in this channel's own markup instead of sending its
      * characters as written. ON by default. Each channel shows what it can — Telegram has no
-     * headings, lists or tables, QQ has no code or tables, Feishu has all of them — and a
+     * headings, lists or tables, QQ has no code or tables, Feishu has all of them, and WeChat
+     * reads Markdown itself so the render is a subtraction rather than a translation — and a
      * rendering the channel refuses falls back to the plain source, so this can cost
      * formatting and never a message.
      */
     renderMarkdown: boolean;
     /**
-     * Whether an inbound Feishu chat is known (the bot has been messaged at least once).
-     * Replies and test messages target that chat; until it exists nothing can be sent.
+     * Whether an inbound chat is known (the bot has been messaged at least once). Replies and
+     * test messages target that chat; until it exists nothing can be sent.
      */
     lastChatKnown: boolean;
     createdAt: string;
     updatedAt: string;
 }
+/** The stored Feishu config, secret masked (plaintext never leaves the server). */
+interface FeishuBindingInfo extends MessagingBindingCommon {
+    channel: "feishu";
+    appId: string;
+    /**
+     * Masked app secret (site-wide mask rule: `***`, or `first4…last4` for long values);
+     * absent when no secret is stored (never entered, or cleared) — the binding cannot be
+     * enabled until one is saved.
+     */
+    appSecretMasked?: string;
+    baseDomain: string;
+}
 /** The stored Telegram config, token masked (plaintext never leaves the server). */
-interface TelegramBindingInfo {
+interface TelegramBindingInfo extends MessagingBindingCommon {
     channel: "telegram";
-    sessionId: string;
     /** The numeric bot id (the token's half before the colon) — the channel-scoped account identity, never secret. */
     botId: string;
     /**
@@ -1596,40 +1621,15 @@ interface TelegramBindingInfo {
      * is saved.
      */
     botTokenMasked?: string;
-    /** Connection INTENT (the state toggle's value); new bindings start disabled, and at most one of a Session's channels is enabled. */
-    enabled: boolean;
-    /**
-     * Send each non-blank line of a relayed assistant reply as its own message instead of one
-     * message per reply. Off by default; off is the original one-message-per-reply behaviour.
-     */
-    linePerMessage: boolean;
-    /**
-     * Relay only the LAST completed assistant message of a run, delivered when the run ends,
-     * instead of mirroring each completed message as it completes. Off by default; off is the
-     * original every-message behaviour. Independent of `linePerMessage`, which then applies to
-     * that one final message. The approval notice is not a reply and is unaffected.
-     */
-    finalReplyOnly: boolean;
-    /**
-     * Render a relayed reply's Markdown in this channel's own markup instead of sending its
-     * characters as written. ON by default. Each channel shows what it can — Telegram has no
-     * headings, lists or tables, QQ has no code or tables, Feishu has all of them — and a
-     * rendering the channel refuses falls back to the plain source, so this can cost
-     * formatting and never a message.
-     */
-    renderMarkdown: boolean;
-    /**
-     * Whether an inbound Telegram chat is known (the bot has been messaged at least once).
-     * Replies and test messages target that chat; until it exists nothing can be sent.
-     */
-    lastChatKnown: boolean;
-    createdAt: string;
-    updatedAt: string;
 }
-/** The stored QQ config, secret masked (plaintext never leaves the server). */
-interface QQBindingInfo {
+/**
+ * The stored QQ config, secret masked (plaintext never leaves the server).
+ *
+ * The three preference fields are re-declared unchanged: every one of them costs something
+ * different here, and the platform's reply budget is what a reader setting one needs to know.
+ */
+interface QQBindingInfo extends MessagingBindingCommon {
     channel: "qq";
-    sessionId: string;
     /** The bot's App ID — the channel-scoped account identity, never secret. */
     appId: string;
     /**
@@ -1638,8 +1638,6 @@ interface QQBindingInfo {
      * enabled until one is saved.
      */
     appSecretMasked?: string;
-    /** Connection INTENT (the state toggle's value); new bindings start disabled, and at most one of a Session's channels is enabled. */
-    enabled: boolean;
     /**
      * Send each non-blank line of a relayed assistant reply as its own message instead of one
      * message per reply. Off by default. On QQ the split is additionally capped at the
@@ -1648,10 +1646,8 @@ interface QQBindingInfo {
      */
     linePerMessage: boolean;
     /**
-     * Relay only the LAST completed assistant message of a run, delivered when the run ends,
-     * instead of mirroring each completed message as it completes. Off by default; off is the
-     * original every-message behaviour. Independent of `linePerMessage`, which then applies to
-     * that one final message. The approval notice is not a reply and is unaffected.
+     * Relay only the LAST completed assistant message of a run, delivered when the run ends.
+     * Off by default.
      *
      * On QQ it cuts both ways, which is worth knowing before setting it here. It spends the
      * least of the platform's passive-reply budget a run can spend — one message, where an
@@ -1662,25 +1658,41 @@ interface QQBindingInfo {
      */
     finalReplyOnly: boolean;
     /**
-     * Render a relayed reply's Markdown in this channel's own markup instead of sending its
-     * characters as written. ON by default. QQ's own subset is the widest for prose and the
-     * narrowest for code: headings, lists, blockquotes and rules render, while inline code,
-     * fenced code and tables have no syntax at all here — a code block arrives as plain
-     * escaped lines. A rendering the platform refuses falls back to the plain source, at the
-     * cost of one more slot from the passive-reply budget.
+     * Render a relayed reply's Markdown in this channel's own markup. ON by default. QQ's own
+     * subset is the widest for prose and the narrowest for code: headings, lists, blockquotes
+     * and rules render, while inline code, fenced code and tables have no syntax at all here —
+     * a code block arrives as plain escaped lines. A rendering the platform refuses falls back
+     * to the plain source, at the cost of one more slot from the passive-reply budget.
      */
     renderMarkdown: boolean;
     /**
-     * Whether an inbound QQ chat is known (the bot has been messaged at least once).
-     * Weaker than it looks on this channel: QQ accepts only replies to a recent message, so a
-     * known chat is necessary but not sufficient for anything to be deliverable right now.
+     * Whether an inbound QQ chat is known (the bot has been messaged at least once). Weaker
+     * than it looks on this channel: QQ accepts only replies to a recent message, so a known
+     * chat is necessary but not sufficient for anything to be deliverable right now.
      */
     lastChatKnown: boolean;
-    createdAt: string;
-    updatedAt: string;
+}
+/**
+ * The stored WeChat config, token masked (plaintext never leaves the server).
+ *
+ * No preference field is re-declared. The three delivery preferences cost exactly what they
+ * cost on Feishu and Telegram here — this channel has no reply budget and no expiring reply
+ * window — and re-declaring a field to say nothing new about it would only invite the next
+ * reader to look for the difference.
+ */
+interface WeChatBindingInfo extends MessagingBindingCommon {
+    channel: "wechat";
+    /** The bot id a scan issued — the channel-scoped account identity, never secret. */
+    botId: string;
+    /**
+     * Masked bot token (site-wide mask rule: `***`, or `first4…last4` for long values);
+     * absent when none is stored (cleared, or a scan that never completed) — the binding
+     * cannot be enabled until a scan saves one.
+     */
+    botTokenMasked?: string;
 }
 /** A Session's saved config for one messaging channel (`channel` is the discriminant). */
-type MessagingBindingInfo = FeishuBindingInfo | TelegramBindingInfo | QQBindingInfo;
+type MessagingBindingInfo = FeishuBindingInfo | TelegramBindingInfo | QQBindingInfo | WeChatBindingInfo;
 /** One saved channel config with its event-connection runtime status. */
 interface MessagingChannelState {
     binding: MessagingBindingInfo;
@@ -1710,12 +1722,32 @@ interface QQBindingResponse {
     binding: QQBindingInfo | null;
     status: MessagingRuntimeStatus;
 }
+/** GET / PUT …/messaging/wechat response (the WeChat narrowing of the same envelope). */
+interface WeChatBindingResponse {
+    binding: WeChatBindingInfo | null;
+    status: MessagingRuntimeStatus;
+}
 /**
  * PUT …/messaging/feishu — saves credentials/config ONLY, never flipping the connection
  * (exception: an enabled binding's connector restarts with the new credentials so stored
  * config and live connection never diverge). The connection toggle is POST …/state.
  */
-interface FeishuBindingPutRequest {
+/**
+ * The delivery preferences any channel's PUT may set. Each is optional and each behaves the
+ * same way on every channel: an omitted field keeps the stored value, so a client that knows
+ * about one preference can save it without having to send the others back. Their meanings are
+ * on {@link MessagingBindingCommon}, and where a channel charges differently for one, on that
+ * channel's own `*BindingInfo`.
+ *
+ * The defaults a binding created without them starts from: `linePerMessage` off,
+ * `finalReplyOnly` off, `renderMarkdown` ON.
+ */
+interface MessagingDeliveryPatch {
+    linePerMessage?: boolean;
+    finalReplyOnly?: boolean;
+    renderMarkdown?: boolean;
+}
+interface FeishuBindingPutRequest extends MessagingDeliveryPatch {
     appId: string;
     /** Omitted or blank keeps the stored secret (the masked value never round-trips). */
     appSecret?: string;
@@ -1726,21 +1758,6 @@ interface FeishuBindingPutRequest {
      * it). Refused with 409 `messaging_disable_before_clear` while the binding is enabled.
      */
     clearAppSecret?: boolean;
-    /**
-     * Delivery preference (see `FeishuBindingInfo.linePerMessage`). Omitted keeps the stored
-     * value; a binding created without it starts with it off.
-     */
-    linePerMessage?: boolean;
-    /**
-     * Delivery preference (see `FeishuBindingInfo.finalReplyOnly`). Omitted keeps the stored
-     * value; a binding created without it starts with it off.
-     */
-    finalReplyOnly?: boolean;
-    /**
-     * Delivery preference (see `FeishuBindingInfo.renderMarkdown`). Omitted keeps the stored
-     * value; a binding created without it starts with it ON.
-     */
-    renderMarkdown?: boolean;
 }
 /**
  * PUT …/messaging/telegram — saves the credential ONLY, same contract as the Feishu PUT
@@ -1748,7 +1765,7 @@ interface FeishuBindingPutRequest {
  * POST …/state). Saving never conflicts across Sessions: the same bot may sit saved on
  * several, and only enabling it is exclusive.
  */
-interface TelegramBindingPutRequest {
+interface TelegramBindingPutRequest extends MessagingDeliveryPatch {
     /** Omitted or blank keeps the stored token (the masked value never round-trips). */
     botToken?: string;
     /**
@@ -1757,21 +1774,6 @@ interface TelegramBindingPutRequest {
      * `messaging_disable_before_clear` while the binding is enabled.
      */
     clearBotToken?: boolean;
-    /**
-     * Delivery preference (see `TelegramBindingInfo.linePerMessage`). Omitted keeps the stored
-     * value; a binding created without it starts with it off.
-     */
-    linePerMessage?: boolean;
-    /**
-     * Delivery preference (see `TelegramBindingInfo.finalReplyOnly`). Omitted keeps the stored
-     * value; a binding created without it starts with it off.
-     */
-    finalReplyOnly?: boolean;
-    /**
-     * Delivery preference (see `TelegramBindingInfo.renderMarkdown`). Omitted keeps the stored
-     * value; a binding created without it starts with it ON.
-     */
-    renderMarkdown?: boolean;
 }
 /**
  * PUT …/messaging/qq — saves the credential pair ONLY, same contract as the Feishu PUT
@@ -1779,7 +1781,7 @@ interface TelegramBindingPutRequest {
  * is POST …/state). The App ID is the account identity, so changing it rebinds the row to
  * a different bot and drops the remembered chat.
  */
-interface QQBindingPutRequest {
+interface QQBindingPutRequest extends MessagingDeliveryPatch {
     appId: string;
     /** Omitted or blank keeps the stored secret (the masked value never round-trips). */
     appSecret?: string;
@@ -1788,21 +1790,23 @@ interface QQBindingPutRequest {
      * it). Refused with 409 `messaging_disable_before_clear` while the binding is enabled.
      */
     clearAppSecret?: boolean;
+}
+/**
+ * PUT …/messaging/wechat — the delivery preferences ONLY.
+ *
+ * The one PUT on this router that carries no credential, because there is none to carry: a
+ * WeChat bot token exists only where a scan put it, and there is no console to copy one out
+ * of. Saving therefore presupposes a binding — a PUT before any scan answers 400
+ * `wechat_token_required` rather than creating an empty row — and the connection toggle
+ * stays POST …/state, as on every channel.
+ */
+interface WeChatBindingPutRequest extends MessagingDeliveryPatch {
     /**
-     * Delivery preference (see `QQBindingInfo.linePerMessage`). Omitted keeps the stored
-     * value; a binding created without it starts with it off.
-     */
-    linePerMessage?: boolean;
-    /**
-     * Delivery preference (see `QQBindingInfo.finalReplyOnly`). Omitted keeps the stored
-     * value; a binding created without it starts with it off.
-     */
-    finalReplyOnly?: boolean;
-    /**
-     * Delivery preference (see `QQBindingInfo.renderMarkdown`). Omitted keeps the stored
-     * value; a binding created without it starts with it ON.
+     * Drops the STORED token (the models-page clear idiom). Refused with 409
+     * `messaging_disable_before_clear` while the binding is enabled. The row and its bot
+     * identity stay; only a fresh scan can make it connectable again.
      */
-    renderMarkdown?: boolean;
+    clearBotToken?: boolean;
 }
 /**
  * POST …/messaging/<channel>/state — enable connects with the STORED credentials,
@@ -1895,6 +1899,82 @@ interface QQScanPollResponse {
     /** The saved binding, present on `completed` so the editor refreshes without a second GET. */
     binding?: QQBindingInfo;
 }
+/**
+ * WeChat credential-test outcome. There is no request body and no draft to probe: this
+ * channel's credential exists only where a scan put it, so the test always probes the STORED
+ * binding. It answers 400 `wechat_token_required` when there is none.
+ *
+ * No account label, for the same reason QQ has none: the probe (`getconfig`) reports the
+ * bot's settings and names neither the bot nor the person.
+ */
+interface WeChatTestResponse {
+    ok: boolean;
+    latencyMs?: number;
+    error?: string;
+}
+/**
+ * POST …/messaging/wechat/scan — starts a scan-to-connect flow, which on this channel is the
+ * ONLY way to bind: the bot token has no console to be copied out of.
+ *
+ * The server registers a code and answers with what the browser may know. The platform's own
+ * poll handle is absent from this type on purpose — it is what collects the bot token, so it
+ * never leaves the server, and `taskId` is a handle this server mints in its place.
+ */
+interface WeChatScanStartResponse {
+    /** Opaque scan handle, passed back to the poll, verify and cancel endpoints. */
+    taskId: string;
+    /** The URL to ENCODE into a QR code. It is opened by WeChat, never fetched by the browser. */
+    qrUrl: string;
+    /** How often to poll, in milliseconds. */
+    pollMs: number;
+}
+/**
+ * Where a WeChat scan stands. Richer than QQ's four states because the flow is: WeChat
+ * separates scanning from confirming, and may interpose a pairing code shown on the phone.
+ *
+ * - `pending` — the code is up and nothing has happened; keep polling.
+ * - `scanned` — scanned; the phone is showing the confirmation prompt.
+ * - `need_verify_code` — the phone is showing digits that must be sent to the verify
+ *   endpoint before the bind proceeds.
+ * - `blocked` — too many wrong pairing codes; the code is spent and a new scan is needed.
+ * - `expired` — the code lapsed before it was used; show a new one.
+ * - `already_bound` — this bot is already bound to this server, so no new credentials were
+ *   issued and nothing was saved. Not a failure: the existing binding still works.
+ * - `completed` — the server has already SAVED the binding; `botId` names the bot.
+ */
+type WeChatScanStatus = "pending" | "scanned" | "need_verify_code" | "blocked" | "expired" | "already_bound" | "completed";
+/**
+ * POST …/messaging/wechat/scan/poll — one step of the scan.
+ *
+ * `completed` means the server has decrypted nothing and stored everything: the credentials
+ * went from the platform into storage without passing through the browser. Saving is all it
+ * does — enabling the connection stays the separate, exclusive act it is on every channel. A
+ * task id that is unknown, belongs to another Session, or was already resolved answers 404
+ * `wechat_scan_task_unknown`.
+ *
+ * Unlike QQ's poll, an overlapping request answers `pending` rather than 404: the upstream
+ * call is a LONG poll, so one of them spans several of the client's intervals, and that
+ * overlap is the normal rhythm rather than a replay.
+ */
+interface WeChatScanPollResponse {
+    status: WeChatScanStatus;
+    /** The bound bot's id; present only on `completed`. Never the token. */
+    botId?: string;
+    /** The saved binding, present on `completed` so the editor refreshes without a second GET. */
+    binding?: WeChatBindingInfo;
+}
+/**
+ * POST …/messaging/wechat/scan/verify — the digits WeChat showed on the phone.
+ *
+ * They ride the NEXT poll rather than a request of their own, because the platform takes the
+ * pairing code as a parameter of the status call: this endpoint records them and answers
+ * 204. A wrong code is not reported here — the next poll asks for one again, which is how
+ * the platform reports it.
+ */
+interface WeChatScanVerifyRequest {
+    taskId: string;
+    verifyCode: string;
+}
 /**
  * POST …/messaging/<channel>/test-message — sent to the last known chat (409
  * `feishu_no_chat` / `telegram_no_chat` / `qq_no_chat` before one exists). On QQ this can
@@ -2450,6 +2530,23 @@ interface UsageModelSeries extends UsageEntitySeriesCounts {
     provider: string;
     modelId: string;
 }
+/**
+ * Lifetime Token total for one Model, keyed by the (provider, modelId) pair. Deliberately
+ * unfiltered — no date range, no Agent: it answers "how much has this model been used", a
+ * question with no window attached, and the models page that shows it carries no filters of its
+ * own to honour. Models never used are absent rather than zero.
+ */
+interface UsageModelTotal {
+    provider: string;
+    modelId: string;
+    /** The three buckets summed (cache read + cache write + output), matching the cost center's Token figure. */
+    tokens: number;
+    requests: number;
+}
+/** Response of `GET /usage/model-totals`. */
+interface UsageModelTotals {
+    totals: UsageModelTotal[];
+}
 /**
  * The two categories an error record is filed under: `unexpected` is a 500 or an unforeseen
  * runtime exception, `expected` an HttpError / business 4xx. The panel separates them by
@@ -2481,6 +2578,15 @@ interface UsageErrorItem {
  */
 interface UsageErrors {
     total: number;
+    /**
+     * How many of {@link total} a clear would actually take (see {@link UsageErrorsClearResponse}).
+     *
+     * The same as `total` for an ordinary member, and smaller for an admin, whose reads include
+     * unattributed rows that no Project-scoped clear removes. The confirmation is the only place
+     * this matters, and it is the place it matters most: an irreversible delete has to name the
+     * number that will really go, not the number on screen.
+     */
+    clearable: number;
     /** Count of unexpected ones (500 / runtime exceptions) among them — the part the frontend highlights. */
     unexpected: number;
     /** The most frequent source · code (null when there are no errors). */
@@ -2502,6 +2608,18 @@ interface UsageErrorsPage {
     /** Filtered row count, so the caller knows when it has reached the end. */
     total: number;
 }
+/**
+ * DELETE /api/projects/:projectId/usage/errors — empties the error table for the filter the
+ * panel is showing (its date range and Agent), Project owner only.
+ *
+ * Scoped to the filter rather than the Project's whole history, so a clear takes exactly the
+ * rows on screen. Errors with no Project attribution are never included, whoever asks: they
+ * belong to no Project and are surfaced in every Project's admin view.
+ */
+interface UsageErrorsClearResponse {
+    /** How many rows were deleted, so the caller can say what went instead of guessing. */
+    deleted: number;
+}
 interface UsageResponse {
     summary: {
         today: UsageBucket;
@@ -2863,4 +2981,4 @@ interface MachinesResponse {
     job: MachineInstallJob | null;
 }
 
-export type { AdminPasswordResetRequest, AdminUserCreateRequest, AdminUserCreateResponse, AdminUsersResponse, AgentCompactionConfigDto, AgentConfigDto, AgentConfigResponse, AgentConfigUpdateRequest, AgentCreateRequest, AgentCreateResponse, AgentImportRequest, AgentImportResponse, AgentKernelUpdateResponse, AgentMemoryConfigDto, AgentModelConfigDto, AgentSchedulesConfigDto, AgentSkillsConfigDto, AgentSkillsResponse, AgentSummary, AgentTraceDateGroup, AgentTraceFileRef, AgentTraceSessionEntry, AgentTraceSessionFile, AgentTraceSessionGroup, AgentTracesResponse, AgentVaultConfigDto, AgentsResponse, ApprovalDecisionRequest, ApprovalMode, AuthLoginRequest, AuthResponse, BenchmarkCaseScore, BenchmarkCaseSummary, BenchmarkCasesResponse, BenchmarkEvaluation, BenchmarkRunScore, BenchmarkSummary, BenchmarksResponse, CaseMaterial, ChatDefaultsDto, CommandPolicyDto, CommandPolicyRuleDto, ContextToolShare, CredentialInfo, DefaultModelResponse, DefaultModelUpdateRequest, DesktopUpdateStatus, DesktopUpdateStatusResponse, DesktopUpdaterCommandMessage, DesktopUpdaterStatusMessage, DirEntryInfo, DirListResponse, DirectorySkillItem, DirectorySkillsResponse, DraftShortcut, EndpointModelListRequest, EndpointModelListResponse, ErrorBody, FeishuBindingInfo, FeishuBindingPutRequest, FeishuBindingResponse, FeishuTestRequest, FeishuTestResponse, FilesStatRequest, FilesStatResponse, GoalResponse, GoalServerEvent, GoalStateView, HistoryMessage, InstallResponse, MachineInfo, MachineInstallJob, MachinesResponse, McpServerTestResponse, MeResponse, MemberAddRequest, MemberAddResponse, MemberInfo, MembersResponse, MemoryFileInfo, MemoryFileResponse, MemoryFilesResponse, MemoryImportMode, MemoryImportRequest, MemoryImportResponse, MemoryOverviewResponse, MemoryScopeExport, MemoryScopeInfo, MemoryTransferFile, MessagesLiveTail, MessagesPageInfo, MessagesResponse, MessagingBindingInfo, MessagingBindingStateRequest, MessagingBindingsResponse, MessagingChannel, MessagingChannelState, MessagingDeliveryError, MessagingRuntimeState, MessagingRuntimeStatus, MessagingTestMessageResponse, ModelInfo, ModelOAuthCodeRequest, ModelOAuthCodeResponse, ModelOAuthErrorCode, ModelOAuthMode, ModelOAuthStartRequest, ModelOAuthStartResponse, ModelOAuthStatusResponse, ModelPricingDto, ModelProtocolDetectRequest, ModelProtocolDetectResponse, ModelProtocolProbeDto, ModelRefDto, ModelTestRequest, ModelTestResponse, ModelUpdateEntry, ModelVisionDetectRequest, ModelVisionDetectResponse, ModelVisionOutcome, ModelsResponse, ModelsUpdateRequest, PasswordChangeRequest, PendingFollowUpInfo, PendingSteeringInfo, PrefsResponse, ProjectCreateRequest, ProjectCreateResponse, ProjectRole, ProjectSummary, ProjectUpdateRequest, ProjectUpdateResponse, ProjectsResponse, ProtocolProbeOutcome, QQBindingInfo, QQBindingPutRequest, QQBindingResponse, QQScanPollResponse, QQScanStartResponse, QQTestRequest, QQTestResponse, RecalledMessageResponse, RequestSpan, RetryNowResponse, ScheduleItem, ScheduleServerEvent, ScheduleStatus, ScheduleUpsertRequest, SchedulesResponse, ServerEvent, ServerSettings, ServerSettingsResponse, ServerSettingsUpdateRequest, SessionCategory, SessionCategoryCounts, SessionContextParts, SessionContextResponse, SessionCreateRequest, SessionCreateResponse, SessionForkRequest, SessionForkResponse, SessionInfo, SessionPatchRequest, SessionProcessInfo, SessionProcessesResponse, SessionResponse, SessionSource, SessionStatus, SessionTracesResponse, SessionsResponse, SkillArchiveInstallRequest, SkillGroupItem, SkillInstallRequest, SkillLibraryResponse, SkillMetadataItem, SkillUpdateRef, SteerRequest, SubagentMessageResponse, SubagentRuntimeInfo, TaskCreateRequest, TaskCreateResponse, TaskInputPart, TelegramBindingInfo, TelegramBindingPutRequest, TelegramBindingResponse, TelegramTestRequest, TelegramTestResponse, ToolCallSpan, TraceAnalysisResponse, TraceEventsResponse, TraceFileInfo, TraceImportRequest, TraceImportResponse, TraceModelSegment, TraceOtherSpan, TracePosition, TraceTaskStats, TraceToolSpan, UiPrefs, UpdateCheckResponse, UpdateRunResponse, UploadLimits, UsageAgentSeries, UsageBucket, UsageEntitySeriesCounts, UsageErrorCount, UsageErrorItem, UsageErrorKind, UsageErrors, UsageErrorsPage, UsageGranularity, UsageGroupBy, UsageGroupRow, UsageModelSeries, UsageResponse, UsageSeriesPoint, UsageTrendPointInTrace, UserInfo, VaultEntryInfo, VaultEntryUpdate, VaultResponse, VaultUpdateRequest, VersionResponse, WorkspaceFileEntry, WorkspaceFilesResponse };
+export type { AdminPasswordResetRequest, AdminUserCreateRequest, AdminUserCreateResponse, AdminUsersResponse, AgentCompactionConfigDto, AgentConfigDto, AgentConfigResponse, AgentConfigUpdateRequest, AgentCreateRequest, AgentCreateResponse, AgentImportRequest, AgentImportResponse, AgentKernelUpdateResponse, AgentMemoryConfigDto, AgentModelConfigDto, AgentSchedulesConfigDto, AgentSkillsConfigDto, AgentSkillsResponse, AgentSummary, AgentTraceDateGroup, AgentTraceFileRef, AgentTraceSessionEntry, AgentTraceSessionFile, AgentTraceSessionGroup, AgentTracesResponse, AgentVaultConfigDto, AgentsResponse, ApprovalDecisionRequest, ApprovalMode, AuthLoginRequest, AuthResponse, BenchmarkCaseScore, BenchmarkCaseSummary, BenchmarkCasesResponse, BenchmarkEvaluation, BenchmarkRunScore, BenchmarkSummary, BenchmarksResponse, CaseMaterial, ChatDefaultsDto, CommandPolicyDto, CommandPolicyRuleDto, ContextToolShare, CredentialInfo, DefaultModelResponse, DefaultModelUpdateRequest, DesktopUpdateStatus, DesktopUpdateStatusResponse, DesktopUpdaterCommandMessage, DesktopUpdaterStatusMessage, DirEntryInfo, DirListResponse, DirectorySkillItem, DirectorySkillsResponse, DraftShortcut, EndpointModelListRequest, EndpointModelListResponse, ErrorBody, FeishuBindingInfo, FeishuBindingPutRequest, FeishuBindingResponse, FeishuTestRequest, FeishuTestResponse, FilesStatRequest, FilesStatResponse, GoalResponse, GoalServerEvent, GoalStateView, HistoryMessage, InstallResponse, MachineInfo, MachineInstallJob, MachinesResponse, McpServerTestResponse, MeResponse, MemberAddRequest, MemberAddResponse, MemberInfo, MembersResponse, MemoryFileInfo, MemoryFileResponse, MemoryFilesResponse, MemoryImportMode, MemoryImportRequest, MemoryImportResponse, MemoryOverviewResponse, MemoryScopeExport, MemoryScopeInfo, MemoryTransferFile, MessagesLiveTail, MessagesPageInfo, MessagesResponse, MessagingBindingCommon, MessagingBindingInfo, MessagingBindingStateRequest, MessagingBindingsResponse, MessagingChannel, MessagingChannelState, MessagingDeliveryError, MessagingDeliveryPatch, MessagingRuntimeState, MessagingRuntimeStatus, MessagingTestMessageResponse, ModelInfo, ModelOAuthCodeRequest, ModelOAuthCodeResponse, ModelOAuthErrorCode, ModelOAuthMode, ModelOAuthStartRequest, ModelOAuthStartResponse, ModelOAuthStatusResponse, ModelPricingDto, ModelProtocolDetectRequest, ModelProtocolDetectResponse, ModelProtocolProbeDto, ModelRefDto, ModelTestRequest, ModelTestResponse, ModelUpdateEntry, ModelVisionDetectRequest, ModelVisionDetectResponse, ModelVisionOutcome, ModelsResponse, ModelsUpdateRequest, PasswordChangeRequest, PendingFollowUpInfo, PendingSteeringInfo, PrefsResponse, ProjectCreateRequest, ProjectCreateResponse, ProjectRole, ProjectSummary, ProjectUpdateRequest, ProjectUpdateResponse, ProjectsResponse, ProtocolProbeOutcome, QQBindingInfo, QQBindingPutRequest, QQBindingResponse, QQScanPollResponse, QQScanStartResponse, QQTestRequest, QQTestResponse, RecalledMessageResponse, RequestSpan, RetryNowResponse, ScheduleItem, ScheduleServerEvent, ScheduleStatus, ScheduleUpsertRequest, SchedulesResponse, ServerEvent, ServerSettings, ServerSettingsResponse, ServerSettingsUpdateRequest, SessionCategory, SessionCategoryCounts, SessionContextParts, SessionContextResponse, SessionCreateRequest, SessionCreateResponse, SessionForkRequest, SessionForkResponse, SessionInfo, SessionPatchRequest, SessionProcessInfo, SessionProcessesResponse, SessionResponse, SessionSource, SessionStatus, SessionTracesResponse, SessionsResponse, SkillArchiveInstallRequest, SkillGroupItem, SkillInstallRequest, SkillLibraryResponse, SkillMetadataItem, SkillUpdateRef, SteerRequest, SubagentMessageResponse, SubagentRuntimeInfo, TaskCreateRequest, TaskCreateResponse, TaskInputPart, TelegramBindingInfo, TelegramBindingPutRequest, TelegramBindingResponse, TelegramTestRequest, TelegramTestResponse, ToolCallSpan, TraceAnalysisResponse, TraceEventsResponse, TraceFileInfo, TraceImportRequest, TraceImportResponse, TraceModelSegment, TraceOtherSpan, TracePosition, TraceTaskStats, TraceToolSpan, UiPrefs, UpdateCheckResponse, UpdateRunResponse, UploadLimits, UsageAgentSeries, UsageBucket, UsageEntitySeriesCounts, UsageErrorCount, UsageErrorItem, UsageErrorKind, UsageErrors, UsageErrorsClearResponse, UsageErrorsPage, UsageGranularity, UsageGroupBy, UsageGroupRow, UsageModelSeries, UsageModelTotal, UsageModelTotals, UsageResponse, UsageSeriesPoint, UsageTrendPointInTrace, UserInfo, VaultEntryInfo, VaultEntryUpdate, VaultResponse, VaultUpdateRequest, VersionResponse, WeChatBindingInfo, WeChatBindingPutRequest, WeChatBindingResponse, WeChatScanPollResponse, WeChatScanStartResponse, WeChatScanStatus, WeChatScanVerifyRequest, WeChatTestResponse, WorkspaceFileEntry, WorkspaceFilesResponse };

package/dist/auth-token.js

@@ -2,7 +2,7 @@ import {
   AuthSessionsRepo,
   UsersRepo,
   openExistingDatabase
-} from "./chunk-622KL7BQ.js";
+} from "./chunk-WL5FUO3A.js";
 
 // src/auth-token.ts
 import path from "path";

package/dist/{chunk-UGAFPYVX.js → chunk-OTYHSDV7.js}

@@ -1,6 +1,6 @@
 import {
   sessionTokenHash
-} from "./chunk-622KL7BQ.js";
+} from "./chunk-WL5FUO3A.js";
 
 // src/auth/password.ts
 import { randomBytes, scrypt, timingSafeEqual } from "crypto";
@@ -371,4 +371,4 @@ export {
   toUserInfo,
   AuthService
 };
-//# sourceMappingURL=chunk-UGAFPYVX.js.map
+//# sourceMappingURL=chunk-OTYHSDV7.js.map

package/dist/{chunk-622KL7BQ.js → chunk-WL5FUO3A.js}

@@ -123,13 +123,13 @@ CREATE TABLE IF NOT EXISTS goal_state (        -- goal-mode runtime state (GOAL.
 CREATE INDEX IF NOT EXISTS idx_goal_session ON goal_state(session_id);
 CREATE TABLE IF NOT EXISTS messaging_bindings ( -- Session \u2194 messaging-channel bot bindings (runtime/messaging/ holds the long connections)
   session_id       TEXT NOT NULL,              -- a Session keeps at most one saved config PER channel (composite PK below); at most ONE of them is enabled at a time (route-enforced, 409 another_channel_enabled), and enabling is what binds the account to this Session
-  channel          TEXT NOT NULL,              -- messaging channel discriminator ('feishu' | 'telegram' | 'qq')
-  account_id       TEXT NOT NULL,              -- channel-scoped bot/app identity (feishu: app_id; telegram: the bot token's numeric id; qq: the bot's App ID); NOT unique \u2014 any number of Sessions may keep the same account saved side by side, each with its own config and last-chat memory; only ENABLING is exclusive (route-enforced, 409 account_enabled_elsewhere: one account has one event stream, two live connections on it would race)
-  config_json      TEXT NOT NULL,              -- channel-specific credentials/config JSON (feishu: appId/appSecret/baseDomain; telegram: botToken; qq: appId/appSecret); secrets plaintext at rest (same trade-off as the proxy address in server_settings), masked at every API surface; a cleared secret is stored as "" (the row and its account identity stay)
+  channel          TEXT NOT NULL,              -- messaging channel discriminator ('feishu' | 'telegram' | 'qq' | 'wechat')
+  account_id       TEXT NOT NULL,              -- channel-scoped bot/app identity (feishu: app_id; telegram: the bot token's numeric id; qq: the bot's App ID; wechat: the scanned bot id); NOT unique \u2014 any number of Sessions may keep the same account saved side by side, each with its own config and last-chat memory; only ENABLING is exclusive (route-enforced, 409 account_enabled_elsewhere: one account has one event stream, two live connections on it would race)
+  config_json      TEXT NOT NULL,              -- channel-specific credentials/config JSON (feishu: appId/appSecret/baseDomain; telegram: botToken; qq: appId/appSecret; wechat: botId/botToken/baseUrl/userId); secrets plaintext at rest (same trade-off as the proxy address in server_settings), masked at every API surface; a cleared secret is stored as "" (the row and its account identity stay)
   enabled          INTEGER NOT NULL DEFAULT 0, -- INTENT state (the connection's runtime status stays in memory): new bindings start disabled \u2014 saving credentials never opens a connection, the explicit state toggle does
   line_per_message INTEGER NOT NULL DEFAULT 0, -- delivery preference: 1 = every non-blank line of a relayed assistant reply is sent as its own message (a reply written as spoken lines arrives as spoken lines), 0 = one message per reply. Channel-agnostic, so it lives here rather than in config_json, which each connector owns
   final_reply_only INTEGER NOT NULL DEFAULT 0, -- delivery preference: 1 = a run's intermediate assistant messages are held and only its LAST completed one is sent, at the run's end, 0 = every completed assistant message mirrors the moment it completes. Channel-agnostic like the column above and independent of it: with both set, that one final text is the one split per line
-  render_markdown  INTEGER NOT NULL DEFAULT 1, -- delivery preference: 1 = a relayed reply's Markdown is rendered in the channel's own markup (Telegram HTML, a Feishu card, QQ markdown), 0 = the reply's characters are sent as written. DEFAULT 1 because the model writes Markdown and showing it raw was the defect; the per-channel subsets and the plain-text fallback live in the connectors
+  render_markdown  INTEGER NOT NULL DEFAULT 1, -- delivery preference: 1 = a relayed reply's Markdown is rendered in the channel's own markup (Telegram HTML, a Feishu card, QQ markdown, the subset WeChat itself reads), 0 = the reply's characters are sent as written. DEFAULT 1 because the model writes Markdown and showing it raw was the defect; the per-channel subsets and the plain-text fallback live in the connectors
   last_chat_id     TEXT,                       -- most recent inbound chat (NULL until the bot is messaged once; replies and test messages target it); CONNECTOR-OPAQUE, not necessarily a bare chat id \u2014 telegram appends the forum topic (see telegram-connector.ts chatRefOf), so only that channel's connector may interpret it
   last_chat_is_direct INTEGER NOT NULL DEFAULT 1, -- 1 = direct chat (reply by chat id), 0 = group chat (prefer reply-to-message)
   last_inbound_message_id TEXT,                 -- channel id of the most recently PROCESSED inbound message (NULL until one arrives); the durable half of the bridge's redelivery guard, so a channel replaying an event this server already turned into a Task after a restart does not run it twice
@@ -357,4 +357,4 @@ export {
   sessionTokenHash,
   AuthSessionsRepo
 };
-//# sourceMappingURL=chunk-622KL7BQ.js.map
+//# sourceMappingURL=chunk-WL5FUO3A.js.map