merge: retain published Desktop 0.13.13 history

Merge the published release preparation commit without rewriting either
branch. Keep the approved Desktop 0.13.14 and Agent 0.13.4 versions and
bilingual notes, and restore the historical release documentation.

The merged product source, tests, dependencies, and approved release notes
are identical to d23af99, which passed 5127 tests. Post-merge release-note
checks, nine focused tests, full typecheck, and lint passed.

docs/development/release-preparation-0.13.13.md

@@ -0,0 +1,37 @@
+# Desktop 0.13.13 Preparation
+
+Prepared on 2026-09-23 from `b16fc90`, relative to published Desktop `v0.13.12`.
+This is a Desktop-only release; Agent remains at published `0.13.3`.
+No LoongArch preview is requested.
+
+## Scope and isolation
+
+- `bf8ff7f` reduces repeated activity-history reads during streaming saves.
+- `b16fc90` restores compact supervision feedback controls and target names.
+- The candidate is prepared in a separate worktree. The user's uncommitted
+  supervision timeout tests in the original worktree are explicitly excluded.
+- Desktop and both root lockfile versions are `0.13.13`. Both feature matrices
+  and bilingual release notes were reviewed against this range.
+- Database schema and Agent/Runtime contracts are unchanged. The activity
+  comparison cache belongs to Desktop persistence; it does not modify the
+  deployed Agent, model bridge, or remote Runtime lifecycle.
+
+## Validation
+
+- Six focused files passed 192 tests: activity-history I/O, AssistantDatabase,
+  storage upgrades, sidebar interactions, SupervisionCard, and the Supervisor
+  Electron layout fixture.
+- Re-running `tests/supervisor-layout.electron.test.ts` with
+  `GOODBUDDY_SUPERVISOR_SIDEBAR=1` passed its additional sidebar scenario:
+  480, 300, and 200 pixel widths in both themes, no horizontal overflow,
+  compact 34px buttons, visible keyboard focus, and no raw target ID in body text.
+- `npm run release:notes:verify`, `npm run typecheck`, and `npm run lint` passed.
+- Ten consecutive activity saves performed one full-history scan. WAL and SQL
+  counters are not installed-application physical disk throughput measurements.
+- No real model requests, local full-suite rerun, production build, packaging,
+  or packaged-app probe were performed. UI validation uses production
+  components with isolated fixtures, not a real user database.
+
+The candidate must pass complete main-branch CI and its production build before
+an unused annotated `v0.13.13` tag is pushed to both remotes. Native six-platform
+packaging and public GitHub/OSS verification remain subsequent release steps.

docs/development/release-preparation-0.13.14.md

@@ -16,6 +16,9 @@
 - Fetch 确认两个远端 main 均为 `7756231b3bdfa148f1b2702e4ff3fc3bd0cb057e`。
   用户批准以普通合并保留双方历史，保留本次版本和已批准说明，
   补回历史发布文档；不强推、不改动已有标签。
+- 本地候选提交为 `d23af99`。普通合并解决后，仅新增或修改文档；
+  产品源码、测试、依赖、版本文件及两份已批准说明与该候选完全一致。
+  合并后 `v0.13.13` 恢复为可达发布基线，先前祖先链差异仅记录准备起点状态。
 
 ## 交付与数据边界
 
@@ -39,6 +42,8 @@
 - `npm run typecheck`、`npm run lint`：首轮与联合候选复验均通过。
 - `npm run release:notes:verify`：联合说明写入后通过；Desktop 三处版本一致，
   当前说明仅一项，Agent lock 与独立双语标题一致。
+- 合并后复验：发布说明校验、9 项发布说明测试、完整 typecheck、lint、
+  `git diff --check` 通过。因合并仅恢复文档，未重复运行完整测试和 Host 探针。
 - 当前源码 Linux x64 完成/历史恢复探针通过：两轮 Ask 均完成，Runtime 重建后
   保留会话历史，每轮结束及最终退出时所属进程数均为 0。
 - 隔离旧安装清理探针通过：真实 CLI 回收所属孤儿进程、删除对应旧 payload，