tianshu-mcp 0.7.3 → 0.7.5

package/CHANGELOG.en.md

@@ -8,6 +8,88 @@ Chinese version: [CHANGELOG.md](CHANGELOG.md)
 
 ---
 
+## [0.7.5] - 2026-09-29
+
+### Fixed
+
+- **Qoder CN 0.4.2/0.4.3 support** (PR #26, contributed by jian-in): from 0.4.2 the model menu drops
+  the "default/custom" group tabs (candidates become a flat list and the model name moves to the trigger
+  text); in 0.4.3 the composer picker loses its `aria-label` and the bound-workspace container loses its
+  `title`. The selector candidate order now puts the stable marker `[data-workspace-picker-trigger]` before
+  the broad aria heuristic (otherwise it matches the sidebar "Workspace" section header and surfaces as
+  `qoder_stage_timeout: workspace-menu`); the "menu is open" check is narrowed to the search box
+  `workspaceSearch` (a generic `[role=menu][data-state=open]` can be matched by an unrelated overlay and
+  pass falsely); bound-workspace readback lists title-less container candidates and falls back to
+  `aria-label`/text. `QoderCdpClient` gains `resolveKey()`/`textKey()` for compound queries that need the
+  first matching candidate.
+- **Verify engine normalises the `cwd` drive-letter case on Windows** (same PR): a project path may be
+  registered with a lowercase drive letter (e.g. `e:/proj` in `projects.json`), and vite/vitest key their
+  module graph by path string, so `e:\proj` and `E:\proj` count as two locations, the same module appears
+  twice, and collection crashes. `runVerifyCommand` now normalises with `fs.realpathSync.native` before
+  spawning (the non-native variant returns the lowercase drive letter unchanged on Windows); when the path
+  cannot be resolved it falls back to the original value, so normalisation never blocks acceptance.
+
+## [0.7.4] - 2026-09-28
+
+### Fixed
+
+- **Project-scoped dispatch on ZCode 3.14.x always failed with `project_mismatch` (issue #24).**
+  ZCode 3.14.x removed the two DOM contracts tianshu-mcp used for **binding read-back**
+  (`data-project-path` and `data-testid^="workspace-item-"`), while `pathOf()` in
+  `src/agents/zcode/dom.ts:27` recognises nothing else — so `workspaceBinding().projectPath` was always
+  empty and `cdp.projects()` always returned `[]`, leaving the binding criterion unsatisfiable forever.
+  The failure happens **before the task brief is ever sent**, which made `autoFixRounds` inert
+  (`roundsUsed` stayed 0). The fix touches four places, all stemming from that one root cause:
+  - `selectors.ts:107` gains `projectMenuItem` (`[role="menuitemcheckbox"]`), and `projectItem` /
+    `projectPath` are now explicitly labelled as 3.11.x contracts;
+  - `workspaceBindingExpression()` in `dom.ts:38` now also returns `projectName` (the bound display name)
+    and `menuChecked` (display names of menu items with `aria-checked="true"`), treating multiple checked
+    items as ambiguity; it **never fabricates a path** — on 3.14.x `projectPath` stays an empty string, and
+    the decision layer uses that to distinguish evidence strength;
+  - `projects()` in `cdp.ts:279` falls back to harvesting the expanded menu **only when the old contracts
+    yield nothing**, and it includes the checked state and excludes "work outside a project", so the
+    3.11.x result is byte-for-byte unchanged;
+  - `matchZcodeProject()` in `project.ts:61` gains a **display-name exact-match** branch and reports
+    `matchedBy`; a new `boundProjectVerdict()` implements the layered criterion — **strict path equality
+    whenever a path is available (unchanged semantics), display name when there is no path channel** —
+    and requires the project list to be free of same-name ambiguity.
+- **Removed a fragile timing dependency**: `ensureProjectBound()` used to accept an externally supplied
+  item, which made "the menu happens to still be open" an implicit precondition. It is now an idempotent
+  self-check: read the verdict first, pass immediately when already bound, and only expand the menu and
+  click when it is not.
+- **Better failure diagnostics**: the `project_mismatch` message now carries the trigger text, the menu
+  checked state and the path read-back, so users are no longer left with a bare "read-back mismatch".
+- **On-device evidence entry point**: `scripts/probe-zcode.mjs` gains a `dom-contracts` subcommand that
+  reports hit counts for both legacy contracts, the trigger's full attributes, the menu item list and the
+  post-fix read-back — for re-checking this contract assumption against a real ZCode build.
+
+### Known limitation
+
+- The ZCode 3.14.x DOM exposes a project's **display name** but not its absolute path, so the criterion is
+  "display name + global same-name disambiguation": more than one same-name item yields
+  `project_ambiguous` (fail-closed). Disambiguation requires the menu to be expanded (that is `projects()`'
+  data source); with the menu closed only the `binding` display-name evidence is used, and a missing list
+  never negates a binding. The 3.11.x path-equality chain keeps the highest priority and is unchanged.
+
+### Tests
+
+- **14** new cases: 4 in `test/unit/zcode-dom.test.ts` (read-back contract under the missing 3.14.x
+  contracts, multi-check ambiguity, and no regression for 3.11.x), 6 in `test/unit/zcode-core.test.ts`
+  (display-name matching / same-name fail-closed / layered criterion / path priority), and 4 in
+  `test/integration/zcode-flow.test.ts` (already-bound dispatch without a stray click, switch-then-dispatch,
+  same-name ambiguity fail-closed, and a **counter-example** where missing display-name evidence still
+  fails closed with diagnostics). Full suite: **1383 passed / 12 skipped** (1395 tests, 115 files plus 3
+  real-browser files skipped by design).
+
+> **On-device verification boundary (disclosed honestly)**: this machine has **no ZCode 3.14.x**, so the fix
+> was not re-verified on hardware. The root cause (missing DOM contracts) is **deterministically reproducible
+> locally** against a `linkedom` fixture: the new cases were first written to show three failing assertions
+> (`projectName`/`menuChecked` absent, `projects()` empty, multi-check not treated as ambiguous) and then
+> driven to green. The on-device measurements reported in issue #24 (`data-project-path` 0 hits,
+> `workspace-item-` 0 hits, `menuitemcheckbox` intact) were **not independently reproduced**; the fix is
+> designed against those contracts. Maintainers with a 3.14.x environment should run
+> `npm run probe:zcode -- dom-contracts` to confirm.
+
 ## [0.7.3] - 2026-09-28
 
 ### Fixed
@@ -130,11 +212,35 @@ Chinese version: [CHANGELOG.md](CHANGELOG.md)
 - ARCHITECTURE / README / agent-profiles / adapter-matrix / SKILL / usage-examples (both languages): the status moves from "in development" to "wired", and the new `endReason` / `needsUserKind` values are added.
 - Versions: `package.json` and `src/version.generated.ts` are synced to `0.7.1` (per the `+0.0.1` rule); tag `v0.7.1` pushed and published to npm.
 
-## [Unreleased] — mcp-gui independent line
-
-> This change adds a **new independent delivery surface**. The MCP package's runtime logic (tool contracts, task
-> model, acceptance engine and all of `src/**`) is **unchanged**.
-> **The MCP package version stays at `0.7.0` (not yet released)**; the GUI evolves independently with its own version
+## [0.1.0] — 2026-09-29 — mcp-gui independent line
+
+> This is the **first stable release** of the GUI's independent version line (going stable + update log panel).
+> The MCP package's runtime logic (tool contracts, task model, acceptance engine and all of `src/**`) is
+> **unchanged**, and the package version stays at `0.7.4`; the GUI evolves independently with its own version
+> numbers and its own tags (`gui-v*`).
+>
+> **Three categories of change relative to `0.1.0-beta.9`**:
+>
+> 1. **New update log panel**: a dedicated desktop update window ("Update log") that pops up automatically when the
+>    silent startup check finds a new version that has not been ignored. It offers `Download and install` /
+>    `Ignore this version` / `Later`. "Ignore this version" suppresses the **automatic** prompt only (a manual
+>    "Check for updates" still shows that version, a higher version re-prompts, and the record is persisted in app
+>    preferences). The window states **which source will be used** (the result of concurrently probing Gitee /
+>    GitHub and picking by latency, with an explicit degradation notice when neither is reachable). Its body is the
+>    **bilingual release note** for that version (composed from `docs/release-gui-v<version>.md` + `.en.md`, rendered
+>    as Markdown with inline HTML disabled). The window size follows the maintainer's annotation:
+>    `min(1070px,92vw)` × `min(750px,88vh)`. Adds `mcp-gui/src/core/version.ts` (version comparison and ignore
+>    decisions, 16 unit tests) and `mcp-gui/src/components/UpdateDialog.vue`; `Preferences` gains
+>    `ignored_update_version` (with a serde default so an old preferences file is not reset wholesale).
+> 2. **Release pipeline now supports stable releases**: the tag filter in `.github/workflows/gui.yml` widens from
+>    `gui-v*-beta.*` to **`gui-v*`**, so stable and preview builds share one pipeline; a new step decides the
+>    pre-release flag from the tag shape (only tags containing `-beta.` / `-rc.` pass `--prerelease`); a new
+>    `scripts/gui-release-body.mjs` composes the bilingual release body (used via `--notes-file` on GitHub and
+>    `--body-file` on Gitee, so both sides are **byte-identical in content**, and a missing doc **exits non-zero**).
+> 3. **Version and wording go stable**: the GUI version is unified to `0.1.0` in all four places
+>    (`package.json` / `package-lock.json` / `tauri.conf.json` / `Cargo.toml`); the UI label
+>    "Beta channel (pre-release)" becomes "Stable channel / 正式版通道"; and every hard-coded "beta" wording in
+>    `gitee-gui-release.mjs` and `gui.yml` is removed.
 > (`0.1.0-beta.N`) and its own tag (`gui-v*`).
 
 ### Added

