@botharness/core 1.0.2 → 1.1.0

package/CHANGELOG.md

@@ -5,7 +5,42 @@ Notable changes to DeepSeekBot are recorded here. See the
 
 ## [Unreleased]
 
-Nothing yet since 1.0.2.
+Nothing yet since 1.1.0.
+
+## [1.1.0] - 2026-10-06
+
+PersonaBots can run Bot Schedules and manage them themselves, every Session starts with the Bot's Soul and Core Memory, the Channel sidebar sections share one card design, WeChat accepts voice transcripts and images, each Bot's Memory keeps a `.botharness/bot.json` profile for the Bot Marketplace, the plugin sends anonymous usage statistics that can be turned off, and Bot settings can install a DeepSeekBot update and restart DSH with one click.
+
+### Added
+
+- Added a candidate personal WeChat voice source path using platform-provided transcripts and explicit missing-transcript states in the Bot Inbox, without adding ASR or audio playback; a real native voice → model → original-DM reply was confirmed by the Human ([#905](https://github.com/BotHarness/BotHarness/issues/905)).
+- Added a source-preview WeChat image path with automatic image preview inside the original Inbox message bubble, native model image input and own-identity native image replies, with the original-DM image receipt confirmed by the Human ([#904](https://github.com/BotHarness/BotHarness/issues/904), [connection guide](docs/wechat-connection.md)).
+- PersonaBots gain Bot Schedules: the Channel sidebar's Schedules section lets the Human create, edit, pause and delete minute, hourly or daily tasks; each firing lands in the Bot Inbox and wakes the Orchestrator, and every schedule shows its last 20 firings with links to the handling session ([#960](https://github.com/BotHarness/BotHarness/issues/960), [ADR-0133](docs/adr/0133-bot-schedules-wake-the-orchestrator-through-the-bot-inbox.md)).
+- DeepSeekBot now writes `.botharness/bot.json` into each Bot's Memory when the Bot is created, and updates it when its name, roles or avatar change. Existing Bots get the file on the next start. A shared Bot therefore shows the same name, roles and avatar in the Bot Marketplace as in the sidebar ([#966](https://github.com/BotHarness/BotHarness/issues/966), [guide](docs/share-bot.md)).
+- DeepSeekBot sends anonymous usage statistics from the DSH Host, tied only to a random install ID: `plugin_started` (plugin and DSH version, OS, architecture), `bot_created`, `bot_archived`, `bot_deleted`, `marketplace_bot_installed`, `connector_enabled` (connector type only), `avatar_edited`, one `daily_usage` summary (counts of PersonaBots, Sessions and messages, and the window in hours), and unhandled BotHarness errors in the Host as `$exception` reports with the error type and a stack reduced to package-relative file names, never the message or a file path; Bot mode explains this once in a notice linking the privacy page and source. Turn it off with the **Anonymous usage statistics** switch in Bot settings, which applies at once without a restart and is remembered; `telemetry: false` in the core plugin config, `DO_NOT_TRACK=1` or `BOTHARNESS_TELEMETRY=0` force it off and lock the switch ([#951](https://github.com/BotHarness/BotHarness/issues/951), [#952](https://github.com/BotHarness/BotHarness/issues/952), [ADR-0132](docs/adr/0132-anonymous-posthog-telemetry-and-campaign-short-links.md), [guide](docs/settings.md)).
+- PersonaBots can manage their own Bot Schedules: ask a Bot to do something every hour or every day and it creates the schedule itself, marked as Bot-created in the sidebar; it can also change or delete any schedule the Human has not locked. The Human locks a schedule from its row or editor, at most 20 schedules can be enabled per Bot, the sidebar updates as soon as the Bot changes a schedule, and DSH's own `schedule_*` tools are refused in the Orchestrator so a Bot keeps one schedule list ([#961](https://github.com/BotHarness/BotHarness/issues/961)).
+- Bot Schedules can now run weekly on chosen days, once at a date and time (turning themselves off afterwards), or on a five-field cron expression, all in the schedule's own time zone; the editor previews the next three runs, the Bot's schedule tools accept the same cadences, and **Run now** on a row wakes the Orchestrator immediately without moving the next planned run. The new [Schedules guide](docs/channel-sidebar/schedules.md) covers each cadence, Run now, pausing and locking ([#962](https://github.com/BotHarness/BotHarness/issues/962)).
+- Bot settings can install a newer DeepSeekBot release with one click through DSH's Plugin Manager. On the web, **Restart now** then restarts `dsh web` in the same terminal and the page reconnects on its own; DSH Desktop shows how to quit and reopen. When the Plugin Manager is unavailable or the install fails, the reason and the manual update command are shown instead. The new [Update DeepSeekBot](docs/update-deepseekbot.md) guide covers each step ([#986](https://github.com/BotHarness/BotHarness/issues/986)).
+
+### Changed
+
+- The Channel sidebar's Sessions, Bot Inbox and Workspace Grants sections now use the same card rows as Schedules, with an icon, status chips and a meta line on every row; a Bot Inbox item from a Bot Schedule now opens that schedule ([#972](https://github.com/BotHarness/BotHarness/issues/972)).
+- The Channel sidebar's Computer and Browser sections now use the same card rows: a status card shows the target (local or Docker), a state chip such as Running, Needs setup or Paused, and its controls, and the Browser's open tabs are listed as card rows ([#975](https://github.com/BotHarness/BotHarness/issues/975)).
+- The Bot Profile avatar area is now one Avatar section with two side-by-side choices, Design a pixel avatar and Upload an image, and marks the one in use; the duplicate Change avatar button is gone and the divider under the profile header has whitespace around it ([#985](https://github.com/BotHarness/BotHarness/issues/985)).
+- A PersonaBot's persona file is now `SOUL.md`, its Soul, and every Session also starts with its Core Memory, `MEMORY.md`, so a new conversation already knows what the Bot remembers. Both are frozen for the Session with a character usage header (5,000 and 3,000 by default), new Bots get a short `MEMORY.md` template, and an existing `PERSONA.md` is renamed to `SOUL.md` on the next start ([#988](https://github.com/BotHarness/BotHarness/issues/988), [ADR-0134](docs/adr/0134-soul-and-core-memory-are-session-frozen-system-prompt-files.md)).
+- Each Bot's profile has a Standing memory limits section for the `SOUL.md` and `MEMORY.md` character limits, with their approximate size in Chinese characters and English words, applied from the next Session. The Memory panel pins both files at the top with a Standing badge and their current usage, highlighted when over the limit, and Memory search now covers them ([#989](https://github.com/BotHarness/BotHarness/issues/989), [ADR-0134](docs/adr/0134-soul-and-core-memory-are-session-frozen-system-prompt-files.md)).
+
+### Fixed
+
+- Lark user targets with an explicit private chat ID can receive unmentioned private messages into the same PersonaBot Inbox and reply through its bound identity; targets without that locator remain send-only ([#996](https://github.com/BotHarness/BotHarness/issues/996)).
+
+### Documentation
+
+- Documented the development-source Discord file candidate with actual model save/process/import/original-thread result, independent unchanged-input/output byte proof and temporary Workspace write cleanup ([#1002](https://github.com/BotHarness/BotHarness/issues/1002), [verification](docs/dev/verification/discord-1002-source-files.md)).
+- New guide [Bot Soul and Core Memory](docs/soul-and-core-memory.md): why `SOUL.md` and `MEMORY.md` start every Session frozen, what each file is for and why there is no `USER.md`, the character limits with their approximate size and token cost in Chinese and English, how to change them, what an over-limit file looks like, when edits take effect, and how to shape `MEMORY.md` together with the Bot ([#990](https://github.com/BotHarness/BotHarness/issues/990), [ADR-0134](docs/adr/0134-soul-and-core-memory-are-session-frozen-system-prompt-files.md)).
+- The GitHub and npm READMEs cover Bot Schedules, the Bot Marketplace and update notes, add a Release highlights section drawn from this ledger, and replace the screenshots with a high-resolution gallery in which every avatar is a BotPixel pixel avatar ([#984](https://github.com/BotHarness/BotHarness/issues/984)).
+- Documented the isolated Discord nearby context candidate: exact native source container, five-minute window, sparse Human-text minima and bounded continuation; real-model sparse pagination, canonical retention, original-thread reply and temporary permission restoration are verified independently of product promotion ([#981](https://github.com/BotHarness/BotHarness/issues/981), [guide](docs/dev/guides/im-provider-integration.md)).
+- Documented final development-source Discord context acceptance with real model continuation, precise edited-source refusal, whole-page rollback and restored Message Content permissions ([#937](https://github.com/BotHarness/BotHarness/issues/937), [verification](docs/dev/verification/discord-937-context-reads.md)).
 
 ## [1.0.2] - 2026-10-06
 

package/CHANGELOG.zh.md

@@ -5,7 +5,42 @@
 
 ## [Unreleased]
 
-1.0.2 之后暂无变更。
+1.1.0 之后暂无变更。
+
+## [1.1.0] - 2026-10-06
+
+PersonaBot 可设置并自行管理定时任务，每个会话都会带上 Bot 的 Soul 与核心记忆，Channel 侧栏各分区统一为卡片样式，微信支持语音转写和图片；每个 Bot 的 Memory 会保存供 Bot 市场使用的 `.botharness/bot.json`；插件会发送可关闭的匿名使用统计；Bot 设置可一键安装 DeepSeekBot 更新并重启 DSH。
+
+### Added
+
+- 增加个人微信语音来源候选链路，使用平台提供的转写，在 Bot Inbox 区分有转写与缺少转写；不增加 ASR 或音频播放，真实原生语音 → 模型 → 原私聊回复已由 Human 确认（[#905](https://github.com/BotHarness/BotHarness/issues/905)）。
+- 增加源码预览微信图片链路，支持 Inbox 原消息气泡内自动加载的 checked 图片预览、原生模型图片输入与本身份原生图片回复，Human 已确认原私聊收到内容一致的图片（[#904](https://github.com/BotHarness/BotHarness/issues/904)，[连接指南](docs/wechat-connection.md)）。
+- PersonaBot 新增定时任务（Bot Schedule）：Channel 侧栏的「定时任务」分区可新建、编辑、暂停和删除按分钟、按小时或每天执行的任务；每次触发进入 Bot 收件箱并唤醒 Orchestrator，每个任务可查看最近 20 次触发及处理它的会话（[#960](https://github.com/BotHarness/BotHarness/issues/960)，[ADR-0133](docs/adr/0133-bot-schedules-wake-the-orchestrator-through-the-bot-inbox.md)）。
+- DeepSeekBot 现在会在创建 Bot 时，自动在它的 Memory 里写入 `.botharness/bot.json`，之后改名称、岗位或头像时同步更新；已有的 Bot 会在下次启动时补上。分享出去的 Bot 在 Bot 市场里显示的名称、岗位和头像，和侧栏里一致（[#966](https://github.com/BotHarness/BotHarness/issues/966)、[教程](docs/share-bot.md)）。
+- DeepSeekBot 由 DSH 后台发送匿名使用统计，只关联一个随机安装 ID：`plugin_started`（插件和 DSH 版本、操作系统、架构），`bot_created`、`bot_archived`、`bot_deleted`、`marketplace_bot_installed`、`connector_enabled`（只含连接器类型）、`avatar_edited`，每天一次的 `daily_usage` 汇总（PersonaBot、会话和消息数量及统计时长），以及 BotHarness 后台未处理错误的 `$exception` 报告（错误类型和只保留包内文件名的调用栈，从不含错误信息或文件路径）；Bot 模式会弹出一次说明，并链接隐私说明和源码。可在 Bot 设置中关掉「匿名使用统计」开关，立即生效、无需重启，并会被记住；在 core 插件配置中设置 `telemetry: false`，或设置 `DO_NOT_TRACK=1`、`BOTHARNESS_TELEMETRY=0`，会强制关闭并锁定该开关（[#951](https://github.com/BotHarness/BotHarness/issues/951)，[#952](https://github.com/BotHarness/BotHarness/issues/952)，[ADR-0132](docs/adr/0132-anonymous-posthog-telemetry-and-campaign-short-links.md)，[教程](docs/settings.md)）。
+- PersonaBot 可以自己管理定时任务：让 Bot「每小时检查一下 X」或「每天早上总结」，它会自己创建定时任务，侧栏里标为 Bot 创建；它也可以修改或删除你没有锁定的任务。你可以在任务行或编辑弹窗里锁定任务；每个 Bot 最多同时启用 20 个；Bot 改动后侧栏立即刷新；Orchestrator 中 DSH 自带的 `schedule_*` 工具会被拒绝，确保每个 Bot 只有一套定时任务（[#961](https://github.com/BotHarness/BotHarness/issues/961)）。
+- 定时任务新增每周（选择星期几）、单次（指定日期和时间，触发后自动停用）和 5 段 Cron 三种频率，均按任务自己的时区计算；编辑弹窗会预览接下来三次触发时间，Bot 的定时任务工具也支持这些频率；任务行上的「立即运行」会马上唤醒 Orchestrator，且不改变下一次计划时间。新增[定时任务使用指南](docs/channel-sidebar/schedules.md)，说明各种频率、立即运行、暂停与锁定（[#962](https://github.com/BotHarness/BotHarness/issues/962)）。
+- Bot 设置可以通过 DSH 的插件管理一键安装新版本 DeepSeekBot。Web 版装完点「立即重启」，`dsh web` 会在同一个终端里重启，页面自动重新连接；DSH Desktop 会提示退出后重新打开。插件管理不可用或安装失败时，会显示原因和手动更新命令。新增[更新 DeepSeekBot](docs/update-deepseekbot.md)教程，说明每一步（[#986](https://github.com/BotHarness/BotHarness/issues/986)）。
+
+### Changed
+
+- Channel 侧栏的会话、Bot 收件箱和工作区授权改用与定时任务相同的卡片行：每行带图标、状态 chip 和说明行；来自定时任务的收件箱条目现在可以点开对应的定时任务（[#972](https://github.com/BotHarness/BotHarness/issues/972)）。
+- Channel 侧栏的电脑和浏览器分区也改用相同的卡片行：状态卡片显示目标（本机或 Docker）、运行中、需要设置、已暂停等状态 chip 和对应操作，浏览器打开的标签页也以卡片行列出（[#975](https://github.com/BotHarness/BotHarness/issues/975)）。
+- Bot Profile 的头像区合并为一个「头像」分区，并排提供「设计像素头像」和「上传图片」两种方式，并标出正在使用的那种；去掉了重复的「更换头像」按钮，顶部分隔线上下留出空白（[#985](https://github.com/BotHarness/BotHarness/issues/985)）。
+- PersonaBot 的人格文件改名为 `SOUL.md`（Soul），每个 Session 开始时还会带上 Core Memory `MEMORY.md`，新对话一开始就知道 Bot 记得什么。两者在整个 Session 内冻结，并带字符用量标注（默认上限 5,000 和 3,000 字符）；新建的 Bot 会附带一份简短的 `MEMORY.md` 模板，已有的 `PERSONA.md` 会在下次启动时改名为 `SOUL.md`（[#988](https://github.com/BotHarness/BotHarness/issues/988)，[ADR-0134](docs/adr/0134-soul-and-core-memory-are-session-frozen-system-prompt-files.md)）。
+- 每个 Bot 的资料页新增「常驻记忆上限」，可分别设置 `SOUL.md` 和 `MEMORY.md` 的字符上限，并显示约合多少汉字和英文单词，从下一个 Session 开始生效。Memory 面板把这两个文件置顶，带「常驻」标记和当前用量，超限时标红；Memory 搜索现在也能搜到它们（[#989](https://github.com/BotHarness/BotHarness/issues/989)，[ADR-0134](docs/adr/0134-soul-and-core-memory-are-session-frozen-system-prompt-files.md)）。
+
+### Fixed
+
+- 带明确私聊 Chat ID 的 Lark 用户目标可以将未 @ 的私聊消息送进同一个 PersonaBot Inbox，并以绑定身份回复；未提供该标识的目标仍只支持发送（[#996](https://github.com/BotHarness/BotHarness/issues/996)）。
+
+### Documentation
+
+- 记录开发来源 Discord 文件候选的真实模型保存／处理／导入／原 thread 结果、独立原件不变／输出字节证据及临时工作区写权限清理（[#1002](https://github.com/BotHarness/BotHarness/issues/1002)，[verification](docs/dev/verification/discord-1002-source-files.md)）。
+- 新增教程 [Bot 灵魂与核心记忆](docs/soul-and-core-memory.md)：说明 `SOUL.md` 与 `MEMORY.md` 为什么在每个 Session 开始时冻结注入、两个文件分别代表什么、为什么没有 `USER.md`、字符上限及中英文的大致篇幅和 token 量、如何修改上限、超限时的样子、修改何时生效，以及如何和 Bot 一起塑造 `MEMORY.md`（[#990](https://github.com/BotHarness/BotHarness/issues/990)，[ADR-0134](docs/adr/0134-soul-and-core-memory-are-session-frozen-system-prompt-files.md)）。
+- GitHub 与 npm 的 README 补充定时任务、Bot 市场和更新提示，新增依据本 Ledger 整理的「版本亮点」，并换成高清截图表格，所有头像均为 BotPixel 像素头像（[#984](https://github.com/BotHarness/BotHarness/issues/984)）。
+- 记录隔离 Discord nearby 上下文候选的准确原生来源范围、五分钟窗口、稀疏 Human 文本最小条数与有界续页；真实模型稀疏续页、canonical 留存、原 thread 回复和临时权限恢复已独立验证，产品提升仍另行管理（[#981](https://github.com/BotHarness/BotHarness/issues/981)，[指南](docs/dev/guides/im-provider-integration.md)）。
+- 补全 Discord 上下文开发来源验收文档，提供真实模型续页、准确的已编辑来源拒绝、整页回滚及消息正文权限恢复证据（[#937](https://github.com/BotHarness/BotHarness/issues/937)，[verification](docs/dev/verification/discord-937-context-reads.md)）。
 
 ## [1.0.2] - 2026-10-06
 

package/dist/index.d.mts

@@ -1,8 +1,8 @@
 import { DatabaseSync } from "node:sqlite";
 import { ToolCallKind, ToolCallView, ToolExecution } from "@deepseek-ai/dsh-tools";
 import { BlockAssembler, ContextFormed, ToolCallId } from "@deepseek-ai/dsh-llm";
-import { Agent, AgentHandle, AssistantStreamFrame, CreateAgentOptions, ModelSelection, ResumeAgentOptions } from "@deepseek-ai/dsh-agent";
 import { Session, SessionId } from "@deepseek-ai/dsh-session";
+import { Agent, AgentHandle, AssistantStreamFrame, CreateAgentOptions, ModelSelection, ResumeAgentOptions } from "@deepseek-ai/dsh-agent";
 //#region node_modules/.pnpm/@deepseek-ai+cosmokit@1.8.5/node_modules/@deepseek-ai/cosmokit/lib/types/types.d.ts
 declare function isArrayBufferLike(value: any): value is ArrayBufferLike;
 declare function isArrayBufferSource(value: any): value is Binary.Source;
@@ -8021,6 +8021,11 @@ interface MessagingAttachment {
   sizeBytes?: number;
   mediaType?: string;
 }
+interface MessagingVoice {
+  transcript: 'platform' | 'unavailable';
+  itemId?: string;
+  durationMs?: number;
+}
 interface MessagingInboundEvent {
   version: 1;
   channel: 'feishu' | 'slack' | 'discord' | 'weixin';
@@ -8046,6 +8051,7 @@ interface MessagingInboundEvent {
   at: string;
   text: string;
   attachments?: MessagingAttachment[];
+  voice?: MessagingVoice;
   reply: MessagingReplyRoute;
   replay: {
     kind: 'provider-redelivery';
@@ -8157,6 +8163,7 @@ interface MessagingProvider {
       id: string;
       name: string;
       bytes: Uint8Array;
+      mediaType?: string;
     };
     signal: AbortSignal;
     beforeSend?: () => boolean;
@@ -8297,6 +8304,16 @@ interface InboundMessaging {
   close(): void;
 }
 //#endregion
+//#region packages/core/src/telemetry/service.d.ts
+type TelemetryValue = string | number | boolean;
+type TelemetryCapture = (event: string, properties?: Record<string, TelemetryValue>) => void;
+type TelemetryLock = 'config' | 'DO_NOT_TRACK' | 'BOTHARNESS_TELEMETRY';
+interface TelemetryStatus {
+  enabled: boolean;
+  preference: boolean;
+  lockedBy?: TelemetryLock;
+}
+//#endregion
 //#region packages/core/src/messaging/outbound.d.ts
 interface MessagingGrant {
   id: string;
@@ -8432,8 +8449,21 @@ export declare function createOutboundMessaging(options: {
   recover?: boolean;
   now?: () => Date;
   warn?: (message: string) => void;
+  capture?: TelemetryCapture;
 }): OutboundMessaging;
 //#endregion
+//#region packages/core/src/memory/soul.d.ts
+interface StandingLimits {
+  soul: number;
+  coreMemory: number;
+}
+interface StandingUsage {
+  path: string;
+  role: 'soul' | 'coreMemory';
+  chars: number;
+  limit: number;
+}
+//#endregion
 //#region packages/core/src/models/presets.d.ts
 interface ModelRoute {
   provider: string;
@@ -8698,6 +8728,7 @@ interface PersonaBotRecord {
   computerAccess?: boolean;
   browserAccess?: boolean;
   browserProfile?: string;
+  standingLimits?: StandingLimits;
 }
 interface CreatePersonaBotInput {
   slug: string;
@@ -8886,6 +8917,10 @@ interface PersonaBotRegistryOptions {
   initializeMemory?: (memoryDir: string) => MemoryRepositoryInitialization;
   cloneMemory?: (destination: string, url: string) => Promise<MemoryCloneResult>;
   onPurge?: (slug: string, removeFiles: () => void) => void;
+  capture?: TelemetryCapture;
+  syncDescriptor?: (memoryDir: string, record: PersonaBotRecord, options: {
+    onlyIfMissing: boolean;
+  }) => void;
 }
 interface PersonaBotRegistry {
   rootDir: string;
@@ -8904,6 +8939,7 @@ interface PersonaBotRegistry {
   setComputerAccess(slug: string, enabled: boolean): UpdatePersonaBotResult;
   setBrowserAccess(slug: string, enabled: boolean): UpdatePersonaBotResult;
   setBrowserProfile(slug: string, profile: string): UpdatePersonaBotResult;
+  setStandingLimits(slug: string, limits: StandingLimits): UpdatePersonaBotResult;
   applyModelPreset(slug: string, preset: ModelPreset): UpdatePersonaBotResult;
   migrateLegacyModel(slug: string, expectedModel: string, route: ModelRoute): UpdatePersonaBotResult;
   customizeModelPlan(slug: string, orchestrator: PersonaBotModelPlan['orchestrator'], expectedRevision: number): UpdatePersonaBotResult;
@@ -8995,6 +9031,7 @@ interface MemoryAcceptedSnapshot {
   head: string | null;
   files: string[];
   provisional: boolean;
+  standing: StandingUsage[];
 }
 interface MemoryChangeDelta {
   summary: string;
@@ -9193,7 +9230,7 @@ interface MemoryStore {
   read(path: string): MemoryEntry | undefined;
   write(input: MemoryWriteInput): Promise<MemoryWriteResult>;
   search(query: string): Promise<MemorySearchHit[]>;
-  persona(): string | undefined;
+  standingPrompt(limits?: StandingLimits): string;
   history(limit?: number): MemoryCommit[];
 }
 export declare function createMemoryStore(options: MemoryStoreOptions): MemoryStore;
@@ -9260,6 +9297,81 @@ interface AssignmentReportPage {
   estimatedTokens: number;
 }
 //#endregion
+//#region packages/core/src/schedules/bot-schedules.d.ts
+type BotScheduleTrigger = {
+  kind: 'every';
+  everySeconds: number;
+} | {
+  kind: 'daily';
+  time: string;
+  timeZone: string;
+} | {
+  kind: 'weekly';
+  time: string;
+  timeZone: string;
+  weekdays: number[];
+} | {
+  kind: 'once';
+  date: string;
+  time: string;
+  timeZone: string;
+} | {
+  kind: 'cron';
+  expression: string;
+  timeZone: string;
+};
+type BotScheduleCreator = 'human' | 'personabot';
+type BotScheduleFiringState = 'pending' | 'observed' | 'handled' | 'coalesced' | 'skipped';
+interface BotScheduleFiring {
+  id: string;
+  scheduleId: string;
+  trigger: 'planned' | 'manual';
+  occurrenceAt: string;
+  firedAt: string;
+  state: BotScheduleFiringState;
+  sourceEventId?: string;
+  sessionId?: string;
+}
+interface BotSchedule {
+  id: string;
+  botSlug: string;
+  title: string;
+  prompt: string;
+  trigger: BotScheduleTrigger;
+  enabled: boolean;
+  creator: BotScheduleCreator;
+  locked: boolean;
+  nextRunAt?: string;
+  lastFiring?: BotScheduleFiring;
+  createdAt: string;
+  updatedAt: string;
+}
+interface BotScheduleInput {
+  title: string;
+  prompt: string;
+  trigger: BotScheduleTrigger;
+  enabled?: boolean;
+  locked?: boolean;
+}
+interface BotScheduleChange {
+  title?: string;
+  prompt?: string;
+  trigger?: BotScheduleTrigger;
+  enabled?: boolean;
+  locked?: boolean;
+}
+interface BotScheduleStore {
+  list(botSlug: string): BotSchedule[];
+  create(botSlug: string, input: BotScheduleInput, creator: BotScheduleCreator): BotSchedule;
+  update(botSlug: string, id: string, change: BotScheduleChange, actor: BotScheduleCreator): BotSchedule;
+  remove(botSlug: string, id: string, actor: BotScheduleCreator): boolean;
+  history(botSlug: string, id: string): BotScheduleFiring[];
+  runNow(botSlug: string, id: string): BotScheduleFiring;
+  tick(): void;
+  start(): void;
+  close(): void;
+}
+//#endregion
 //#region packages/core/src/runtime/bot-runtime.d.ts
 type AssignmentActivity = 'working' | 'idle' | 'error' | 'stopping' | 'stopped';
 type AssignmentReportState = 'progress' | 'completed' | 'blocked' | 'waiting-human' | 'failed';
@@ -9408,6 +9520,12 @@ interface OrchestratorAgentRun {
     resetImmediateDelivery(sourceClass: 'human-dm' | 'bot-dm' | 'group-mention'): BotSourcePolicy;
   };
   assignments: OrchestratorAssignmentAccess;
+  schedules?: {
+    list(): BotSchedule[];
+    create(input: BotScheduleInput): BotSchedule;
+    update(id: string, change: BotScheduleChange): BotSchedule;
+    remove(id: string): boolean;
+  };
   memory?: {
     switchBranch(branch: string): {
       from: string;
@@ -9645,6 +9763,7 @@ interface BotRuntime {
   listAssignments(botSlug: string): AssignmentSummary[];
   getAssignment(botSlug: string, sessionId: string): AssignmentDetail | undefined;
   admitExternalSource?(botSlug: string, sourceEventId: string): void;
+  admitScheduleFiring?(botSlug: string): void;
   resumePendingDigests?(botSlug: string): void;
   whenIdle(): Promise<void>;
   close(): Promise<void>;
@@ -9654,6 +9773,7 @@ interface BotRuntimeOptions {
   externalMessaging?: OutboundMessaging;
   database: OperationalDatabaseOwner;
   sourcePolicy?: BotSourcePolicyStore;
+  schedules?: Pick<BotScheduleStore, 'list' | 'create' | 'update' | 'remove'>;
   registry: PersonaBotRegistry;
   channels: ChannelStore;
   agents: BotAgentAdapter;
@@ -10440,6 +10560,7 @@ interface BotAttentionItem {
   assignmentReportState?: 'progress' | 'completed' | 'blocked' | 'waiting-human' | 'failed';
   assignmentTurn?: number;
   relatedReportSourceEventId?: string;
+  scheduleId?: string;
   sourceAvailable: boolean;
   authorKind: 'human' | 'bot' | 'bridged' | 'system';
   authorBotSlug?: string;
@@ -10450,6 +10571,7 @@ interface BotAttentionItem {
     conversationId: string;
     senderId: string;
     senderName?: string;
+    voice?: NonNullable<ExternalSource['event']['voice']>;
   };
   summary: string;
 }
@@ -10690,6 +10812,7 @@ interface BotHarnessConfig {
   agentPreset?: string;
   activityDetailConsumers?: string[];
   marketplaceUrl?: string;
+  telemetry?: boolean;
 }
 export declare const DEFAULT_CONFIG: BotHarnessConfig;
 declare const Config$1: Schema<Schemastery.ObjectS<NoInfer<{
@@ -10697,11 +10820,13 @@ declare const Config$1: Schema<Schemastery.ObjectS<NoInfer<{
   activityDetailConsumers: Schema<string[], string[], "defined">;
   agentPreset: Schema<string, string, "defined">;
   marketplaceUrl: Schema<string, string, "defined">;
+  telemetry: Schema<boolean, boolean, "defined">;
 }>>, Schemastery.ObjectT<NoInfer<{
   enabled: Schema<boolean, boolean, "defined">;
   activityDetailConsumers: Schema<string[], string[], "defined">;
   agentPreset: Schema<string, string, "defined">;
   marketplaceUrl: Schema<string, string, "defined">;
+  telemetry: Schema<boolean, boolean, "defined">;
 }>>, "plain">;
 interface BotHarnessCore {
   rootDir: string;
@@ -10724,6 +10849,7 @@ interface BotHarnessCore {
   runtime: BotRuntime;
   attention: BotAttentionQuery;
   sourcePolicy: BotSourcePolicyStore;
+  schedules: BotScheduleStore;
   humanAttention: HumanAttentionQuery;
   humanAttentionDecisions: HumanAttentionDecisions;
   grants: WorkspaceGrantStore;
@@ -10751,6 +10877,7 @@ export declare function createCore(options?: {
   onOutputCommitted?: (event: PersonaBotOutputCommitted) => void;
   activeQuestionMessageIds?: () => readonly string[];
   activeToolApprovalMessageIds?: () => readonly string[];
+  capture?: TelemetryCapture;
 }): BotHarnessCore;
 export declare function apply(ctx: Context, config: BotHarnessConfig): void;
 declare module '@deepseek-ai/cordis' {
@@ -10868,10 +10995,36 @@ type ReleaseUpdate = {
   current: string;
   latest: string;
   releases: ReleaseNote[];
+  installable: boolean;
+} | {
+  status: 'restart-required';
+  current: string;
+  installed: string;
+  restartable: boolean;
+};
+type ReleaseInstallFailure = 'unavailable' | 'invalid-version' | 'network' | 'incompatible' | 'build-blocked' | 'failed';
+type ReleaseInstall = {
+  status: 'installed';
+  current: string;
+  installed: string;
+  restartable: boolean;
+} | {
+  status: 'failed';
+  reason: ReleaseInstallFailure;
+  diagnostic?: string;
+  logPath?: string;
+};
+type ReleaseRestart = {
+  status: 'restarting';
+} | {
+  status: 'failed';
+  reason: 'unavailable' | 'not-pending';
 };
 interface ReleaseService {
   info(since?: string): ReleaseInfo;
   update(): Promise<ReleaseUpdate>;
+  install(version: string): Promise<ReleaseInstall>;
+  restart(): Promise<ReleaseRestart>;
 }
 //#endregion
 //#region packages/core/src/channels/profile-activity.d.ts
@@ -10979,6 +11132,7 @@ interface PersonaBotSummary {
   avatar?: string;
   appearance?: AvatarAppearance | RetainedAvatarAppearance;
   paused?: boolean;
+  standingLimits: StandingLimits;
   aggregateState: AggregatedState;
   workspaces: string[];
   createdAt: string;
@@ -11389,6 +11543,9 @@ interface BridgeMethods {
   browserProfileSet(payload: unknown): BridgeResult<{
     bot: PersonaBotDetail;
   }>;
+  standingLimitsSet(payload: unknown): BridgeResult<{
+    bot: PersonaBotDetail;
+  }>;
   botAvatarSet(payload: unknown): BridgeResult<{
     bot: PersonaBotDetail;
   }>;
@@ -11407,6 +11564,31 @@ interface BridgeMethods {
   }>>;
   releaseInfo(payload: unknown): BridgeResult<ReleaseInfo>;
   releaseUpdate(): Promise<BridgeResult<ReleaseUpdate>>;
+  releaseInstall(payload: unknown): Promise<BridgeResult<ReleaseInstall>>;
+  releaseRestart(payload: unknown): Promise<BridgeResult<ReleaseRestart>>;
+  telemetryStatus(): BridgeResult<TelemetryStatus>;
+  telemetrySet(payload: unknown): BridgeResult<TelemetryStatus>;
+  scheduleList(payload: unknown): BridgeResult<{
+    schedules: BotSchedule[];
+  }>;
+  scheduleCreate(payload: unknown): BridgeResult<{
+    schedule: BotSchedule;
+  }>;
+  scheduleUpdate(payload: unknown): BridgeResult<{
+    schedule: BotSchedule;
+  }>;
+  scheduleDelete(payload: unknown): BridgeResult<{
+    removed: boolean;
+  }>;
+  scheduleHistory(payload: unknown): BridgeResult<{
+    firings: BotScheduleFiring[];
+  }>;
+  scheduleRunNow(payload: unknown): BridgeResult<{
+    firing: BotScheduleFiring;
+  }>;
+  schedulePreview(payload: unknown): BridgeResult<{
+    occurrences: string[];
+  }>;
 }
 interface BridgeMethodsDeps {
   warn?: (message: string) => void;
@@ -11425,6 +11607,7 @@ interface BridgeMethodsDeps {
   runtime?: BotRuntime;
   attention?: BotAttentionQuery;
   sourcePolicy?: BotSourcePolicyStore;
+  schedules?: BotScheduleStore;
   humanAttention?: HumanAttentionQuery;
   humanAttentionDecisions?: HumanAttentionDecisions;
   grants?: WorkspaceGrantStore;
@@ -11448,6 +11631,11 @@ interface BridgeMethodsDeps {
   createBotId?: () => string;
   marketplace?: MarketplaceClient;
   release?: ReleaseService;
+  telemetry?: {
+    status(): TelemetryStatus;
+    setPreference(enabled: boolean): TelemetryStatus;
+    capture?: TelemetryCapture;
+  };
 }
 export declare function createBridgeMethods(deps: BridgeMethodsDeps): BridgeMethods;
 //#endregion
@@ -11566,6 +11754,9 @@ export declare class BotharnessBridgeService extends TypertRemoteService {
   browserProfileSet(slug: string, profile: string): {
     bot: PersonaBotDetail;
   };
+  standingLimitsSet(slug: string, soul: number, coreMemory: number): {
+    bot: PersonaBotDetail;
+  };
   botAvatarSet(channelId: string, avatar: string | null): {
     bot: PersonaBotDetail;
   };
@@ -11815,6 +12006,31 @@ export declare class BotharnessBridgeService extends TypertRemoteService {
   marketplaceDetail(id: string): Promise<MarketplaceDetail>;
   releaseInfo(since?: string): Promise<ReleaseInfo>;
   releaseUpdate(): Promise<ReleaseUpdate>;
+  releaseInstall(version: string): Promise<ReleaseInstall>;
+  releaseRestart(): Promise<ReleaseRestart>;
+  telemetryStatus(): TelemetryStatus;
+  telemetrySet(enabled: boolean): TelemetryStatus;
+  scheduleList(slug: string): {
+    schedules: BotSchedule[];
+  };
+  scheduleCreate(slug: string, input: BotScheduleInput): {
+    schedule: BotSchedule;
+  };
+  scheduleUpdate(slug: string, id: string, change: BotScheduleChange): {
+    schedule: BotSchedule;
+  };
+  scheduleDelete(slug: string, id: string): {
+    removed: boolean;
+  };
+  scheduleHistory(slug: string, id: string): {
+    firings: BotScheduleFiring[];
+  };
+  scheduleRunNow(slug: string, id: string): {
+    firing: BotScheduleFiring;
+  };
+  schedulePreview(trigger: BotScheduleTrigger): {
+    occurrences: string[];
+  };
 }
 export declare function registerBridge(ctx: Context, methods: BridgeMethods): BotharnessBridgeService;
 //#endregion
@@ -11990,6 +12206,7 @@ interface DshImOutboundService {
     id: string;
     name: string;
     bytes: Uint8Array;
+    mediaType?: string;
   }, options: {
     expectedFingerprint: string;
     signal: AbortSignal;
@@ -12017,6 +12234,8 @@ interface DshImOutboundService {
     expectedFingerprint: string;
     signal: AbortSignal;
     sourceFiles?: boolean;
+    sourceImages?: boolean;
+    sourceVoiceTranscripts?: boolean;
     ordinaryText?: boolean;
     onEcho?(event: unknown, context: {
       signal: AbortSignal;