termdock 1.4.309 → 1.4.311

package/README.en.md

@@ -123,7 +123,9 @@ PWA caching lets you reopen the cached interface offline. Terminal input, file a
 
 ## AI and collaboration
 
-Open an Agent in your project terminal, then select **Map → Generate** in the right sidebar. Review the built-in analysis prompt, insert it into the current input or context draft, and send it to the Agent. Choose the entire project, selected directories/modules (multiple relative paths), or a feature flow across directories. Optional controls set dependency depth and analysis requirements; large projects do not need a full overview first. Wide workspaces reuse the Files tree beside the analysis form; expand folders, search and use its reference buttons to add whole folders or files while writing your question. Phones and narrow sidebars use **Choose folders or files** and return to the form after confirmation. You can also use the folder currently open in Files, the current file, or paste file, line and diff references, which become project-relative paths. To analyze one feature within a module, choose **Feature flow**, describe the feature and select its module folder. Boundary mode explains the implementation within those paths; dependency mode follows only necessary outside calls. Write your own question in **Analysis request and constraints**; the generated prompt combines it with the selected scope. The overview uses `.termdock/architecture.json`; scoped maps are saved independently under `.termdock/architectures/`. Switch with **Saved analyses**. **Update** targets only the selected map; **Analyze this module in detail** prepares its source paths directly. The panel checks for saved changes every 10 seconds while visible and offers manual refresh. Analysis uses the current Agent's time and allowance. Maps and source files use the selected service's encrypted transport, including remote projects reached through an entry relay. On phones, module cards open a separate reading panel that preserves list position. Ordinary and fullscreen graphs share a reading flow: wide workspaces show details beside the canvas, while narrow workspaces start with a compact two-line preview and let you expand or collapse details explicitly. Layout follows the available panel space, including narrow desktop sidebars. Source and detailed analysis in the ordinary view open a reading page inside the workspace; returning preserves the map position. Reading panes reserve space for the canvas, preserve zoom, and keep the selected node visible. Follow related modules and step back through them; preview source at its referenced line within the map, then return to the module in one action. Switch perspectives and explore submodules without leaving fullscreen. Diagrams also support drag-to-pan and pinch-to-zoom, with readable labels by default. Long analysis notes, path lists and limitations are kept in collapsible sections.
+Open an Agent in your project terminal, then select **Map → Generate** in the right sidebar. Review the built-in analysis prompt, insert it into the current input or context draft, and send it to the Agent. Choose the entire project, selected directories/modules (multiple relative paths), or a feature flow across directories. Optional controls set dependency depth and analysis requirements; large projects do not need a full overview first. Wide workspaces reuse the Files tree beside the analysis form; expand folders, search and use its reference buttons to add whole folders or files while writing your question. Phones and narrow sidebars use **Choose folders or files** and return to the form after confirmation. You can also use the folder currently open in Files, the current file, or paste file, line and diff references, which become project-relative paths. To analyze one feature within a module, choose **Feature flow**, describe the feature and select its module folder. Boundary mode explains the implementation within those paths; dependency mode follows only necessary outside calls. Write your own question in **Analysis request and constraints**; the generated prompt combines it with the selected scope. The overview uses `.termdock/architecture.json`; scoped maps are saved independently under `.termdock/architectures/`. Switch with **Saved analyses**. **Update** targets only the selected map; **Analyze this module in detail** prepares its source paths directly. Encrypted file watchers refresh saved changes with a 300 ms debounce, backed by ten-second polling for unsubscribed directories and disconnections. Analysis uses the current Agent's time and allowance. Maps and source files use the selected service's encrypted transport, including remote projects reached through an entry relay. On phones, module cards open a separate reading panel that preserves list position. Ordinary and fullscreen graphs share a reading flow: wide workspaces show details beside the canvas, while narrow workspaces start with a compact two-line preview and let you expand or collapse details explicitly. Layout follows the available panel space, including narrow desktop sidebars. Source and detailed analysis in the ordinary view open a reading page inside the workspace; returning preserves the map position. Reading panes reserve space for the canvas, preserve zoom, and keep the selected node visible. Follow related modules and step back through them; preview source at its referenced line within the map, then return to the module in one action. Switch perspectives and explore submodules without leaving fullscreen. Diagrams also support drag-to-pan and pinch-to-zoom, with readable labels by default. Long analysis notes, path lists and limitations are kept in collapsible sections.
+
+The workspace reads oh-my-mermaid `.omm` directories, supports an all-perspective overview, nested levels, cross-perspective references and seven Markdown document fields. Edit node or perspective documents with version history and optimistic conflict protection. History, import and sharing provides changes, JSON / `.omm` bundles and private viewer links bound to the target service. `td architecture --help` exposes native commands and project-local Agent skill setup. Authentication and synchronization use Termdock services and device grants rather than the upstream hosted SaaS. See the [capability comparison and validation boundaries](docs/architecture-parity.md).
 
 ### Use your preferred CLI
 

package/README.md

@@ -174,7 +174,9 @@ docker run -d --name termdock-guacd --network host --restart unless-stopped \
 - STL / GLB / glTF 模型查看与位置引用；KiCad 原理图、PCB 和工程预览。部分转换需要服务机上的额外工具，见[电子设计预览](docs/electronics-preview.md)。
 - Android 投屏与控制，需要服务机上的 adb、scrcpy 及已授权的设备；电脑桌面控制步骤见上文。
 
