@bruc3van/dsh-doctor 0.5.4 → 0.5.6

package/README.en.md

@@ -12,7 +12,7 @@ DSH 0.1.1 → DSH 0.1.2
 
 The project also diagnoses DSH profiles and installed plugins, checks for compatible versions, and performs safety checks before quarantine or removal.
 
-> This is a community-maintained third-party project, not an official DeepSeek project. The current catalog uses `dsh-v0.1.1-rc.2` and `dsh-v0.1.2-alpha.2` as the reference points for the 0.1.1-to-0.1.2 changes. An agent should still check actual differences when a plugin uses another patch or prerelease.
+> This is a community-maintained third-party project, not an official DeepSeek project. The migration scope remains DSH 0.1.1 → 0.1.2; the current known-latest catalog exactly covers `dsh-v0.1.1-rc.2` through `dsh-v0.1.2-alpha.3`. The older alpha.2 catalog remains as historical rules. When a newer 0.1.2 prerelease appears, inspect its delta before deliberately updating the catalog and skill.
 
 ## Upgrade a plugin with the skill
 
@@ -99,11 +99,11 @@ Source analysis uses the TypeScript AST and is cross-checked against the manifes
 ## Safety
 
 - `diagnose`, `migrate analyze`, and static verification are read-only and do not load or execute the inspected plugin;
-- `migrate apply` requires `--safe`; without `--yes`, it only previews changes;
+- `migrate apply` requires `--safe --plan-file`; preview only creates a new plan outside the plugin root, never overwrites an existing file, and persists the complete analysis plus every input-file hash; `--yes` applies only that same reviewed plan;
 - only `exact` migrations are auto-edited; semantic changes are not guessed;
 - SHA-256 is checked before writing, so a file changed after preview is rejected;
 - existing files receive timestamped backups and are replaced atomically through a temporary file;
-- build and runtime verification execute plugin scripts and therefore require explicit `--yes`;
+- build and runtime verification synchronize dependencies and execute plugin scripts, so they require explicit `--yes --install`; install lifecycle scripts are disabled and lockfile plus resolved-version evidence is recorded;
 - runtime verification uses a temporary `DSH_HOME`, not the normal `~/.dsh`;
 - JSON, baselines, and recovery snapshots redact plugin configuration and common secret/token/password/key fields;
 - global CLI installation, persistent quarantine, plugin removal, and publishing are never performed automatically by the skill.
@@ -115,7 +115,7 @@ Node.js `^22.19.0` or `>=24.0.0` is required.
 First confirm that the CLI contains the required migration:
 
 ```sh
-npx --yes --package=@bruc3van/dsh-doctor@0.5.4 \
+npm exec --yes --package=@bruc3van/dsh-doctor@<selected-version> -- \
   dsh-doctor migrations list
 ```
 
@@ -124,43 +124,45 @@ npx --yes --package=@bruc3van/dsh-doctor@0.5.4 \
 ```sh
 dsh-doctor migrate analyze /path/to/plugin \
   --from dsh-v0.1.1-rc.2 \
-  --to dsh-v0.1.2-alpha.2 \
+  --to dsh-v0.1.2-alpha.3 \
   --harness-root /path/to/deepseek-harness \
   --json
 ```
 
-Analysis checks source, dependencies, manifest, client graph, patch targets, and existing build output without executing plugin code.
+Analysis checks source, dependencies, manifest, client graph, patch targets, and existing build output without executing plugin code. `--from`/`--to` select the exact catalog that supplies API rules. Alpha.3 is the current default, so it needs no separate `--target-version`. If a newer 0.1.2 build is explicitly targeted before the catalog is updated, inspect the source delta from alpha.3 first, then use `--target-version` to control dependency ranges, safe-plan pins, and the runtime version check. The report keeps the catalog and actual targets separate.
 
 ### 2. Apply
 
 ```sh
 # Preview
 dsh-doctor migrate apply /path/to/plugin --safe \
+  --plan-file /temporary/path/reviewed-migration-plan.json \
   --harness-root /path/to/deepseek-harness --json
 
 # Write after confirmation
 dsh-doctor migrate apply /path/to/plugin --safe --yes \
+  --plan-file /temporary/path/reviewed-migration-plan.json \
   --harness-root /path/to/deepseek-harness --json
 ```
 