package/CHANGELOG.md

@@ -7,6 +7,69 @@
 
 ---
 
+## [0.7.5] - 2026-09-29
+
+### 修复
+
+- **Qoder CN 0.4.2/0.4.3 适配**（PR #26，贡献者 jian-in）：0.4.2 起模型菜单移除「默认/自定义」
+  分组 tab（候选为平铺列表、模型名移到触发器文本），0.4.3 的输入栏 picker 去掉 `aria-label`、
+  已绑定工作区容器去掉 `title`。选择器候选顺序把稳定标记 `[data-workspace-picker-trigger]`
+  提到宽泛 aria 启发式之前（否则会点中侧栏「工作区」区域头，表现为 `qoder_stage_timeout: workspace-menu`）；
+  「菜单已打开」判定收窄为只认搜索框 `workspaceSearch`（泛化的 `[role=menu][data-state=open]`
+  会被无关浮层误命中而假通过）；已绑定工作区读回并列无 `title` 容器候选并回退 `aria-label`/文本。
+  `QoderCdpClient` 新增 `resolveKey()`/`textKey()`，供组合式查询取首个命中候选。
+- **验收引擎在 Windows 上归一 check 的 `cwd` 盘符大小写**（同 PR）：项目路径可能以小写盘符登记
+  （如 `projects.json` 里的 `e:/proj`），而 vite/vitest 按路径字符串建模块图与缓存键，
+  `e:\proj` 与 `E:\proj` 会被当成两个位置、同一模块出现两份实例，表现为收集期崩溃。
+  `runVerifyCommand` 在 spawn 前用 `fs.realpathSync.native` 归一（非 native 版本在 Windows 上
+  原样返回小写盘符，不纠正大小写）；路径不可解析时退回原值，归一失败不阻断验收。
+
+## [0.7.4] - 2026-09-28
+
+### 修复
+
+- **ZCode 3.14.x 有项目派单恒败于 `project_mismatch`（issue #24）**。ZCode 3.14.x 删除了 tianshu-mcp
+  用于**绑定回读**的两处 DOM 契约（`data-project-path` 与 `data-testid^="workspace-item-"`），而
+  `src/agents/zcode/dom.ts:27` 的 `pathOf()` 只认这两个来源 —— 于是 `workspaceBinding().projectPath`
+  恒为空、`cdp.projects()` 恒为 `[]`，绑定判据永不成立。失败发生在**发送任务书之前**，
+  `autoFixRounds` 形同虚设（`roundsUsed` 恒为 0）。修复落在四处（同一根因）：
+  - `selectors.ts:107` 新增 `projectMenuItem`（`[role="menuitemcheckbox"]`），并把 `projectItem` /
+    `projectPath` 显式标注为 3.11.x 契约；
+  - `dom.ts:38` 的 `workspaceBindingExpression()` 增补 `projectName`（当前绑定显示名）与 `menuChecked`
+    （菜单中 `aria-checked="true"` 的显示名），多勾选判歧义；**不伪造路径** —— 3.14.x 下 `projectPath`
+    仍为空串，判定层据此区分证据等级；
+  - `cdp.ts:279` 的 `projects()` 改为「旧契约完全落空时才从展开菜单采集」（含勾选态、排除
+    「不在项目中工作」），保证 3.11.x 的采集结果逐字不变；
+  - `project.ts:61` 的 `matchZcodeProject()` 增加**显示名精确匹配**分支并返回 `matchedBy`，
+    新增 `boundProjectVerdict()` 实现分层判据：**路径可得时严格判等（原语义不变），无路径渠道时按显示名**，
+    且要求项目列表无同名歧义。
+- **修掉一条被掩盖的脆弱时序**：`ensureProjectBound()` 原先接受外部传入的 item，使「菜单是否恰好还开着」
+  成为隐式前提。现改为幂等自检 —— 每轮先读判定，已绑定即通过、未绑定才展开菜单并点击。
+- **绑定失败诊断补齐**：`project_mismatch` 的错误信息现携带「触发器文本 / 菜单勾选态 / 路径回读」，
+  用户不必再面对一句「回读不一致」而无法自救。
+- **真机取证入口**：`scripts/probe-zcode.mjs` 新增 `dom-contracts` 子命令，输出两处旧契约的命中计数、
+  触发器全属性、菜单项清单与修复后的回读结果（用于在真实 ZCode 上复核本次契约假设）。
+
+### 已知限制
+
+- ZCode 3.14.x 的 DOM 只暴露项目**显示名**、不暴露绝对路径，因此判定采用「显示名 + 全局同名消歧」：
+  同名项 > 1 直接判 `project_ambiguous`（fail-closed）。**能区分的前提是菜单已展开**（`projects()` 的数据源）；
+  菜单收起时只凭 `binding` 的显示名证据，不因列表缺失而否定绑定。3.11.x 的路径判等链路优先级最高，行为不变。
+
+### 测试
+
+- 新增 **14** 用例：`test/unit/zcode-dom.test.ts` 4 条（3.14.x 契约缺席下的回读契约 + 多勾选歧义 +
+  3.11.x 无退化）、`test/unit/zcode-core.test.ts` 6 条（显示名匹配 / 同名 fail-closed / 分层判据 / 路径优先）、
+  `test/integration/zcode-flow.test.ts` 4 条（已绑定直发不误点、未绑定切换后派发、同名歧义 fail-closed、
+  **缺显示名证据的反例**：仍 fail-closed 且错误信息带诊断）。全量 **1383 passed / 12 skipped**
+  （1395 项，115 文件 + 3 个真实浏览器文件按设计 skip）。
+
+> **真机验证边界（如实披露）**：本机**无 ZCode 3.14.x**，未在真机复验。根因（DOM 契约缺席）在
+> `linkedom` 夹具上可**本地决定性复现**：先写用例确认 3 处红灯（`projectName`/`menuChecked` 缺失、
+> `projects()` 为空、多勾选不判歧义），再修到全绿。issue #24 报告的真机实测数据（`data-project-path`
+> 0 命中、`workspace-item-` 0 命中、`menuitemcheckbox` 完好）**未被独立复现**，修复按该契约设计；
+> 有 3.14.x 环境的维护者请跑 `npm run probe:zcode -- dom-contracts` 复核一次。
+
 ## [0.7.3] - 2026-09-28
 
 ### 修复
