Files
dsh_shenxian/dsh-server-docs/docs-manifest.json
T
admin 4e3a1a4a13 docs(overlay): 覆盖网络/客户端化 10 份规划转正式档案 103-112 + 登记
- 新增 04-调整方案/103-112:可行性评估 · 全球架构复盘 · 骨干层方案 ·
  百台推演 v2 · 千台全场景推演 · 游戏专项 · 游戏网络与群聊上限调研 ·
  答疑(群聊/备份/迁移/保密) · 补遗与参考方案 · 九大瓶颈落地方案
- 每份按 交接单/README.md §二 8 段改写(目标/只读前置/范围/决策点/
  步骤/验收/回滚/回报格式)+ 头部状态标注(📋 规划态 · 未实施)
- 技术内容不变:附录 A 逐字保留原文全文(仅去其一级标题),已逐份校验字节一致
- 登记:INDEX.md §二 +10 行、03-路线图与待办.md §二 +1 行
- 收尾:docs-audit.py 退出码 0(无 P0)· docs-manifest.py 已刷新
- 本轮零代码、零服务器改动;⛔ 未 push
- 占号:103-112(先原子 mkdir .lock-<NN> 再写)
2026-09-16 10:25:09 +08:00

2255 lines
67 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"generatedFrom": "scripts/docs-manifest.py",
"counts": {
"files": 148,
"chars": 1222542
},
"tiers": {
"hot": 7,
"cur": 27,
"warm": 57,
"cold": 21,
"doc": 36
},
"domains": {
"platform": 60,
"method": 29,
"ui": 14,
"plugin": 27,
"ops": 11,
"?": 2,
"external": 5
},
"layers": {
"L0": 1,
"L5": 125,
"L4": 4,
"L2": 3,
"?": 1,
"L1": 2,
"L3": 12
},
"items": [
{
"path": "01-规划与架构.md",
"num": null,
"title": "dsh(DeepSeek Harness)多用户部署与配置改造方案",
"status": "?",
"date": "",
"chars": 9813,
"lines": 239,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L0",
"domain": "platform",
"tldr": ""
},
{
"path": "02-运维手册.md",
"num": null,
"title": "六、单实例迁移执行步骤(从当前 data/ 形态 → users/main 形态)",
"status": "?",
"date": "",
"chars": 14364,
"lines": 336,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "03-路线图与待办.md",
"num": null,
"title": "03 路线图与待办",
"status": "?",
"date": "",
"chars": 18981,
"lines": 128,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L4",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/01-launch-token自动携带.md",
"num": "01",
"title": "十六、方案 A 落地:launch/status 自动携带 dsh launch token(2026-09-08 19:30)",
"status": "✅",
"date": "04-01",
"chars": 1262,
"lines": 26,
"refs": 2,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "04-调整方案/02-安全加固-权限边界与DB.md",
"num": "02",
"title": "十七、权限边界实测 + DB 权限安全加固(2026-09-08)",
"status": "✅",
"date": "04-02",
"chars": 1922,
"lines": 38,
"refs": 2,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "ui",
"tldr": ""
},
{
"path": "04-调整方案/03-统一KEY管理员管控.md",
"num": "03",
"title": "十八、统一 KEY:管理员统一设置,用户只能使用管理员 KEY 和模型(2026-09-08 20:40)",
"status": "✅",
"date": "04-03",
"chars": 1315,
"lines": 24,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ui",
"tldr": ""
},
{
"path": "04-调整方案/04-删除用户功能.md",
"num": "04",
"title": "十九、界面删除用户功能(2026-09-09 07:00)",
"status": "✅",
"date": "04-04",
"chars": 1144,
"lines": 19,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "ui",
"tldr": ""
},
{
"path": "04-调整方案/05-登录直达会话与功能插件化-可行性.md",
"num": "05",
"title": "调整方案 05:登录直达会话窗口 + 桌面功能插件化(可行性调研 + PoC)",
"status": "PoC 实证完成(插件 v0",
"date": "04-05",
"chars": 14061,
"lines": 177,
"refs": 16,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:登录直达 + 桌面功能插件化的可行性调研与 PoC:**0.1.2-rc.1 的官方 profile 插件机制可用且完整闭环**(安装/装载/持久/升级/删除全验证),红线零违反。"
},
{
"path": "04-调整方案/06-登录直达会话窗口.md",
"num": "06",
"title": "调整方案 06:登录直达 DSH 会话窗口(v1 + v2 已上线)",
"status": "已上线",
"date": "",
"chars": 1548,
"lines": 31,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "04-调整方案/07-红线-禁止dsh自动获取最新版本.md",
"num": "07",
"title": "调整方案 07:红线 — 禁止 dsh 自动获取最新版本 + 版本升级流程",
"status": "生效",
"date": "",
"chars": 2111,
"lines": 44,
"refs": 10,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/08-实例常驻上限与单活跃会话.md",
"num": "08",
"title": "08-实例常驻上限与单活跃会话(idle-reap + last-wins,2026-09-09 落地)",
"status": "✅",
"date": "04-08",
"chars": 3941,
"lines": 99,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/09-普通用户隐藏模型设置-角色化profile-patch.md",
"num": "09",
"title": "09-普通用户隐藏「模型」设置分区(角色化 profile patch)",
"status": "已落地",
"date": "04-09",
"chars": 3287,
"lines": 74,
"refs": 7,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ui",
"tldr": ""
},
{
"path": "04-调整方案/10-共享技能只读部署-bundledSkillDir.md",
"num": "10",
"title": "10-共享技能只读部署(bundledSkillDir 层)",
"status": "已实施",
"date": "04-10",
"chars": 6261,
"lines": 129,
"refs": 48,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "method",
"tldr": "**结论**:共享只读技能层:dsh **原生支持** `bundledSkillDir`(全员可用、不可修改)。"
},
{
"path": "04-调整方案/100-实例内我的技能-并入功能管理分组.md",
"num": "100",
"title": "100 · 实例内「我的技能」—— 并入「功能管理」的分组方案与实现",
"status": "✅ 已实施并投放(`busi",
"date": "2026-09-15",
"chars": 12599,
"lines": 251,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "method",
"tldr": "**结论**:在**既有「功能管理」section 内新增「我的技能」分组**(**不新开 section**),用户在同一页看完并管理「功能插件 + 我的技能」两类功能;技能行支持 上传 / 启用 / 停用 / 删除,平台共享技能显示为*"
},
{
"path": "04-调整方案/101-能力管理-改名与tab分页与卡片三行.md",
"num": "101",
"title": "101 · 「能力管理」:分区改名 + 页内 tab 分页 + 插件卡片三行描述 + DeepSeek 改名",
"status": "✅ 已实施并投放",
"date": "2026-09-15",
"chars": 6575,
"lines": 152,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:分区改名「**能力管理**」(label 级),页内改为 **tab 分页**(功能插件 / 我的技能,各自独立操作),插件卡片的**中文用途描述从 1 行放宽到 3 行**(`.bp-plugDesc`),并把「**内置 D"
},
{
"path": "04-调整方案/102-语言切换搬入用户设置并撤除偏好设置.md",
"num": "102",
"title": "102 · 语言切换从「偏好设置」搬进「用户设置」,并撤除偏好设置分区",
"status": "✅ 已实施并投放",
"date": "2026-09-15",
"chars": 6957,
"lines": 156,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "ui",
"tldr": "**结论**:语言切换搬进 **`@dsh-local/portal-entry` 的「用户设置」分区**(id `user-settings`,order 103),"
},
{
"path": "04-调整方案/103-客户端安装与覆盖网络互联-可行性评估.md",
"num": "103",
"title": "103 · 客户端安装与覆盖网络互联 · 可行性评估",
"status": "📋 规划态 / 未实施(本轮",
"date": "2026-09-16",
"chars": 11661,
"lines": 242,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> ✅ **可行,且现有架构已给出约 80% 的形状** —— T08 集群化已经把「一台机器 = 一个可被平台拨入的执行体」定义完了,"
},
{
"path": "04-调整方案/104-覆盖网络-全球架构复盘.md",
"num": "104",
"title": "104 · 覆盖网络 · 全球架构复盘",
"status": "📋 规划态 / 未实施(架构",
"date": "2026-09-16",
"chars": 9621,
"lines": 267,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> ✅ **有完整可循的工程路径** —— Tailscale / ZeroTier / Nebula / libp2p / BitTorrent 已反复验证过,**关键是照抄它们踩过的坑,而不是自己发明**。"
},
{
"path": "04-调整方案/105-覆盖网络-骨干层方案.md",
"num": "105",
"title": "105 · 覆盖网络 · 骨干层方案",
"status": "📋 规划态 / 未实施(设计",
"date": "2026-09-16",
"chars": 7710,
"lines": 254,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "?",
"tldr": "> ✅ **可以,而且是成熟系统里的标准模式** —— 业内叫「**超级节点 / 骨干层(supernode / backbone)**」(ZeroTier Moon · Nebula Lighthouse · Tailscale DERP"
},
{
"path": "04-调整方案/106-覆盖网络-百台规模推演-v2.md",
"num": "106",
"title": "106 · 覆盖网络 · 百台规模推演-v2",
"status": "📋 规划态",
"date": "2026-09-16",
"chars": 8519,
"lines": 255,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/107-覆盖网络-千台全场景推演.md",
"num": "107",
"title": "107 · 覆盖网络 · 千台全场景推演",
"status": "📋 规划态(文字推演",
"date": "2026-09-16",
"chars": 9463,
"lines": 290,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "?",
"tldr": "> 1000 台异构设备 × 11 个场景的流量推演。**控制面在 1000 台规模仍不是瓶颈**(50 req/s);"
},
{
"path": "04-调整方案/108-覆盖网络-游戏专项-MMORPG与MUD.md",
"num": "108",
"title": "108 · 覆盖网络 · 游戏专项-MMORPG与MUD",
"status": "📋 规划态 / 未实施",
"date": "2026-09-16",
"chars": 7498,
"lines": 231,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> 这三类游戏的架构(**服务端权威 + tick 驱动 + AOI 九宫格广播 + 分区/分线**)**本身就是覆盖网络友好型的**,"
},
{
"path": "04-调整方案/109-覆盖网络-调研-游戏网络特征与群聊上限.md",
"num": "109",
"title": "109 · 覆盖网络 · 调研-游戏网络特征与群聊上限",
"status": "📋 规划态(全网调研稿",
"date": "2026-09-16",
"chars": 7347,
"lines": 203,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> 两部分:① **这类游戏的网络特征**(传奇 / MMORPG / MUD 的每玩家带宽、同步间隔、承载、延迟/丢包门槛);"
},
{
"path": "04-调整方案/11-技能管理面-shared+mine-API与页面.md",
"num": "11",
"title": "11-技能管理面(admin 共享 + 普通用户个人)",
"status": "已实施 + API 全链路验",
"date": "04-11",
"chars": 7789,
"lines": 176,
"refs": 28,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "method",
"tldr": "**结论**:补完技能管理面:admin 管**全员共享技能** + 每个用户管**自己的个人技能**(`/api/skills/{shared,mine}` + 页面)。"
},
{
"path": "04-调整方案/110-覆盖网络-答疑-群聊备份迁移保密.md",
"num": "110",
"title": "110 · 覆盖网络 · 答疑-群聊备份迁移保密",
"status": "📋 规划态(技术答疑稿",
"date": "2026-09-16",
"chars": 6824,
"lines": 221,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "ops",
"tldr": "> 四问四答:① **群聊 + agent 入群** = ✅ 可实现(群聊是**应用层**的事,覆盖网络只解决「可达」);② **备份** = **主备份优先对象存储**,"
},
{
"path": "04-调整方案/111-覆盖网络-补遗与参考方案.md",
"num": "111",
"title": "111 · 覆盖网络 · 补遗与参考方案",
"status": "📋 规划态(补遗复盘稿",
"date": "2026-09-16",
"chars": 8308,
"lines": 251,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> 四部分:① **互联游戏可行性**(✅ 支持,但**由游戏形态决定**;优先做「**只传输入**」的锁步/回合制);"
},
{
"path": "04-调整方案/112-覆盖网络-九大瓶颈落地方案.md",
"num": "112",
"title": "112 · 覆盖网络 · 九大瓶颈落地方案",
"status": "📋 规划态 / 未实施",
"date": "2026-09-16",
"chars": 9158,
"lines": 282,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "method",
"tldr": "> 把 107 §4 排出的**九大瓶颈**逐个给成**可执行做法 + 验收判据**(含 Slack / SCCM 官方照抄点)。"
},
{
"path": "04-调整方案/12-VoxEMW全云API化接入dsh-调研与M1落地.md",
"num": "12",
"title": "12-VoxEMW 全云 API 化接入 dsh(调研 + M1 落地)",
"status": "已冻结",
"date": "04-12",
"chars": 4117,
"lines": 77,
"refs": 4,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/13-登录直达冷启动竞态404修复.md",
"num": "13",
"title": "13-登录直达冷启动竞态404修复",
"status": "已落地 + 验证通过",
"date": "04-13",
"chars": 2444,
"lines": 58,
"refs": 5,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "04-调整方案/14-实例会话敏感信息暴露面审计与加固.md",
"num": "14",
"title": "14 · 实例会话敏感信息暴露面审计与加固",
"status": "审计已完成 → 加固项待用户",
"date": "2026-09-10",
"chars": 8235,
"lines": 240,
"refs": 7,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:实例会话敏感信息暴露面审计:**跨租户 / 提权不成立**(门户资产全部拒绝访问)。"
},
{
"path": "04-调整方案/15-会话失效401未跳登录页修复与guest可见面复核.md",
"num": "15",
"title": "15 · 会话失效 401 未跳登录页修复 + guest 会话可见面复核",
"status": "已上线,页面全部 200",
"date": "2026-09-10",
"chars": 5856,
"lines": 154,
"refs": 5,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "04-调整方案/16-页面导航定稿-技能插件管理面三决策落地.md",
"num": "16",
"title": "16 · 页面导航定稿 + 插件三层归属模型(方案)",
"status": "已封板,实施中",
"date": "2026-09-10",
"chars": 6869,
"lines": 121,
"refs": 37,
"refsCurrent": 3,
"tier": "hot",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:技能/插件管理面定稿:**技能与插件各独立页面**(`skills.html` / `plugins.html`,公共面仅 admin)+「我的技能」走**实例设置页 section**。"
},
{
"path": "04-调整方案/17-工作区选择器暴露面核查.md",
"num": "17",
"title": "17 · 工作区选择器暴露面核查(\"选择工作区目录\"为何能看到 `/`)",
"status": "核查完成 → 收敛项 H1-",
"date": "2026-09-10",
"chars": 5124,
"lines": 91,
"refs": 11,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:「添加工作区」为何能看到 `/`:**不是越权漏洞**(跨租户与系统目录读/写均被拦),但确有两个真问题。"
},
{
"path": "04-调整方案/18-目录选择器收敛为仅见自有目录.md",
"num": "18",
"title": "18 · 会话内目录选择器收敛为\"仅见自有目录\"(含 admin)",
"status": "✅ 已实施并在 admin/",
"date": "2026-09-10",
"chars": 10704,
"lines": 216,
"refs": 25,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:目录选择器收敛 **v3 定稿**:官方对话框 UI 保留 + **自建 host 插件把根钉在 `<userRoot>/ws`**(含 admin)+ CSS 隐藏「改路径」入口。"
},
{
"path": "04-调整方案/19-方案与代码全面审查.md",
"num": "19",
"title": "19 · 方案与代码全面审查(优化项 / 合并项 / 过期项)",
"status": "🔄 批次 1 因改走 bun",
"date": "2026-09-10",
"chars": 6639,
"lines": 67,
"refs": 27,
"refsCurrent": 4,
"tier": "hot",
"layer": "L5",
"domain": "method",
"tldr": "**结论**:全面审查(代码 10 项 + 文档 8 项):**3 个 P1**(含 1 个会阻塞档案 18 落地)与批次整改计划。"
},
{
"path": "04-调整方案/20-崩溃自愈现状核实与加固方案.md",
"num": "20",
"title": "20 · 崩溃自愈现状核实与加固方案",
"status": "方案 A + handoff",
"date": "2026-09-10",
"chars": 8099,
"lines": 155,
"refs": 26,
"refsCurrent": 3,
"tier": "hot",
"layer": "L5",
"domain": "ops",
"tldr": "**结论**:**订正档案 19 §C4**:崩溃自愈**本来就有**(`exit` → 1 s 退避重启 main,与 watchdog 无关)。"
},
{
"path": "04-调整方案/21-guest会话卡顿排查.md",
"num": "21",
"title": "21 · guest 会话\"卡顿 / 断开显示连接中\"排查",
"status": "根因已定位并修复(nginx",
"date": "2026-09-10",
"chars": 6418,
"lines": 130,
"refs": 9,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "ops",
"tldr": "**结论**:guest「卡顿 / 显示连接中」排查:**服务端与模型都不慢**(TTFT 1.0–3.5 s、实例 TTFB 2 ms、nginx 全 <5 s)。"
},
{
"path": "04-调整方案/22-服务域名迁移到alotbuy.com.md",
"num": "22",
"title": "22 · 服务域名迁移:dsh.alotbuy.com → alotbuy.com",
"status": "已上线",
"date": "2026-09-10",
"chars": 4894,
"lines": 99,
"refs": 11,
"refsCurrent": 6,
"tier": "hot",
"layer": "L5",
"domain": "ui",
"tldr": "**结论**:域名迁移完成:门户 **`alotbuy.com`**、用户实例 **`<用户名>.alotbuy.com`**;旧域 `dsh.alotbuy.com` 全部 **301**(含用户名映射)。"
},
{
"path": "04-调整方案/23-实例内AI能力与权限限制核查.md",
"num": "23",
"title": "23 · 实例内 AI 能力与权限限制核查(guest 对话记录)",
"status": "修复已编译(CI ✅),待重",
"date": "2026-09-11",
"chars": 3925,
"lines": 66,
"refs": 13,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:guest 报的 9 条环境限制逐条判定:**1 条真 P1**(合成根缺 `/bin /sbin /lib` → dsh 沙箱探针失败 → **实例内 bash 工具被整体拒绝**,已修)+ 3 条可优化 + 4 条设计使然"
},
{
"path": "04-调整方案/24-实例侧401自动恢复.md",
"num": "24",
"title": "24 · 实例侧 401(launch token 过期)浏览器导航自动恢复",
"status": "已实施并上线",
"date": "2026-09-11",
"chars": 2074,
"lines": 51,
"refs": 5,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/25-实例崩溃循环修复与not_running兜底.md",
"num": "25",
"title": "25 · 实例崩溃循环事故(重复 loader id)+ not_running 浏览器导航兜底",
"status": "已修复并上线(服务已重启",
"date": "2026-09-11",
"chars": 2662,
"lines": 62,
"refs": 11,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/26-dsh升级耦合点与回归清单.md",
"num": "26",
"title": "26 · dsh 升级耦合点与回归清单",
"status": "清单建立",
"date": "2026-09-11",
"chars": 3168,
"lines": 57,
"refs": 12,
"refsCurrent": 3,
"tier": "hot",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/27-MCN工作台插件平台化评估.md",
"num": "27",
"title": "27 · MCN 工作台插件平台化评估",
"status": "?",
"date": "2026-09-11",
"chars": 5568,
"lines": 89,
"refs": 3,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/28-用户数据清理策略.md",
"num": "28",
"title": "28 · 用户数据清理策略(工作区 / 会话 / 回收站)",
"status": "✅",
"date": "2026-09-11",
"chars": 4095,
"lines": 79,
"refs": 10,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "external",
"tldr": ""
},
{
"path": "04-调整方案/29-官方白名单插件来源.md",
"num": "29",
"title": "29 · 官方白名单插件来源(方案 C · 方案 B 口径)",
"status": "✅ 已实施并端到端验证",
"date": "2026-09-11",
"chars": 6702,
"lines": 131,
"refs": 15,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:dsh 官方白名单插件接入门户插件管理(方案 C):官方目录 **3408 款**,npm 预构建路径覆盖 **52.6%**(下载 TOP10 全覆盖)。"
},
{
"path": "04-调整方案/30-编排器孤儿实例清理.md",
"num": "30",
"title": "30 · 编排器孤儿实例清理(单实例保证从内存升到 OS 层)",
"status": "✅ 已实施并 live 验证",
"date": "2026-09-11",
"chars": 2199,
"lines": 64,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/31-插件管理页双Tab与说明为主视觉.md",
"num": "31",
"title": "31 · 插件管理页双 Tab + 说明为主视觉 + 目录字段用全",
"status": "✅ 已实施并视觉验证",
"date": "2026-09-11",
"chars": 4775,
"lines": 103,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/32-mcntimo会话取证与沙箱P0核查.md",
"num": "32",
"title": "32 · mcntimo 会话取证与「dsh 沙箱不可用」P0 核查",
"status": "🔍 核查完成,P0 待决策",
"date": "2026-09-11",
"chars": 3632,
"lines": 78,
"refs": 9,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "method",
"tldr": "**结论**:admin 在 mcntimo 工作区的会话取证 → 查出 **「dsh 沙箱不可用 → 拒绝执行任何 shell」** 这一 P0。"
},
{
"path": "04-调整方案/33-实例权限默认档位改为完全权限.md",
"num": "33",
"title": "33 · 实例权限默认档位改为「完全权限」(复用官方 DSH_PERMISSION_MODE)",
"status": "✅ 已实施(commit 见",
"date": "2026-09-11",
"chars": 3410,
"lines": 74,
"refs": 11,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:实例权限默认档位改为**「完全权限」**(复用官方 `DSH_PERMISSION_MODE`),避免 agent 每步都弹确认。"
},
{
"path": "04-调整方案/34-功能插件启用探活与逐插件隔离.md",
"num": "34",
"title": "34 · 功能插件启用:探活 + 快照回滚 + 逐插件隔离标记",
"status": "✅ 已实施(commit `",
"date": "2026-09-11",
"chars": 2625,
"lines": 61,
"refs": 14,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/35-ws-cleanup误删平台bundle包.md",
"num": "35",
"title": "35 · ws-cleanup 误删平台 bundle 包(P0 回归修复)",
"status": "✅ 已修复(commit `",
"date": "2026-09-11",
"chars": 1660,
"lines": 47,
"refs": 3,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/36-功能插件分区铺给普通用户.md",
"num": "36",
"title": "36 · 功能插件分区铺给普通用户 + 新用户自动铺(批次 2)",
"status": "✅ 已实施(commit `",
"date": "2026-09-11",
"chars": 2667,
"lines": 77,
"refs": 7,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/37a-guest会话取证与平台缺陷清单.md",
"num": "37a",
"title": "37a · guest 会话取证与平台缺陷清单(MCN短视频创作)",
"status": "🔍 取证完成",
"date": "2026-09-11",
"chars": 8997,
"lines": 168,
"refs": 8,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:从 guest 的「MCN短视频创作」会话反查平台缺陷清单(**只记录缺陷,不含代码改动**)。"
},
{
"path": "04-调整方案/37b-功能插件分区v0.2官方token与i18n.md",
"num": "37b",
"title": "37b · 功能插件分区 v0.2.0:官方 token 化 + i18n + 交互升级(批次 3)",
"status": "✅ 已实施(commit `",
"date": "2026-09-11",
"chars": 2765,
"lines": 63,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ui",
"tldr": "**结论**:「功能插件」section 升级 v0.2:**官方 `--dsw-*` design token**(自动跟随亮/暗/第三方主题)+ 官方 locale 中英双语。"
},
{
"path": "04-调整方案/38a-实例软件安装共享与网络安边界核查.md",
"num": "38a",
"title": "38a · 实例内软件安装、共享复用可行性、网络与安全边界核查",
"status": "🔍 核查完成",
"date": "2026-09-11",
"chars": 9620,
"lines": 224,
"refs": 10,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:回答\"每个用户是否要各装一份\":**宿主 `/usr` 已 ro-bind → 宿主装一次、全部实例共享**;同时暴露最大隐患 = 实例与宿主**共享网络命名空间**(可访问 `127.0.0.1:3080/22` 等)。"
},
{
"path": "04-调整方案/38b-术语统一业务插件改功能插件.md",
"num": "38b",
"title": "38b · 术语统一「业务插件」→「功能插件」(含 0.2.1 与脚本加固)",
"status": "✅ 已实施(`99de8c5",
"date": "2026-09-11",
"chars": 3334,
"lines": 72,
"refs": 6,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:「业务插件」统一改名 **功能插件**(字段 / 文案 / 文档),含 v0.2.1 与脚本加固。"
},
{
"path": "04-调整方案/39-实例可见面收窄与宿主访问封锁.md",
"num": "39",
"title": "39-实例可见面收窄(/etc 白名单 + 宿主访问封锁)(2026-09-11 落地)",
"status": "✅ 已落地",
"date": "04-39",
"chars": 6221,
"lines": 150,
"refs": 37,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:按用户要求收窄实例可见面:`/etc` 改**白名单**,并**封 `127.0.0.0/8` 等四类目的地址**(宿主 loopback、内网卡、docker0、公网 EIP)。"
},
{
"path": "04-调整方案/40-共享技能层挂载修复.md",
"num": "40",
"title": "40-共享技能层挂载修复(bundled-skills 进实例命名空间)(2026-09-11 落地)",
"status": "✅",
"date": "04-40",
"chars": 2596,
"lines": 71,
"refs": 4,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "04-调整方案/41-技能上传安全加固与用户技能启停.md",
"num": "41",
"title": "41-技能上传安全加固与用户技能启停(2026-09-11 落地)",
"status": "✅",
"date": "04-41",
"chars": 4634,
"lines": 118,
"refs": 17,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "04-调整方案/42-实例共享Python运行时与会话取证复核.md",
"num": "42",
"title": "42-实例共享 Python 运行时与会话取证复核(2026-09-11)",
"status": "✅ 已修复",
"date": "04-42",
"chars": 8303,
"lines": 149,
"refs": 13,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:会话取证发现 `python3` 不存在 —— 实为**档案 39 收窄 `/etc` 引入的回归**;本轮改为实例侧使用**共享 Python 运行时**(宿主装一次、全员可用)。"
},
{
"path": "04-调整方案/43-平台root污染用户工作区与属主自愈.md",
"num": "43",
"title": "43-平台 root 污染用户工作区与属主自愈(2026-09-11 落地)",
"status": "✅",
"date": "04-43",
"chars": 1938,
"lines": 47,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "external",
"tldr": ""
},
{
"path": "04-调整方案/44-基础运行时版本冻结.md",
"num": "44",
"title": "44-基础运行时版本冻结(禁止用户升级 Python/pip/node)(2026-09-11 落地)",
"status": "✅",
"date": "04-44",
"chars": 2806,
"lines": 79,
"refs": 3,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/45-存量会话新开会话提示.md",
"num": "45",
"title": "45-存量会话「新开会话」提示(P0-1 的最小代价处置)(2026-09-11 落地)",
"status": "✅",
"date": "04-45",
"chars": 1919,
"lines": 53,
"refs": 6,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/46-实例共享工具jq-ripgrep-ffmpeg.md",
"num": "46",
"title": "46-实例共享工具(jq / ripgrep / ffmpeg)(2026-09-11 落地)",
"status": "✅",
"date": "04-46",
"chars": 2404,
"lines": 61,
"refs": 1,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/47-运行环境管理页.md",
"num": "47",
"title": "47-运行环境管理页(admin 可视化共享运行时与工具)(2026-09-11 落地)",
"status": "✅",
"date": "04-47",
"chars": 1670,
"lines": 52,
"refs": 4,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/49-实例回收后首次访问的反馈与自愈.md",
"num": "49",
"title": "49-实例回收后首次访问的反馈与自愈(2026-09-11 落地)",
"status": "✅ 已落地",
"date": "04-49",
"chars": 2907,
"lines": 67,
"refs": 10,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:实例被空闲回收后首次访问\"没反应\":**拉起逻辑早就有,缺的是反馈**。"
},
{
"path": "04-调整方案/50-会话过期自愈注入脚本.md",
"num": "50",
"title": "50-会话过期自愈:实例 HTML 注入「重连」脚本(2026-09-11 落地)",
"status": "?",
"date": "04-50",
"chars": 4368,
"lines": 116,
"refs": 9,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/51-实例回收后401透明重放.md",
"num": "51",
"title": "档案 51 · 实例回收后「继续发消息」失败 —— 实例侧 401 透明重放",
"status": "已落地并实测验证",
"date": "04-51",
"chars": 4656,
"lines": 140,
"refs": 11,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:实例被回收后「继续发消息」报错:实例侧 401 由代理**透明重放**(带最新 launch token 自动重试),用户不必手动刷新。"
},
{
"path": "04-调整方案/52-新用户实例无法启动.md",
"num": "52",
"title": "档案 52 · 新用户实例无法启动 —— 三处连锁缺陷(picker 铺开脚本)",
"status": "已落地并端到端验证",
"date": "04-52",
"chars": 3410,
"lines": 103,
"refs": 6,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/53-文档质量审查与精简方案.md",
"num": "53",
"title": "53 · 文档库质量审查与精简方案",
"status": "🔄 第一批已修复",
"date": "2026-09-11",
"chars": 4780,
"lines": 129,
"refs": 12,
"refsCurrent": 4,
"tier": "hot",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "04-调整方案/54-文档信息架构优化-BRIEF与机读清单.md",
"num": "54",
"title": "54 · 文档信息架构优化:BRIEF 现状卡 + 机读清单",
"status": "✅ 已实施(两批):第一批 ",
"date": "2026-09-11",
"chars": 4244,
"lines": 100,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "method",
"tldr": "结论 / 关键 / 状态`),紧接头部置顶 | ✅ 已插入(含被引最多的 19/16/18/20/10/11/37/38…)。效果:**读档案第一屏即可判断要不要读全文**(每份 TL;DR ≈150–250 字符)。11 份需补空行(已修"
},
{
"path": "04-调整方案/55-guest最新会话取证与优化项.md",
"num": "55",
"title": "55 · guest 最新会话取证与优化项(2026-09-11)",
"status": "🔍 取证完成",
"date": "2026-09-11",
"chars": 4584,
"lines": 100,
"refs": 8,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "04-调整方案/56-实例助手与文件下载端点.md",
"num": "56",
"title": "56 · 实例助手:我的文件 / 能力清单 / 档位提示(+ 文件下载端点)",
"status": "✅ 已实施并端到端验证(co",
"date": "2026-09-11",
"chars": 4796,
"lines": 124,
"refs": 13,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/57-设置面板用户管理入口与全员安装.md",
"num": "57",
"title": "57 · 设置面板「用户管理」入口:改名、移位、全员安装",
"status": "✅ 已实施并验证(服务器已生",
"date": "2026-09-11",
"chars": 7470,
"lines": 151,
"refs": 19,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ui",
"tldr": ""
},
{
"path": "04-调整方案/58-实例内存优化与配额下调.md",
"num": "58",
"title": "58 · 实例内存优化:V8 堆上限、编译缓存与配额 512→384",
"status": "✅ 已实施并验证(服务器已生",
"date": "2026-09-12",
"chars": 5394,
"lines": 118,
"refs": 22,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "04-调整方案/59-重连反馈-实例启动加载动画.md",
"num": "59",
"title": "59 · 重连过程的可见反馈:实例启动中的加载动画",
"status": "✅ 已实施并验证(服务器已生",
"date": "2026-09-12",
"chars": 3395,
"lines": 95,
"refs": 7,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/60-设置面板分区改名-功能插件改功能管理.md",
"num": "60",
"title": "60 · 设置面板分区改名:功能插件 → 功能管理",
"status": "✅ 已实施并验证(服务器已生",
"date": "2026-09-12",
"chars": 3699,
"lines": 92,
"refs": 9,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/61-插件管理页官方插件列表加高与底部留白.md",
"num": "61",
"title": "61 · 插件管理页:官方插件列表加高 + 页面底部留白 200px",
"status": "✅ 已实施并验证(服务器已生",
"date": "2026-09-12",
"chars": 3551,
"lines": 98,
"refs": 3,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/62-插件目录缓存状态可见化与重新拉取按钮.md",
"num": "62",
"title": "62 · 插件目录:缓存状态可见化 + 「重新拉取目录」按钮",
"status": "✅ 已实施并验证(服务器已生",
"date": "2026-09-12",
"chars": 2095,
"lines": 60,
"refs": 5,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/64-接入AnySearch搜索provider.md",
"num": "64",
"title": "64 · 接入 AnySearch 搜索 provider(B 方案)",
"status": "admin 侧已实施",
"date": "2026-09-12",
"chars": 10872,
"lines": 245,
"refs": 9,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:接 AnySearch 技术上零障碍(官方插件 `@anysearch/[email protected]`,MIT,自带 `searchProvider: anysearch` 配置);**卡点不在技术,在「key 归属"
},
{
"path": "04-调整方案/65-功能插件启停与web-provider配置联动.md",
"num": "65",
"title": "65 · 功能插件启停与 web provider 配置联动",
"status": "✅ 已部署并生效(服务器 `",
"date": "2026-09-12",
"chars": 5069,
"lines": 126,
"refs": 21,
"refsCurrent": 3,
"tier": "hot",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:候选池「禁用即坏」的根因不是候选池,而是 profile 层那段**硬绑定**的 provider 覆写 —— 插件一被 `pnpm remove`,配置就指向了不存在的 provider(`CONFIGURED_MISSIN"
},
{
"path": "04-调整方案/66-业务插件P0误报与admin显式信任.md",
"num": "66",
"title": "66 · 业务插件上传的「P0 误报」与 admin 显式信任",
"status": "✅ 已实现、已验证、已部署",
"date": "2026-09-12",
"chars": 3376,
"lines": 94,
"refs": 20,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "plugin",
"tldr": "**结论**:P0 规则 `/\\.credentials\\.yaml/` 是**纯字面量匹配、扫所有文本文件**,第三方插件的 README 只要教用户把 key 写进凭据文件就会被判「读取实例会话密钥」—— 这是第二次同类误报(档案 29"
},
{
"path": "04-调整方案/67-功能管理section按UI规范重做.md",
"num": "67",
"title": "67 · 「功能管理」section 按 UI 规范重做(v0.2.4)",
"status": "✅ 已完成并部署",
"date": "2026-09-12",
"chars": 7270,
"lines": 140,
"refs": 3,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "ui",
"tldr": "**结论**:规范第 5 行明确「含其 client 面 section」,本页在约束内,逐项核对确认「简陋」成立;主视觉原本是包名(说明只作 11px 灰字),与门户 plugins 页相反 —— 已反转。"
},
{
"path": "04-调整方案/68-候选池启停的root属主污染根治.md",
"num": "68",
"title": "68 · 候选池启停的 root 属主污染:根治",
"status": "✅ 全部完成并验证",
"date": "2026-09-12",
"chars": 3186,
"lines": 86,
"refs": 4,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": "**结论**:门户候选池的 `install/uninstall` 一直**以平台进程身份(root)跑 pnpm**,装出来的文件属主是 root → 该用户此后**任何** `pnpm add/remove` 都必然 `EACCES`。"
},
{
"path": "04-调整方案/69-并发治理落地-commit常态化与服务器侧锁.md",
"num": "69",
"title": "69 · 并发治理落地(T04):文档库 commit 常态化 + 服务器侧操作锁 + 权限统一",
"status": "✅ 已完成(2026-09-",
"date": "2026-09-12",
"chars": 3760,
"lines": 70,
"refs": 3,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "method",
"tldr": "文档冲突靠 `git status`/mtime 还能看出来,**服务器态变更看不出来**(`systemctl` 不会告诉你 10 分钟前谁重启过)→ 必须靠显式锁。本档记录这套机制的最终形态与验证证据。"
},
{
"path": "04-调整方案/70-anysearch插件不兼容致崩溃循环.md",
"num": "70",
"title": "70 · anysearch 插件与 dsh 0.1.2-rc.1 不兼容 → admin 实例崩溃循环(已止损)",
"status": "✅ 已止损",
"date": "2026-09-12",
"chars": 5950,
"lines": 126,
"refs": 22,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/71-插件兼容性预检-导入上传即判定.md",
"num": "71",
"title": "71 · 插件兼容性预检:导入 / 上传即判定(避免\"装完起不来\")",
"status": "✅ 已落地并部署(2026-",
"date": "2026-09-12",
"chars": 6781,
"lines": 152,
"refs": 12,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "04-调整方案/72-实例回收后回到页面自动唤醒重建连接.md",
"num": "72",
"title": "72 · 实例被回收/关闭后,回到会话页面自动唤醒并重建连接",
"status": "✅ 已完成并部署(2026-",
"date": "2026-09-12",
"chars": 3791,
"lines": 85,
"refs": 11,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "ui",
"tldr": ""
},
{
"path": "04-调整方案/73-让锁真正拦得住人-措辞修正与PreToolUse强制钩子.md",
"num": "73",
"title": "73 · 让「锁」真正拦得住人:措辞修正 + PreToolUse 强制钩子",
"status": "✅ 已实现并单点验证",
"date": "2026-09-12",
"chars": 11230,
"lines": 276,
"refs": 5,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "04-调整方案/74-实例内存治理-V8堆限下调与阈值告警.md",
"num": "74",
"title": "74 · 实例内存治理:V8 堆限下调 + 内存阈值告警(2026-09-12)",
"status": "✅ 已落地并实测验证(配置 ",
"date": "2026-09-12",
"chars": 6958,
"lines": 169,
"refs": 4,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "04-调整方案/75-插件评估新增托管友好性与资源成本两个维度.md",
"num": "75",
"title": "75 · 插件评估新增「托管友好性」与「资源成本」两个维度(2026-09-12)",
"status": "📋 标准已立",
"date": "2026-09-12",
"chars": 3633,
"lines": 123,
"refs": 8,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/76-dsh-univer-office平台适配改造-unix-socket与同源代理.md",
"num": "76",
"title": "76 · dsh-univer-office 平台适配改造:unix socket 传输 + 同源 Viewer 代理(2026-09-12)",
"status": "✅ 代码改造 + 组件级验证",
"date": "2026-09-12",
"chars": 25390,
"lines": 451,
"refs": 5,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/77-回到页面自检与就地恢复-恢复过程可见化.md",
"num": "77",
"title": "77 · 回到页面自检 + 就地恢复:把「恢复过程」做成看得见的",
"status": "✅ 已落地并验证(服务器 `",
"date": "2026-09-13",
"chars": 11654,
"lines": 223,
"refs": 11,
"refsCurrent": 2,
"tier": "cur",
"layer": "L5",
"domain": "ui",
"tldr": "**结论**:提示\"看不到\"不是没做,是**判据失效 + 提示只活 600ms**。"
},
{
"path": "04-调整方案/78-崩溃熔断冷却期与告警.md",
"num": "78",
"title": "78 · 崩溃熔断:冷却期 + 告警(防「崩溃循环可无限重来」)",
"status": "✅ 已部署并验证(2026-",
"date": "2026-09-13",
"chars": 5969,
"lines": 111,
"refs": 10,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "① 熔断态放进独立 `breaker` Map,**不被 `resetCrashState()` 清**;② 熔断后冷却 **10 min × 2^(n-1),封顶 6 h**,冷却期内 `launch()` 抛 `CrashBreaker"
},
{
"path": "04-调整方案/79-插件启停的两处平台缺陷-uninstall缺await与无效pnpm-flag.md",
"num": "79",
"title": "79 · 插件启停的两处平台缺陷:`uninstall` 缺 `await`(把整个 orchestrator 带崩)+ `pnpm remove` 用了无效 ",
"status": "✅ 已修复并部署",
"date": "2026-09-13",
"chars": 4723,
"lines": 79,
"refs": 6,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": "D1(缺 `await`)→ 未捕获 Promise 拒绝 → orchestrator 退出;D2(无效 flag)→ 让 D1 必然被触发;D3(内存不够)→ 让流程必然走进触发 D1 的分支。"
},
{
"path": "04-调整方案/80-架构与功能优化评估-保留功能前提下的重构方向.md",
"num": "80",
"title": "80 · 架构与功能优化评估(**保留现有功能**前提下的重构方向 + 去平台痕迹)",
"status": "📋 评估中",
"date": "2026-09-13",
"chars": 4593,
"lines": 101,
"refs": 17,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "**不推倒重来** —— 平台本体(账号 / 审批 / 实例生命周期 / 反代 / 配额 / DB)就是要保留的那部分,重写 = 把已验证的东西再赌一次、且**零收益**。"
},
{
"path": "04-调整方案/81-目标架构与命名规范-重构总纲.md",
"num": "81",
"title": "81 · 目标架构与命名规范(重构总纲)",
"status": "🚧 执行中(R0 已完成",
"date": "2026-09-13",
"chars": 25616,
"lines": 500,
"refs": 114,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "① 定下**一套命名**:对外叫「**工作台**」、内部统一前缀 **`dshs`**(替换 `dshs`);"
},
{
"path": "04-调整方案/82-R2管理面就地化-原生平台管理分区.md",
"num": "82",
"title": "82 · R2 管理面就地化(原生「平台管理」分区)",
"status": "🚧 代码完成、产物已出",
"date": "2026-09-13",
"chars": 92038,
"lines": 2048,
"refs": 4,
"refsCurrent": 1,
"tier": "cur",
"layer": "L5",
"domain": "platform",
"tldr": "① R2 的 **R5 权限影响评估**已在档案 81 §9.2 出齐并获批(扩大点=实例内出现可操作的管理入口 ⇒ **仅 admin 可见** + **只读** + 写操作回跳);"
},
{
"path": "04-调整方案/83-登录注册页按UI规范对齐与显示密码.md",
"num": "83",
"title": "83 · 登录 / 注册页按 UI 规范对齐 + 显示密码 + 文案修正",
"status": "✅ 已完成并上线验证",
"date": "2026-09-13",
"chars": 2969,
"lines": 67,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "ops",
"tldr": "① 查实:登录页用的是 `design.css` —— 一套**深色 OS-desktop 体系**,与 `06-工作台UI规范`(**强制基线**、冲突时以它为准)**全面冲突**;"
},
{
"path": "04-调整方案/84-实例内存配额口径统一-消灭388误报.md",
"num": "84",
"title": "84-实例内存配额口径统一(消灭「388 MiB」误报)",
"status": "?",
"date": "04-84",
"chars": 4837,
"lines": 98,
"refs": 3,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "04-调整方案/85-模型密钥开放给用户自助配置-两层密钥.md",
"num": "85",
"title": "85 · 模型密钥开放给用户自助配置(两层密钥:自配自用 + 平台共享回落)",
"status": "✅ 已上线并端到端验证(后端",
"date": "2026-09-13",
"chars": 12153,
"lines": 236,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "① 原先平台是「**统一 KEY**」——`resolveApiKey()` **显式忽略入参 userId**,不管谁 spawn 都注入 admin 那一把;② 本轮改为**两层**:**用户自己的 key 优先,没有才回落管理员的「平"
},
{
"path": "04-调整方案/86-admin跨用户实例管理-两处改名.md",
"num": "86",
"title": "86 · admin 跨用户实例/文件管理 + 两处改名(实例管理 / 模型管理)",
"status": "✅ 已上线并端到端验证(后端",
"date": "2026-09-13",
"chars": 5613,
"lines": 128,
"refs": 8,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "① 平台**所有**服务/文件 API 都是 `request.user.id` 语义(`desktop.ts` 头注释原文 \"one user can never address another user's files\")⇒ admin"
},
{
"path": "04-调整方案/87-模型设置页-用户自配厂家与共享开关.md",
"num": "87",
"title": "87 · 平台自建「模型设置」—— 用户自配厂家 / 条目各自开关 / 共享模型开关",
"status": "✅ 已上线并端到端验证(后端",
"date": "2026-09-13",
"chars": 14028,
"lines": 218,
"refs": 12,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "① 官方模型页必须对**所有人(含 admin)**禁用 —— 它要求 Host settings 镜像,而平台是\"浏览器经域名访问远程服务器\"⇒ `isLoopback=false` ⇒ persistence 降级 `memory` ⇒"
},
{
"path": "04-调整方案/88-内置dsh安装路径探测-修静默失效P1.md",
"num": "88",
"title": "88 · 内置 dsh 安装路径按序探测 —— 修「厂家目录 / 平台包目录在 /usr/lib 布局下静默失效」(P1)",
"status": "✅ 已修复并验证(源仓 `c",
"date": "2026-09-14",
"chars": 5166,
"lines": 92,
"refs": 1,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "external",
"tldr": "平台有**三处**把「内置 dsh 的安装目录」写死成 `/usr/local/lib/node_modules/@deepseek-ai/dsh`。而 `npm root -g` 的落点**随发行版变**(发行版包管理器装的 Node 常"
},
{
"path": "04-调整方案/89-对话内文件预览-采纳官方推荐库现成插件.md",
"num": "89",
"title": "89-对话内文件预览——采纳官方推荐库现成插件(2026-09-14 落地)",
"status": "🔄 进行中(L2 机制级已验",
"date": "2026-09-14",
"chars": 6647,
"lines": 120,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "plugin",
"tldr": "> **不重新开发、也不改造 univer** —— 官方推荐库里有现成的,且有一个与我们的 dsh 版本**精确匹配**:"
},
{
"path": "04-调整方案/90-dsh升级项目-0.1.2-rc.1到0.1.5-rc.1.md",
"num": "90",
"title": "90-dsh 升级项目:0.1.2-rc.1 → 0.1.5-rc.1(2026-09-14 立项)",
"status": "🔄 进行中(阶段 1 通过 ",
"date": "2026-09-14",
"chars": 8637,
"lines": 182,
"refs": 1,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "> 目标版本 = **`0.1.5-rc.1`**(npm `latest`;用户材料里插件 peer 也是 `^0.1.5-rc.1`,三方自洽)。"
},
{
"path": "04-调整方案/91-模型设置页复刻官方交互-卡片行与两步新增.md",
"num": "91",
"title": "91-模型设置页复刻官方交互——卡片行 + 两步新增(2026-09-14 落地)",
"status": "✅ 已上线(`busines",
"date": "2026-09-14",
"chars": 6983,
"lines": 134,
"refs": 2,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "ui",
"tldr": "> **换行不是\"窄了\",是版式选错了** —— 原「我已添加的厂家」是 **4 列表格**(`pa-tbl`,列宽 auto):"
},
{
"path": "04-调整方案/92-官方推荐插件列表按dsh版本过滤.md",
"num": "92",
"title": "92-官方推荐插件列表按 dsh 版本过滤(2026-09-14 落地)",
"status": "✅ 已上线",
"date": "2026-09-14",
"chars": 6694,
"lines": 122,
"refs": 1,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": "> 官方目录(`awesome-dsh-plugin.com/plugins.json`)**不带 dsh 版本字段** ⇒ 只能**逐包去 npm 查声明**"
},
{
"path": "04-调整方案/93-兼容判定收口-伞包版本与prerelease语义.md",
"num": "93",
"title": "93-兼容判定收口:伞包版本 + prerelease 语义(2026-09-14 落地)",
"status": "✅ 已上线(平台后端已构建重",
"date": "2026-09-14",
"chars": 5892,
"lines": 132,
"refs": 1,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "> ① **\"单测长期红\"根本不是代码问题** —— 本机 `48 通过 / 0 失败`,是**服务器源码落后于 git**"
},
{
"path": "04-调整方案/94-实例内存口径定案.md",
"num": "94",
"title": "94-实例内存口径定案(2026-09-14 落地)",
"status": "✅ 已上线(平台后端已 `n",
"date": "2026-09-14",
"chars": 3433,
"lines": 72,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> 把两侧常量(编排器 `instanceMemMb()` ↔ 插件客户端 `MEM_*`)**收成一份事实**,按用户裁定落地:"
},
{
"path": "04-调整方案/95-HTML外壳缓存治理-修Failed-to-load-plugins根因.md",
"num": "95",
"title": "95-HTML 外壳缓存治理:修「Failed to load plugins」的根因(2026-09-14 事故复盘)",
"status": "✅ 已上线",
"date": "2026-09-14",
"chars": 5466,
"lines": 135,
"refs": 6,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "04-调整方案/96-实例配额与插件开关解耦.md",
"num": "96",
"title": "96-实例内存:与插件开关解耦,改为「基础 MIN → 最多 MAX」(2026-09-14 落地)",
"status": "✅ 已上线(平台后端已重建重",
"date": "2026-09-14",
"chars": 4416,
"lines": 82,
"refs": 3,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "> 平台侧 = cgroup **两个参数**:`MemoryHigh = MIN = 448 MiB`(**基础/软限**,超过即回收·限速)"
},
{
"path": "04-调整方案/97-plugins合并脚本补ETag与304短路.md",
"num": "97",
"title": "97-`/plugins/` 合并脚本补 ETag + 304 短路(2026-09-14 落地)",
"status": "✅ 已上线",
"date": "2026-09-14",
"chars": 3035,
"lines": 76,
"refs": 6,
"refsCurrent": 0,
"tier": "warm",
"layer": "L5",
"domain": "platform",
"tldr": "> dsh 官方把全部客户端插件拼成**一条 11 MB 的脚本**(`@deepseek-ai/dsh-client-modules` 的 combo URL"
},
{
"path": "04-调整方案/98-治本-陈旧dsh-auth-cookie回写清理.md",
"num": "98",
"title": "98-治本:陈旧 `dsh-auth-*` cookie 回写清理(2026-09-14 落地)",
"status": "✅ 已上线",
"date": "2026-09-14",
"chars": 2944,
"lines": 79,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "platform",
"tldr": "> dsh **每次实例 (重)启动都换** `dsh-auth-<随机后缀>` 的 **cookie 名**;平台此前只在**转发给实例时**"
},
{
"path": "04-调整方案/99-会话自决失效根因与Stop钩子补强.md",
"num": "99",
"title": "99-「会话自行判断继续」失效的根因与机制补强(Stop 钩子)",
"status": "🔄 已落地待生效(钩子已装",
"date": "2026-09-15",
"chars": 4896,
"lines": 106,
"refs": 0,
"refsCurrent": 0,
"tier": "cold",
"layer": "L5",
"domain": "method",
"tldr": "> 1. **根因 = 拦截点错位**(不是\"AI 不听话\"):既有「提问闸门」hook 的 matcher 是 `^AskUserQuestion$`,只能拦**工具调用**;实测本工作区宿主日志 `tool=AskUserQuestio"
},
{
"path": "04-调整方案/README.md",
"num": null,
"title": "04-调整方案 — 档案清单见根 README",
"status": "?",
"date": "",
"chars": 211,
"lines": 7,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "06-工作台UI规范.md",
"num": null,
"title": "短视频工作台 UI 规范",
"status": "?",
"date": "",
"chars": 13260,
"lines": 332,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L2",
"domain": "ui",
"tldr": ""
},
{
"path": "07-实例UI分区登记表.md",
"num": null,
"title": "07 · 实例 UI 分区登记表(settings.section 谁提供、源码在哪、能不能改)",
"status": "✅ 表格为现行值",
"date": "2026-09-15",
"chars": 4215,
"lines": 85,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "?",
"domain": "ui",
"tldr": ""
},
{
"path": "BRIEF.md",
"num": null,
"title": "BRIEF — 现状卡(**AI / 人 首读这一份**)",
"status": "?",
"date": "",
"chars": 5015,
"lines": 71,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L1",
"domain": "platform",
"tldr": ""
},
{
"path": "CODEBUDDY.md",
"num": null,
"title": "文档库使用约定(**子目录指令 —— 只在读写本目录文件时加载**)",
"status": "?",
"date": "",
"chars": 6349,
"lines": 110,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L2",
"domain": "method",
"tldr": ""
},
{
"path": "DEPLOY-本部署.md",
"num": null,
"title": "DEPLOY — 本部署说明(alotbuy.com / 47.77.182.89)",
"status": "?",
"date": "",
"chars": 4415,
"lines": 102,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L1",
"domain": "platform",
"tldr": ""
},
{
"path": "INDEX.md",
"num": null,
"title": "dsh 平台文档导航(INDEX)",
"status": "?",
"date": "",
"chars": 19438,
"lines": 840,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L4",
"domain": "platform",
"tldr": ""
},
{
"path": "README.md",
"num": null,
"title": "dsh 多租户平台 — 改造方案文档库",
"status": "?",
"date": "",
"chars": 10098,
"lines": 101,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L2",
"domain": "platform",
"tldr": ""
},
{
"path": "archive/dsh-improvement-plan-20260909-full.md",
"num": null,
"title": "dsh(DeepSeek Harness)多用户部署与配置改造方案",
"status": "?",
"date": "",
"chars": 23530,
"lines": 556,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T01-档案16阶段3-4-实例内我的技能.md",
"num": null,
"title": "T01 · 档案 16 阶段 3/4 —— 实例内「我的技能」",
"status": "✅ 已完成(2026-09-",
"date": "2026-09-11",
"chars": 9522,
"lines": 153,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T02-文档库收尾-编号消歧与INDEX瘦身.md",
"num": null,
"title": "T02 · 文档库收尾 —— 编号消歧(37/38)+ INDEX 瘦身与事实校正",
"status": "⏳ 待执行",
"date": "2026-09-11",
"chars": 9542,
"lines": 166,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T03-plugin_package整合为单插件并投放.md",
"num": null,
"title": "T03 · 把 `plugin_package` 7 个自研插件整合为 1 个功能插件并投放",
"status": "✅ 已完成并归档",
"date": "2026-09-12",
"chars": 25160,
"lines": 346,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T04-并发治理落地-commit常态化与服务器侧锁.md",
"num": null,
"title": "T04 · 并发治理落地(A 组三项:commit 常态化 / 服务器侧锁 / 权限统一)",
"status": "✅ 已完成(2026-09-",
"date": "2026-09-12",
"chars": 9598,
"lines": 175,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "ops",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T05-插件兼容性预检.md",
"num": null,
"title": "T05 · 插件兼容性预检(导入 / 上传即判定)",
"status": "✅ 已完成并归档(2026-",
"date": "2026-09-12",
"chars": 6245,
"lines": 138,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T06-模型设置页-多厂家条目可开关.md",
"num": null,
"title": "T06 · 平台自建「模型设置」页 —— 多厂家条目自助配置(各自开关、可同时启用)",
"status": "✅ 已完成并归档(后端已部署",
"date": "2026-09-13",
"chars": 5103,
"lines": 80,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "platform",
"tldr": ""
},
{
"path": "archive/交接单-已完成/T07-内置dsh安装路径探测.md",
"num": null,
"title": "T07 · 内置 dsh 安装路径按序探测(修 P1 静默失效)",
"status": "✅ 已完成并归档(源仓 `c",
"date": "2026-09-14",
"chars": 2993,
"lines": 72,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "external",
"tldr": ""
},
{
"path": "archive/工作区草案/VoxEMW全云API化接入dsh修订方案_20260909.md",
"num": null,
"title": "VoxEMW 全云 API 化:接入 dsh 修订方案(零自托管模型)",
"status": "?",
"date": "",
"chars": 10332,
"lines": 223,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "method",
"tldr": ""
},
{
"path": "archive/工作区草案/VoxEMW接入dsh调研与落地方案_20260909.md",
"num": null,
"title": "VoxEMW 接入 dsh:全面调研与落地方案",
"status": "?",
"date": "",
"chars": 17630,
"lines": 354,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "archive/工作区草案/插件管理面_调整方案草案_20260910.md",
"num": null,
"title": "13-插件管理面(修订 v5:入库审查门禁 + 用户自选启用,Step 0 核查结论已回填)",
"status": "方案草案 v5,待用户拍板 ",
"date": "",
"chars": 12568,
"lines": 206,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L5",
"domain": "plugin",
"tldr": ""
},
{
"path": "skills/dsh-change-workflow/SKILL.md",
"num": null,
"title": "dsh-change-workflow — dsh 平台改造工作流",
"status": "?",
"date": "",
"chars": 70347,
"lines": 1039,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "platform",
"tldr": ""
},
{
"path": "skills/dsh-decision-method/SKILL.md",
"num": null,
"title": "dsh-decision-method — 平台改造的思考与决策方法",
"status": "?",
"date": "",
"chars": 14128,
"lines": 335,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": "结论 / 关键 / 状态(紧贴头部,3 行内)"
},
{
"path": "skills/dsh-decision-method/references/素材库-A-AI推理.md",
"num": null,
"title": "素材库 · AI 的有效决策(A1–A22)",
"status": "?",
"date": "",
"chars": 9813,
"lines": 166,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-decision-method/references/素材库-U-用户决策.md",
"num": null,
"title": "素材库 · 用户的有效决策(U1–U24)",
"status": "?",
"date": "",
"chars": 11190,
"lines": 195,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-decision-method/references/素材库-反例-X.md",
"num": null,
"title": "反例库 · 被驳回 / 被纠正的决策(X1–X13)",
"status": "?",
"date": "",
"chars": 2704,
"lines": 35,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-env-bootstrap/SKILL.md",
"num": null,
"title": "dsh-env-bootstrap — 环境引导(常驻规则的可移植化)",
"status": "?",
"date": "",
"chars": 2074,
"lines": 55,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-env-bootstrap/references/常驻规则-快照.md",
"num": null,
"title": "常驻规则 · 可移植快照(由 `scripts/resident-rules.py --snapshot` 生成,勿手改)",
"status": "?",
"date": "",
"chars": 11210,
"lines": 134,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-feature-first/SKILL.md",
"num": null,
"title": "dsh-feature-first — 功能优先协作协议",
"status": "?",
"date": "",
"chars": 14920,
"lines": 361,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-instance-diagnose/SKILL.md",
"num": null,
"title": "dsh-instance-diagnose — DSH 实例故障诊断",
"status": "?",
"date": "",
"chars": 10623,
"lines": 225,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "platform",
"tldr": ""
},
{
"path": "skills/dsh-knowledge-upkeep/SKILL.md",
"num": null,
"title": "dsh-knowledge-upkeep — 知识库维护方法",
"status": "?",
"date": "",
"chars": 4305,
"lines": 134,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "method",
"tldr": ""
},
{
"path": "skills/dsh-opensource-release/SKILL.md",
"num": null,
"title": "dsh-opensource-release — 开源导出与版本迭代",
"status": "?",
"date": "",
"chars": 36866,
"lines": 529,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "external",
"tldr": ""
},
{
"path": "skills/dsh-plugin-diagnose/SKILL.md",
"num": null,
"title": "DSH 业务插件故障诊断",
"status": "?",
"date": "",
"chars": 5919,
"lines": 121,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L3",
"domain": "plugin",
"tldr": ""
},
{
"path": "交接单/README.md",
"num": null,
"title": "交接单(规划会话 → 执行会话)",
"status": "✅ 启用",
"date": "2026-09-11",
"chars": 14100,
"lines": 153,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L4",
"domain": "method",
"tldr": ""
},
{
"path": "交接单/T08-集群化落地-兼容单例模式.md",
"num": null,
"title": "T08 · 集群化落地(Manager / Worker)—— **全程兼容单例模式**",
"status": "?",
"date": "",
"chars": 38295,
"lines": 741,
"refs": 0,
"refsCurrent": 0,
"tier": "doc",
"layer": "L4",
"domain": "platform",
"tldr": ""
}
]
}