-Apply can split mixed imports, move exact symbols, leave semantic symbols in place, and update development dependencies when the change is known. Every changed file receives a backup.
+The plan must stay outside the plugin root so it is not analyzed as plugin input. Apply checks the plan digest, every analyzed input, and each edit's before/after hashes; source, manifest, or other analyzed-input changes require a new reviewed plan. Deterministic dependency edits use catalog-owned Client/Host and peer/dev policies instead of inheriting the removed package's dependency section. Every changed file receives a backup.
 
 ### 3. Verify
 
 ```sh
 dsh-doctor migrate verify /path/to/plugin --level static \
   --harness-root /path/to/deepseek-harness --json
-dsh-doctor migrate verify /path/to/plugin --level build --yes \
-  --harness-root /path/to/deepseek-harness --json
-dsh-doctor migrate verify /path/to/plugin --level runtime --yes \
+dsh-doctor migrate verify /path/to/plugin --level build --yes --install \
   --harness-root /path/to/deepseek-harness --json
+dsh-doctor migrate verify /path/to/plugin --level runtime --yes --install \
+  --dsh-command /path/to/dsh --json
 ```
 
 | Level | What it checks |
 |---|---|
 | `static` | Rechecks source, manifest, client graph, patches, and artifacts |
-| `build` | Runs the plugin's existing build/test scripts and scans the output again |
-| `runtime` | Packs the real tarball and checks the target DSH version, installed package, bundle, and effective configuration in a temporary profile |
+| `build` | Synchronizes and verifies target dependencies and the lockfile, then runs build/test scripts and scans output again |
+| `runtime` | After dependency and build gates, packs the real tarball and checks target DSH, installed package, bundle, and effective configuration in a temporary profile |
 
 Verification states are:
 

package/README.md

@@ -12,7 +12,7 @@ DSH 0.1.1 → DSH 0.1.2
 
 项目同时提供 DSH profile 和插件的诊断、兼容版本检查、隔离与删除前检查。
 
-> 这是社区维护的第三方工具，不属于 DeepSeek 官方项目。当前 catalog 以 `dsh-v0.1.1-rc.2` 和 `dsh-v0.1.2-alpha.2` 为基准记录 0.1.1 到 0.1.2 的变化；插件使用其他 patch 或预发布版本时，Agent 仍需核对实际差异。
+> 这是社区维护的第三方工具，不属于 DeepSeek 官方项目。工具的迁移范围保持为 DSH 0.1.1 → 0.1.2；当前已知最新版 catalog 精确覆盖 `dsh-v0.1.1-rc.2` 到 `dsh-v0.1.2-alpha.3`。旧 alpha.2 catalog 作为历史规则保留；出现更新的 0.1.2 预发布版本时，需要先核对增量，再明确更新 catalog 和 Skill。
 
 ## 使用 Skill 升级插件
 
@@ -99,11 +99,11 @@ Migration catalog 保存 source/target tag 和 Git commit，并记录 package、
 ## 安全性
 
 - `diagnose`、`migrate analyze` 和静态验证只读，不加载或执行待检查插件；
-- `migrate apply` 必须带 `--safe`，没有 `--yes` 时只展示将要修改的内容；
+- `migrate apply` 必须带 `--safe --plan-file`；预览只会新建插件目录外的 plan，不会覆盖已有文件，并把完整分析和所有输入文件哈希固化下来；`--yes` 只应用同一个已审阅 plan；
 - 只有 `exact` 迁移会自动改代码，语义变化不会自动猜测；
 - 写入前检查文件 SHA-256，预览后文件发生变化会拒绝写入；
 - 修改已有文件前创建时间戳备份，并使用临时文件原子替换；
