refactor: one owner for shared values, wire types and sync checks

.changeset/contracts-one-owner.md

@@ -0,0 +1,7 @@
+---
+"dsh-mnemon": patch
+"dsh-mnemon-source-memory-spaces": patch
+"dsh-mnemon-source-runtime": patch
+---
+
+Internal cleanups; nothing you see or store changes, and every stored setting validates as before. dsh-mnemon takes the values it shares with Memory Spaces and runtime memory from those components instead of keeping copies (memory categories and sources, edge types, the embedding defaults, the runtime memory limits and the placement capabilities a persistence strategy can require), lists the endpoints its Host serves once for both the Host and the WebUI, and checks the Git sync settings in the WebUI and on the Host with one set of rules. For plugin authors, the Memory Spaces `./contracts` entry now exports `MEMORY_PLACEMENT_CAPABILITIES`, from which `MemoryPlacementCapability` is derived, and the runtime memory `./contracts` entry exports `RUNTIME_MEMORY_LIMIT_MAX_BYTES`, the largest limit its USER.md and MEMORY.md take.

docs/en/reference/interfaces.md

@@ -167,7 +167,7 @@ RPC is an internal Host-to-client bridge, not a stable external HTTP API. Pages
 | `/dsh-mnemon-write` | Every other mutation | Needs `remoteAccess: trusted-host` |
 | `/dsh-mnemon-pack` | Backup export and import | Needs `remoteAccess: trusted-host` |
 | `/dsh-mnemon-sync` | Git repository sync: configuration, push, preview and pull | Needs `remoteAccess: trusted-host` |
-| `/dsh-mnemon-review` | Reconciliation proposals, review opinions and applying an accepted plan | Reads allowed; `reconcile` and `apply` need `remoteAccess: trusted-host` |
+| `/dsh-mnemon-review` | Reconciliation proposals, review opinions and applying an accepted plan | Needs `remoteAccess: trusted-host` |
 | `/dsh-mnemon-settings` | Host and interface settings | `get` allowed; `mutate` needs `remoteAccess: trusted-host` |
 | `/dsh-mnemon-view` | Memory composition reads | Allowed |
 | `/dsh-mnemon-view-settings` | Saving memory composition, installing a component | Needs `remoteAccess: trusted-host` |

docs/pr-assets/README.md

@@ -12,6 +12,7 @@ For new evaluations, commit the reusable harness and workload generator to [`scr
 
 | Record / 记录 | Scope / 范围 |
 |---|---|
+| [One owner for shared values, wire types and sync checks](./contracts-one-owner/README.md) / [中文](./contracts-one-owner/README.zh-CN.md) | The Starter takes Memory Spaces' lists and embedding defaults, the runtime memory limits and the placement capabilities from those components' contracts, three RPC results move into the browser-safe protocol, one typed list names every endpoint the Host serves, and the WebUI and the Host check the Git sync settings by one set of rules; a harness shows the same verdicts and messages as main / Starter 改从记忆空间与运行时记忆的 contracts 取用记忆空间的列表与嵌入默认值、运行时记忆上限与放置能力，三个 RPC 结果移入可在浏览器使用的协议，一份带类型的列表列出 Host 提供的全部端点，WebUI 与 Host 用同一套规则检查 Git 同步设置；验证脚本证明判断与提示信息与 main 相同 |
 | [Client modules split along their seams](./client-module-splits/README.md) / [中文](./client-module-splits/README.zh-CN.md) | The Memory System workbench, the Git sync section and Memory Spaces' pages split into a module per page, section and dialog, and the workbench's status, Source catalog and navigation into three hooks; the built bundles hold the same statements and run the same effects in the same order, and every public entry exports the same names / 记忆系统工作台、Git 同步区块与记忆空间页面拆成每个页面、区块与对话框各自的模块，工作台的状态、Source 目录与导航移入三个 hook；构建产物包含同样的语句、按同样的顺序运行同样的 effect，每个公开入口导出同样的名称 |
 | [The v0.5.32 WebUI gallery, captured on DSH 0.2.1](./webui-gallery-v0532/README.md) / [中文](./webui-gallery-v0532/README.zh-CN.md) | The documentation's screens and recordings captured again with the live model on DSH 0.2.1-rc.2 as webui-v0.5.32, the current documentation pointed at them, and three behaviors found while capturing added to the plan as items 12 to 14 / 在 DSH 0.2.1-rc.2 上由真实模型重新采集文档的截图与录制（webui-v0.5.32），当前文档改用新图集，采集中发现的三个行为作为第 12 至 14 项加入计划 |
 | [Small cleanups](./small-cleanups/README.md) / [中文](./small-cleanups/README.zh-CN.md) | One module for the shipped components and one accessor for the main Strategy id; Memory Spaces exports the Native Provider id and a space's name and description limits, and its code, its client and the Starter's client use them; the retired `toolviews` preference leaves the resolved config; a compatibility register lists each piece of compatibility code and when it can go; nothing users or the model see changes / 随附组件由一个模块列出，主策略 id 通过一个入口读取；记忆空间导出 Native Provider id 与空间名称、描述的上限，记忆空间自身、其客户端与 Starter 的客户端都改用它们；已弃用的 `toolviews` 偏好不再出现在解析后的配置中；兼容登记表列出每项兼容代码及其移除条件；用户和模型看到的内容不变 |