-在项目终端中打开 Agent，然后进入右侧栏「架构 → 生成」，把内置提示词放入输入区或上下文草稿，检查后发送。生成时可选择整个项目、目录 / 模块（支持多个相对路径），或跨目录的功能链路；可选依赖追踪深度和分析诉求，大项目不必先生成全量总览。宽工作区在分析表单旁复用「文件」页的目录树，可展开目录、搜索并通过引用按钮加入整个目录或文件，边浏览边写问题；手机和窄侧栏通过「选择目录或文件」确认后返回表单。可直接引用「文件」页当前打开的目录或当前文件，或粘贴文件、行号及差异引用，自动转换成项目相对路径。要分析某个模块里的某个功能，选择「功能链路」，填写功能问题并选中该模块目录；范围边界模式只展开范围内的实现，依赖追踪模式再跟随必要的外部调用。可在「分析诉求与限制」中写自己的问题，内置提示词会结合范围和问题生成。项目总览保存在 `.termdock/architecture.json`，局部分析独立保存在 `.termdock/architectures/`，通过「已保存分析」切换。「更新」只处理当前图，其他图保留；选择模块后的「细化分析这个模块」可直接准备其源码范围。面板打开时每 10 秒检查保存结果，并提供手动刷新。分析消耗当前 Agent 的时间和额度。架构文件与源码通过当前目标服务的加密通道读取，支持远端项目和入口中转。 手机默认使用模块说明卡片，详情在独立阅读面板中打开并保留列表位置；普通关系图和全屏图共用阅读动线：宽工作区把说明与画布并排，窄工作区先显示两行简介，按「查看详情」再展开说明，也可收起。布局依据面板可用空间，窄桌面侧栏也使用简介条。普通视图的源码和细化分析在工作区内切换为阅读页面，返回时保留原图位置。说明面板为画布让出空间，保持缩放，并让选中节点留在可见画布内。可沿关联模块查看并逐步返回，源码在当前架构内按行预览，一步返回模块。全屏内可切换视角、展开子模块并返回上一级，也支持拖动平移和双指缩放，默认保持文字可读。长分析说明、路径列表和范围限制放在折叠区。
+在项目终端中打开 Agent，然后进入右侧栏「架构 → 生成」，把内置提示词放入输入区或上下文草稿，检查后发送。生成时可选择整个项目、目录 / 模块（支持多个相对路径），或跨目录的功能链路；可选依赖追踪深度和分析诉求，大项目不必先生成全量总览。宽工作区在分析表单旁复用「文件」页的目录树，可展开目录、搜索并通过引用按钮加入整个目录或文件，边浏览边写问题；手机和窄侧栏通过「选择目录或文件」确认后返回表单。可直接引用「文件」页当前打开的目录或当前文件，或粘贴文件、行号及差异引用，自动转换成项目相对路径。要分析某个模块里的某个功能，选择「功能链路」，填写功能问题并选中该模块目录；范围边界模式只展开范围内的实现，依赖追踪模式再跟随必要的外部调用。可在「分析诉求与限制」中写自己的问题，内置提示词会结合范围和问题生成。项目总览保存在 `.termdock/architecture.json`，局部分析独立保存在 `.termdock/architectures/`，通过「已保存分析」切换。「更新」只处理当前图，其他图保留；选择模块后的「细化分析这个模块」可直接准备其源码范围。面板通过加密文件监听刷新，300 ms 合并变化，并由 10 秒轮询覆盖未订阅目录及断线情况。分析消耗当前 Agent 的时间和额度。架构文件与源码通过当前目标服务的加密通道读取，支持远端项目和入口中转。 手机默认使用模块说明卡片，详情在独立阅读面板中打开并保留列表位置；普通关系图和全屏图共用阅读动线：宽工作区把说明与画布并排，窄工作区先显示两行简介，按「查看详情」再展开说明，也可收起。布局依据面板可用空间，窄桌面侧栏也使用简介条。普通视图的源码和细化分析在工作区内切换为阅读页面，返回时保留原图位置。说明面板为画布让出空间，保持缩放，并让选中节点留在可见画布内。可沿关联模块查看并逐步返回，源码在当前架构内按行预览，一步返回模块。全屏内可切换视角、展开子模块并返回上一级，也支持拖动平移和双指缩放，默认保持文字可读。长分析说明、路径列表和范围限制放在折叠区。
+
+架构工作区兼容 oh-my-mermaid 的 `.omm` 目录，支持全部视角总图、嵌套层级、跨视角引用与七类 Markdown 文档。可直接编辑节点和视角文档，保存时保留版本并检查并发冲突；「历史、导入与分享」提供差异、JSON / `.omm` 文档包互导及绑定目标服务的私有查看链接。`td architecture --help` 提供原生命令及项目内 Agent 技能安装。云端账户和组织沿用 Termdock 自身的服务与设备授权，不连接上游托管 SaaS。详细能力对照与验收边界见 [架构功能对照](docs/architecture-parity.md)。
 
 ### PWA
 

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,30 @@
+# Third-party notices
+
+## oh-my-mermaid
+
+Architecture Mermaid diff utilities and scanner conventions derive from
+https://github.com/oh-my-mermaid/oh-my-mermaid, commit
+38ccdb69298adec949177c92c88d6e3ddfb5bab7. Adaptations use Termdock transport,
+project boundaries, document validation and design tokens.
+
+MIT License
+
+Copyright (c) 2025 oh-my-mermaid
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.