-- build 和 runtime 会执行插件脚本，因此必须显式使用 `--yes`；
+- build 和 runtime 会同步依赖并执行插件脚本，因此必须显式使用 `--yes --install`；依赖安装禁用 lifecycle scripts，并记录 lockfile 和实际解析版本证据；
 - runtime 使用临时 `DSH_HOME`，不会安装到正常的 `~/.dsh`；
 - JSON、baseline 和恢复快照会脱敏插件配置和常见 secret/token/password/key 字段；
 - 全局 CLI 安装、持久隔离、删除插件和发布都不会由 Skill 自动执行。
@@ -115,7 +115,7 @@ Migration catalog 保存 source/target tag 和 Git commit，并记录 package、
 先确认 CLI 包含需要的迁移：
 
 ```sh
-npx --yes --package=@bruc3van/dsh-doctor@0.5.4 \
+npm exec --yes --package=@bruc3van/dsh-doctor@<selected-version> -- \
   dsh-doctor migrations list
 ```
 
@@ -124,43 +124,45 @@ npx --yes --package=@bruc3van/dsh-doctor@0.5.4 \
 ```sh
 dsh-doctor migrate analyze /path/to/plugin \
   --from dsh-v0.1.1-rc.2 \
-  --to dsh-v0.1.2-alpha.2 \
+  --to dsh-v0.1.2-alpha.3 \
   --harness-root /path/to/deepseek-harness \
   --json
 ```
 
-分析会检查源码、依赖、manifest、client graph、patch target 和已有构建产物，不执行插件代码。
+分析会检查源码、依赖、manifest、client graph、patch target 和已有构建产物，不执行插件代码。`--from`/`--to` 选择提供 API 规则的精确 catalog。当前默认目标就是 alpha.3，无需额外指定 `--target-version`；如果在 catalog 更新前明确迁移到更新的 0.1.2 版本，必须先调查 alpha.3 到该版本的源码差异，再用 `--target-version` 单独控制依赖范围、safe plan pin 和 runtime 版本核验。报告会保留 catalog 与实际目标两个值。
 
 ### 2. 修改
 
 ```sh
 # 预览
 dsh-doctor migrate apply /path/to/plugin --safe \
+  --plan-file /temporary/path/reviewed-migration-plan.json \
   --harness-root /path/to/deepseek-harness --json
 
 # 确认后写入
 dsh-doctor migrate apply /path/to/plugin --safe --yes \
+  --plan-file /temporary/path/reviewed-migration-plan.json \
   --harness-root /path/to/deepseek-harness --json
 ```
 
-Apply 可以拆分混合 import、移动精确 symbol、保留语义 symbol，并更新确定可以调整的开发依赖。每个被修改的文件都会保留备份。
+Plan 必须放在插件目录外，避免被当成插件输入。Apply 会核对 plan digest、完整分析输入和每个修改的 before/after hash；源码、manifest 或其他分析输入在预览后变化时必须重新生成并审阅 plan。确定性依赖改写使用 catalog 明确的 Client/Host 与 peer/dev 策略，不再沿用旧包所在的 dependency section。每个被修改的文件都会保留备份。
 
 ### 3. 验证
 
 ```sh
 dsh-doctor migrate verify /path/to/plugin --level static \
   --harness-root /path/to/deepseek-harness --json
-dsh-doctor migrate verify /path/to/plugin --level build --yes \
-  --harness-root /path/to/deepseek-harness --json
-dsh-doctor migrate verify /path/to/plugin --level runtime --yes \
+dsh-doctor migrate verify /path/to/plugin --level build --yes --install \
   --harness-root /path/to/deepseek-harness --json
+dsh-doctor migrate verify /path/to/plugin --level runtime --yes --install \
+  --dsh-command /path/to/dsh --json
 ```
 
 | 级别 | 验证内容 |
 |---|---|
 | `static` | 再次检查源码、manifest、client graph、patch 和产物 |
-| `build` | 运行插件已有的构建与测试脚本，并在构建后重新扫描产物 |
-| `runtime` | 打真实 tarball，在临时 profile 中验证目标 DSH 版本、安装包、bundle 和生效配置 |
+| `build` | 先同步并核验目标依赖和 lockfile，再运行已有构建/测试脚本并重新扫描产物 |
+| `runtime` | 完成依赖与构建门后，打真实 tarball，在临时 profile 中验证目标 DSH、安装包、bundle 和生效配置 |
 
 验证状态依次是：
 

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.2/packages.json