@@ -133,10 +196,29 @@
 - ARCHITECTURE / README / agent-profiles / adapter-matrix / SKILL / usage-examples 双语：状态由「开发中」同步为「已接线」，并补齐新的 `endReason` / `needsUserKind` 取值。
 - 版本：`package.json` 与 `src/version.generated.ts` 同步为 `0.7.1`（按 `+0.0.1` 规则）；已打 tag `v0.7.1` 并发布到 npm。
 
-## [未发布] — mcp-gui 独立版本线
-
-> 本次变更为**新增独立交付面**：MCP 主包的运行时逻辑（工具契约、任务模型、验收引擎与 `src/**`）**零改动**。
-> **MCP 主包版本保持不变**（仍为 `0.7.0`，尚未发布）；GUI 使用独立版本号（`0.1.0-beta.N`）与独立 tag（`gui-v*`）独立演进。
+## [0.1.0] — 2026-09-29 — mcp-gui 独立版本线
+
+> 本版本为 GUI 独立版本线的**首个正式版**（转正 + 更新日志面板）。MCP 主包的运行时逻辑
+> （工具契约、任务模型、验收引擎与 `src/**`）**零改动**，主包版本保持 `0.7.4` 不变；
+> GUI 使用独立版本号与独立 tag（`gui-v*`）独立演进。
+>
+> **0.1.0 相对 `0.1.0-beta.9` 的三类改动**：
+>
+> 1. **新增更新日志面板**：桌面端独立的更新窗口「更新日志」——启动静默检查命中新版本且该版本未被忽略时
+>    自动弹出，提供 `下载并安装 / 忽略此版本 / 稍后`；「忽略此版本」**只压自动提示**（手动「检查更新」
+>    仍展示该版本，出现更高版本时重新提示，记录持久化在应用偏好）；窗口显式展示**本次将通过哪个源更新**
+>    （并发实测 Gitee / GitHub 择优的结果与延迟，两端都不可达时给出降级提示）；正文即该版本的**双语发行说明**
+>    （`docs/release-gui-v<版本>.md` + `.en.md` 合成，Markdown 渲染、禁用内联 HTML）。窗口尺寸按维护者红框批注
+>    实现为 `min(1070px,92vw)` × `min(750px,88vh)`。新增 `mcp-gui/src/core/version.ts`（版本比较与忽略判定，
+>    16 项单测）与 `mcp-gui/src/components/UpdateDialog.vue`；`Preferences` 新增 `ignored_update_version`
+>    （带 serde 默认值兜底，避免旧偏好文件整份回退默认值）。
+> 2. **发布链转为支持正式版**：`.github/workflows/gui.yml` 的 tag 过滤器由 `gui-v*-beta.*` 扩为 **`gui-v*`**，
+>    正式版与预发布共用一条流水线；新增按 tag 形态判定 pre-release 的步骤（含 `-beta.` / `-rc.` 才带
+>    `--prerelease`）；新增 `scripts/gui-release-body.mjs` 合成双语发行版正文（GitHub 侧 `--notes-file`、
+>    Gitee 侧 `--body-file`，两端**同源**，**缺文档即非 0 退出**）。
+> 3. **版本与文案转正**：GUI 版本号四处（`package.json` / `package-lock.json` / `tauri.conf.json` / `Cargo.toml`）
+>    统一为 `0.1.0`；界面「测试版通道（pre-release）」改为「正式版通道 / Stable channel」；
+>    `gitee-gui-release.mjs` 与 gui.yml 中的硬编码「测试版」字样全部移除。
 
 ### 新增