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
1 parent cb184145e9
commit 4e3a1a4a13
@@ -1,27 +1,28 @@
 {
 "generatedFrom": "scripts/docs-manifest.py",
 "counts": {
-  "files": 138,
-  "chars": 1129912
+  "files": 148,
+  "chars": 1222542
 },
 "tiers": {
  "hot": 7,
  "cur": 27,
-  "warm": 56,
-  "cold": 12,
+  "warm": 57,
+  "cold": 21,
  "doc": 36
 },
 "domains": {
-  "platform": 54,
-  "method": 28,
+  "platform": 60,
+  "method": 29,
  "ui": 14,
  "plugin": 27,
-  "ops": 10,
+  "ops": 11,
+  "?": 2,
  "external": 5
 },
 "layers": {
  "L0": 1,
-  "L5": 115,
+  "L5": 125,
  "L4": 4,
  "L2": 3,
  "?": 1,
@@ -65,8 +66,8 @@
   "title": "03 路线图与待办",
   "status": "?",
   "date": "",
-   "chars": 18493,
-   "lines": 127,
+   "chars": 18981,
+   "lines": 128,
   "refs": 0,
   "refsCurrent": 0,
   "tier": "doc",
@@ -217,7 +218,7 @@
   "date": "04-10",
   "chars": 6261,
   "lines": 129,
-   "refs": 24,
+   "refs": 48,
   "refsCurrent": 1,
   "tier": "cur",
   "layer": "L5",
@@ -269,6 +270,111 @@
   "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",
@@ -277,13 +383,58 @@
   "date": "04-11",
   "chars": 7789,
   "lines": 176,
-   "refs": 15,
+   "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",
@@ -1282,7 +1433,7 @@
   "date": "2026-09-13",
   "chars": 5969,
   "lines": 111,
-   "refs": 9,
+   "refs": 10,
   "refsCurrent": 0,
   "tier": "warm",
   "layer": "L5",
@@ -1387,9 +1538,9 @@
   "date": "2026-09-13",
   "chars": 12153,
   "lines": 236,
-   "refs": 0,
+   "refs": 2,
   "refsCurrent": 0,
-   "tier": "cold",
+   "tier": "warm",
   "layer": "L5",
   "domain": "platform",
   "tldr": "① 原先平台是「**统一 KEY**」——`resolveApiKey()` **显式忽略入参 userId**，不管谁 spawn 都注入 admin 那一把；② 本轮改为**两层**：**用户自己的 key 优先，没有才回落管理员的「平"
@@ -1567,7 +1718,7 @@
   "date": "2026-09-14",
   "chars": 3035,
   "lines": 76,
-   "refs": 1,
+   "refs": 6,
   "refsCurrent": 0,
   "tier": "warm",
   "layer": "L5",
@@ -1700,8 +1851,8 @@
   "title": "dsh 平台文档导航（INDEX）",
   "status": "?",
   "date": "",
-   "chars": 16649,
-   "lines": 830,
+   "chars": 19438,
+   "lines": 840,
   "refs": 0,
   "refsCurrent": 0,
   "tier": "doc",
@@ -1910,8 +2061,8 @@
   "title": "dsh-decision-method — 平台改造的思考与决策方法",
   "status": "?",
   "date": "",
-   "chars": 12562,
-   "lines": 306,
+   "chars": 14128,
+   "lines": 335,
   "refs": 0,
   "refsCurrent": 0,
   "tier": "doc",
@@ -2000,8 +2151,8 @@
   "title": "dsh-feature-first — 功能优先协作协议",
   "status": "?",
   "date": "",
-   "chars": 13242,
-   "lines": 353,
+   "chars": 14920,
+   "lines": 361,
   "refs": 0,
   "refsCurrent": 0,
   "tier": "doc",