@@ -38,9 +38,18 @@
     "@deepseek-ai/dsh-win32-process"
   ],
   "targetVersions": {
-    "@deepseek-ai/cordis": "4.0.2",
-    "@deepseek-ai/dsh-client-store": "0.1.2-alpha.2",
-    "@deepseek-ai/dsh-session": "0.1.2-alpha.2"
+    "@deepseek-ai/cordis": "4.0.2"
+  },
+  "dependencyPolicies": {
+    "@deepseek-ai/cordis": {
+      "client": ["peerDependencies", "devDependencies"]
+    },
+    "@deepseek-ai/dsh-client-store": {
+      "client": ["devDependencies"]
+    },
+    "@deepseek-ai/dsh-session": {
+      "client": ["devDependencies"]
+    }
   },
   "semanticReplacements": {
     "@deepseek-ai/dsh-client-runtime": [

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.2/symbols.json

@@ -1,5 +1,13 @@
 {
   "modules": {
+    "@deepseek-ai/dsh-settings": {
+      "settingsNamespace": {
+        "toModule": "@deepseek-ai/dsh-settings",
+        "toSymbol": "SettingsProvider.register",
+        "confidence": "semantic",
+        "reason": "The settingsNamespace factory was removed. Inject the settings Service and register the namespace through ctx.settings.register(name, schema)."
+      }
+    },
     "@deepseek-ai/dsh-client-runtime/client": {
       "ClientContext": {
         "toModule": "@deepseek-ai/cordis",

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3/behavior.md

@@ -0,0 +1,14 @@
+# DSH 0.1.1-rc.2 to 0.1.2-alpha.3 behavior migration
+
+The old Client Runtime was split by ownership. There is no aggregate replacement package.
+
+- Session control, list state, commands, projections, queue and event windows belong to `api-session-controller/client`.
+- Workspace state and commands belong to `api-workspace-controller/client`; navigation policy belongs to `ui-workspace`.
+- Conversation assembly belongs to `ui-conversation`; Chat and Trajectory own their respective projections.
+- Approval and Question own their pending objects; `ui-session` only aggregates domain publications.
+- The store engine belongs to `client-store`; React hook synthesis belongs to the renderer.
+- The Host API Proxy was removed. Unary browser operations live on their natural Remote service owners.
+- The demo-only `dsh-agent-spine-demo` package and the SQLite session persistence package were removed by alpha.3; neither has a catalog-confirmed drop-in replacement.
+- Alpha.3 adds the `dsh-session-turn-outline` package and extends session submission/load-through APIs. These additions do not justify mechanical rewrites of existing plugin behavior.
+
+An import move is safe only when the catalog marks it `exact`. A `semantic` mapping identifies the new owner but still requires the plugin developer to rewrite behavior and verify the real lifecycle.

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3/config-rules.json

@@ -0,0 +1,36 @@
+{
+  "platformModules": [
+    "react",
+    "react/jsx-runtime",
+    "react-dom",
+    "react-dom/client",
+    "@deepseek-ai/cordis",
+    "@deepseek-ai/dsh-client-store",
+    "@deepseek-ai/dsh-client-ui-slots",
+    "@deepseek-ai/dsh-client-ui-primitives"
+  ],
+  "profilePatchPaths": {
+    "web": [
+      "packages/bundle/base/cordis.patch.yml",
+      "packages/bundle/web-app/cordis.patch.yml"
+    ]
+  },
+  "rules": [
+    {
+      "id": "client-inject-is-informational",
+      "note": "dsh.client.inject lists package dependency edges; Cordis service inject controls activation."
+    },
+    {
+      "id": "baseline-external-is-implicit",
+      "note": "Platform modules are implicit and must not be repeated in dsh.client.external."
+    },
+    {
+      "id": "feature-values-use-services-or-slots",
+      "note": "Feature plugins must not use dsh.client.external as a feature-to-feature value dependency mechanism."
+    },
+    {
+      "id": "client-export-required",
+      "note": "A web dsh.client declaration requires a published exports[\"./client\"] artifact."
+    }
+  ]
+}

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3/manifest.json

@@ -0,0 +1,19 @@
+{
+  "schemaVersion": 1,
+  "id": "dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3",
+  "from": {
+    "ref": "dsh-v0.1.1-rc.2",
+    "commit": "b150a551b8d465e31e418e1b2eaf5e79bbb7d28e"
+  },
+  "to": {
+    "ref": "dsh-v0.1.2-alpha.3",
+    "commit": "dd6322d604e00eec1ba5e0c8541159906a21094a",
+    "version": "0.1.2-alpha.3"
+  },
+  "description": "DeepSeek Harness 0.1.1-rc.2 to 0.1.2-alpha.3 plugin migration",
+  "references": {
+    "ownership": ".agents/notes/implemented/architecture/2026-08-20-client-session-conversation-ownership.md",
+    "remoteMigration": ".agents/notes/implemented/architecture/2026-08-10-unary-apiproxy-remote-migration.md",
+    "clientRules": "packages/client/AGENTS.md"
+  }
+}

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3/packages.json

@@ -0,0 +1,74 @@
+{
+  "removed": [
+    "@deepseek-ai/dsh-acp-demo",
+    "@deepseek-ai/dsh-acp-snapshot",
+    "@deepseek-ai/dsh-agent-spine-demo",
+    "@deepseek-ai/dsh-client-runtime",
+    "@deepseek-ai/dsh-host-apiproxy",
+    "@deepseek-ai/dsh-sdk-jsonrpc-demo",
+    "@deepseek-ai/dsh-session-persistence-sqlite"
+  ],
+  "added": [
+    "@deepseek-ai/dsh-acp-app",
+    "@deepseek-ai/dsh-api-session-controller",
+    "@deepseek-ai/dsh-api-settings-controller",
+    "@deepseek-ai/dsh-api-workspace-controller",
+    "@deepseek-ai/dsh-client-store",
+    "@deepseek-ai/dsh-client-ui-approval",
+    "@deepseek-ai/dsh-client-ui-chat",
+    "@deepseek-ai/dsh-client-ui-schedule",
+    "@deepseek-ai/dsh-client-ui-session",
+    "@deepseek-ai/dsh-deepseek-llm-api-extensions",
+    "@deepseek-ai/dsh-deque",
+    "@deepseek-ai/dsh-experimental-agent-team-profile",
+    "@deepseek-ai/dsh-experimental-agent-team-web-profile",
+    "@deepseek-ai/dsh-experimental-client-ui-agent-team",
+    "@deepseek-ai/dsh-experimental-inspector",
+    "@deepseek-ai/dsh-experimental-webworker-packer",
+    "@deepseek-ai/dsh-experimental-webworker-runtime",
+    "@deepseek-ai/dsh-plugin-package-inventory-deepseek",
+    "@deepseek-ai/dsh-sdk-app",
+    "@deepseek-ai/dsh-sdk-minimal",
+    "@deepseek-ai/dsh-session-log-deepseek",
+    "@deepseek-ai/dsh-session-snapshot",
+    "@deepseek-ai/dsh-session-turn-outline",
+    "@deepseek-ai/dsh-util-crypto",
+    "@deepseek-ai/dsh-util-time",
+    "@deepseek-ai/dsh-util-values",
+    "@deepseek-ai/dsh-util-workspace-path",
+    "@deepseek-ai/dsh-webhook",
+    "@deepseek-ai/dsh-webhook-github",
+    "@deepseek-ai/dsh-win32-process"
+  ],
+  "targetVersions": {
+    "@deepseek-ai/cordis": "4.0.2"
+  },
+  "dependencyPolicies": {
+    "@deepseek-ai/cordis": {
+      "client": ["peerDependencies", "devDependencies"]
+    },
+    "@deepseek-ai/dsh-client-store": {
+      "client": ["devDependencies"]
+    },
+    "@deepseek-ai/dsh-session": {
+      "client": ["devDependencies"]
+    }
+  },
+  "semanticReplacements": {
+    "@deepseek-ai/dsh-client-runtime": [
+      "@deepseek-ai/dsh-api-session-controller",
+      "@deepseek-ai/dsh-api-workspace-controller",
+      "@deepseek-ai/dsh-client-store",
+      "@deepseek-ai/dsh-client-ui-session",
+      "@deepseek-ai/dsh-client-ui-conversation",
+      "@deepseek-ai/dsh-client-ui-chat",
+      "@deepseek-ai/dsh-client-ui-trajectory",
+      "@deepseek-ai/dsh-client-ui-approval",
+      "@deepseek-ai/dsh-client-ui-user-questions"
+    ],
+    "@deepseek-ai/dsh-host-apiproxy": [
+      "@deepseek-ai/dsh-api-gateway",
+      "@deepseek-ai/dsh-api-remotes"
+    ]
+  }
+}

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3/services.json

@@ -0,0 +1,28 @@
+{
+  "services": {
+    "sessions": {
+      "owner": "@deepseek-ai/dsh-api-session-controller/client",
+      "confidence": "semantic",
+      "note": "The service name survives, but Session snapshots no longer contain Conversation views or pending interactions."
+    },
+    "workspaces": {
+      "owner": "@deepseek-ai/dsh-api-workspace-controller/client",
+      "confidence": "semantic",
+      "note": "The service name survives, while cross-domain navigation belongs to ui-workspace."
+    },
+    "conversation": {
+      "owner": "@deepseek-ai/dsh-client-ui-conversation/client",
+      "confidence": "semantic",
+      "note": "Conversation assembly and input are independent of Session lifecycle snapshots."
+    },
+    "slots": {
+      "owner": "@deepseek-ai/dsh-client-ui-renderer/client",
+      "confidence": "semantic",
+      "note": "Slot declarations stay in ui-slots; runtime registration and binding belong to ui-renderer."
+    }
+  },
+  "removedHostFacade": {
+    "package": "@deepseek-ai/dsh-host-apiproxy",
+    "replacementPolicy": "Use the natural business Remote owner through generated api-remotes contributions; there is no replacement facade."
+  }
+}

package/migrations/dsh-v0.1.1-rc.2__dsh-v0.1.2-alpha.3/symbols.json

@@ -0,0 +1,134 @@
+{
+  "modules": {
+    "@deepseek-ai/dsh-settings": {
+      "settingsNamespace": {
+        "toModule": "@deepseek-ai/dsh-settings",
+        "toSymbol": "SettingsProvider.register",
+        "confidence": "semantic",
+        "reason": "The settingsNamespace factory was removed. Inject the settings Service and register the namespace through ctx.settings.register(name, schema)."
+      }
+    },
+    "@deepseek-ai/dsh-client-runtime/client": {
+      "ClientContext": {
+        "toModule": "@deepseek-ai/cordis",
+        "toSymbol": "Context",
+        "confidence": "exact",
+        "reason": "ClientContext was a type alias of Cordis Context."
+      },
+      "createSnapshotStore": {
+        "toModule": "@deepseek-ai/dsh-client-store",
+        "toSymbol": "createSnapshotStore",
+        "confidence": "exact",
+        "reason": "The React-free store engine moved to client-store."
+      },
+      "defineStore": {
+        "toModule": "@deepseek-ai/dsh-client-store",
+        "toSymbol": "defineStore",
+        "confidence": "exact",
+        "reason": "The declarative store factory moved to client-store."
+      },
+      "ObservableSnapshot": {
+        "toModule": "@deepseek-ai/dsh-client-store",
+        "toSymbol": "ObservableSnapshot",
+        "confidence": "exact",
+        "reason": "The observable store contract moved to client-store."
+      },
+      "SnapshotStore": {
+        "toModule": "@deepseek-ai/dsh-client-store",
+        "toSymbol": "SnapshotStore",
+        "confidence": "exact",
+        "reason": "The writable store contract moved to client-store."
+      },
+      "shallowEqual": {
+        "toModule": "@deepseek-ai/dsh-client-store",
+        "toSymbol": "shallowEqual",
+        "confidence": "exact",
+        "reason": "The store equality helper moved to client-store."
+      },
+      "SessionId": {
+        "toModule": "@deepseek-ai/dsh-session/types",
+        "toSymbol": "SessionId",
+        "confidence": "exact",
+        "reason": "Session identity is owned by the Session domain."
+      },
+      "ISessions": {
+        "toModule": "@deepseek-ai/dsh-api-session-controller/client",
+        "toSymbol": "ISessions",
+        "confidence": "semantic",
+        "reason": "Session ownership moved to the Session Controller and its snapshots changed."
+      },
+      "Session": {
+        "toModule": "@deepseek-ai/dsh-api-session-controller/client",
+        "toSymbol": "Session",
+        "confidence": "semantic",
+        "reason": "The Client Session object and lifecycle moved to the Session Controller."
+      },
+      "SessionBinding": {
+        "toModule": "@deepseek-ai/dsh-api-session-controller/client",
+        "toSymbol": "SessionBinding",
+        "confidence": "semantic",
+        "reason": "Session bindings are now Controller-owned lifetimes."
+      },
+      "SessionListState": {
+        "toModule": "@deepseek-ai/dsh-api-session-controller/client",
+        "toSymbol": "SessionListState",
+        "confidence": "semantic",
+        "reason": "The list state moved and no longer owns Conversation or pending-interaction facts."
+      },
+      "SessionSummary": {
+        "toModule": "@deepseek-ai/dsh-api-session-controller/client",
+        "toSymbol": "SessionSummary",
+        "confidence": "semantic",
+        "reason": "The Session summary is now a Controller-owned control snapshot."
+      },
+      "UseProjection": {
+        "toModule": "@deepseek-ai/dsh-api-session-controller/client",
+        "toSymbol": "UseProjection",
+        "confidence": "semantic",
+        "reason": "Projection sources are now exposed by Session Controller bindings and adapted by ui-session."
+      },
+      "IWorkspaces": {
+        "toModule": "@deepseek-ai/dsh-api-workspace-controller/client",
+        "toSymbol": "IWorkspaces",
+        "confidence": "semantic",
+        "reason": "Workspace ownership moved to the Workspace Controller and navigation policy moved to ui-workspace."
+      },
+      "WorkspaceId": {
+        "toModule": "@deepseek-ai/dsh-api-workspace-controller/client",
+        "toSymbol": "WorkspaceId",
+        "confidence": "semantic",
+        "reason": "Workspace identity is re-exported by the Workspace Controller."
+      },
+      "WorkspaceView": {
+        "toModule": "@deepseek-ai/dsh-api-workspace-controller/client",
+        "toSymbol": "WorkspaceView",
+        "confidence": "semantic",
+        "reason": "Workspace snapshots are Controller-owned and their shape changed."
+      },
+      "ConversationNode": {
+        "toModule": "@deepseek-ai/dsh-client-ui-conversation/client",
+        "toSymbol": "ConversationNode",
+        "confidence": "semantic",
+        "reason": "Conversation assembly moved out of Session snapshots into ui-conversation."
+      },
+      "ConversationSnapshot": {
+        "toModule": "@deepseek-ai/dsh-client-ui-conversation/client",
+        "toSymbol": "ConversationSnapshot",
+        "confidence": "semantic",
+        "reason": "Conversation is now an independent target-neutral source."
+      },
+      "PendingInteraction": {
+        "toModule": "@deepseek-ai/dsh-client-ui-session/client",
+        "toSymbol": "SessionPendingInteraction",
+        "confidence": "semantic",
+        "reason": "Approval and Question now publish domain-owned pending interactions through ui-session."
+      },
+      "PendingWait": {
+        "toModule": "@deepseek-ai/dsh-client-ui-session/client",
+        "toSymbol": "SessionPendingInteraction",
+        "confidence": "semantic",
+        "reason": "The Runtime PendingWait aggregate was removed; pending domains own their payloads."
+      }
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bruc3van/dsh-doctor",
-  "version": "0.5.4",
+  "version": "0.5.6",
   "description": "Help agents diagnose and upgrade DeepSeek Harness plugins from DSH 0.1.1 to 0.1.2",
   "license": "MIT",
   "type": "module",