Main CI failed: E2E Tests — cli/qwen-serve-live-journal-recovery.test.ts > … > keeps a compatible live chunk stream within the replay ent… (+2 more)

[qwen-code-dev-bot]

A main-branch E2E Tests run failed on main.

Failing tests

• cli/qwen-serve-live-journal-recovery.test.ts > qwen serve live journal recovery > keeps a compatible live chunk stream within the replay entry cap
• cli/qwen-serve-live-journal-recovery.test.ts > qwen serve live journal recovery > attributes a truncated live tail and exposes the complete turn after terminal
• cli/qwen-serve-webui-live-journal-recovery.test.ts > qwen serve WebUI live journal recovery > repairs once after terminal without another model request

This issue is labeled for autofix so the existing agent can create a repair PR.
It is deduped by failing test, so every later commit that hits the same
failure is appended below instead of opening another issue.

Recurrences

• a669957f3d45 · 2026-08-14T11:16:24Z · run 31794537678
• 4ade537a109b · 2026-08-14T10:47:48Z · run 31792592142

[qwen-code-ci-bot]

✅ Qwen Triage finished — view run. See the stage comments in this thread for the result.

✅ Qwen Triage 已完成 —— 查看运行。结果见本线程中的各阶段评论。

[qwen-code-dev-bot]

🤖 The scheduled autofix agent is picking this issue up. It will attempt to establish the current behavior, implement the requested change, run E2E verification, and open a pull request linked to this issue. If the attempt fails, this claim will be withdrawn so a human can take over.

Maintainers: comment or assign someone to stop future automated attempts, or add the autofix/skip label.

[qwen-code-ci-bot]

Triage

• Type: bug — deterministic main-branch E2E regression; same root cause as Main CI failed: E2E Tests on 4257916e7e5b #9159
• Labels: type/bug (existing), added priority/P1, category/integration, scope/testing, scope/ci-cd
• Next: fix tracked in Main CI failed: E2E Tests on 4257916e7e5b #9159 (autofix in progress) — update the mock ACP child to acknowledge the guard handshake

Analysis (static — reproduction not executed in unattended CI)

• Evidence carried: excerpts from the failing run's own CI logs, quoted below. Not verified by local execution (unattended CI must not run PR/main-tree code).
• Failing run: 31792592142 @ 4ade537a109b — all three listed tests fail at session creation, before any journal logic runs:

  DaemonHttpError: POST /session: ACP child did not acknowledge the required external tool guard (received: undefined).
   ❯ ze.createOrAttachSession ../packages/sdk-typescript/dist/index.mjs
   ❯ cli/qwen-serve-live-journal-recovery.test.ts:51:23   (and :104:23)
  

• Root cause (confirmed by static analysis): feat(daemon): guard cross-worktree Git mutations #8687 (4257916e7e5b, "feat(daemon): guard cross-worktree Git mutations", merged 2026-08-14 09:55 UTC — the first red run; the run immediately before it was green) now always hands the daemon bridge a built-in tool guard, so the channel initialize handshake requires every ACP child to acknowledge it (packages/acp-bridge/src/bridge.ts: the child's initialize response must carry _meta['qwen-code/external-tool-guard-ready'] = 'required-v1'). These three tests spawn the daemon with the mock ACP child (integration-tests/fixtures/mock-acp-child/agent.mjs via QWEN_CLI_ENTRY, unchanged since June), whose initialize() returns a bare response with no _meta — deterministic handshake failure in test setup, not a flake. The real CLI child acknowledges via the private QWEN_CODE_PRIVATE_EXTERNAL_TOOL_GUARD env marker; the mock never implemented that contract. The sibling per-commit issue Main CI failed: E2E Tests on 4257916e7e5b #9159 reports all 5 failed shards reproduced the same error on retry.
• Fix direction: make the mock child's initialize() include the guard-ready _meta acknowledgement (mirroring the real child's contract). qwen-daemon-loadtest.test.ts uses the same fixture and benefits from the same update. The repair is already claimed via Main CI failed: E2E Tests on 4257916e7e5b #9159 (autofix/in-progress); the repair PR should reference both issues.

中文说明

• 类型: bug —— main 分支 E2E 确定性回归，根因与 Main CI failed: E2E Tests on 4257916e7e5b #9159 相同
• 标签: type/bug（已有），新增 priority/P1、category/integration、scope/testing、scope/ci-cd
• 下一步: 修复在 Main CI failed: E2E Tests on 4257916e7e5b #9159 跟踪（autofix 进行中）—— 让 mock ACP 子进程确认 guard 握手

分析（无人值守 CI，未本地执行复现；以 CI 日志为证）

• 证据来源: 失败运行自身的 CI 日志摘录（见上）。无人值守 CI 不执行 main 代码，未做本地复现。
• 失败运行: 31792592142 @ 4ade537a109b —— 三个测试均在创建会话阶段失败，尚未进入 journal 逻辑（POST /session: ACP child did not acknowledge the required external tool guard (received: undefined)）。
• 根因（静态分析确认）: feat(daemon): guard cross-worktree Git mutations #8687（4257916e7e5b，“feat(daemon): guard cross-worktree Git mutations”，2026-08-14 09:55 UTC 合入，其前一次运行还是绿色）使 daemon bridge 始终携带内置工具 guard，channel initialize 握手因此要求所有 ACP 子进程在响应 _meta 中回执 qwen-code/external-tool-guard-ready: required-v1（packages/acp-bridge/src/bridge.ts）。这三个测试通过 QWEN_CLI_ENTRY 使用 mock ACP 子进程（integration-tests/fixtures/mock-acp-child/agent.mjs，六月以来未更新），其 initialize() 返回不含 _meta 的裸响应，测试在 setup 阶段确定性失败，并非 flake。真实 CLI 子进程通过私有环境变量 QWEN_CODE_PRIVATE_EXTERNAL_TOOL_GUARD 完成回执，mock 从未实现该约定。姊妹 issue Main CI failed: E2E Tests on 4257916e7e5b #9159 报告全部 5 个失败 shard 重试均复现同一错误。
• 修复方向: 让 mock 子进程的 initialize() 携带 guard-ready _meta 回执（对齐真实子进程约定）。qwen-daemon-loadtest.test.ts 使用同一 fixture，一并受益。修复已由 Main CI failed: E2E Tests on 4257916e7e5b #9159 认领（autofix/in-progress），修复 PR 应同时关联两个 issue。

--- Qwen Code

[doudouOUC]

This failure is deterministic and was introduced by #8687 (4257916, "feat(daemon): guard cross-worktree Git mutations") — the flagged commit 4ade537 only touches the read-only shell classifier and is unrelated.

What the logs show

All three tests fail at createOrAttachSession on every retry (macOS and both Linux sandbox modes), with the same error:

DaemonHttpError: POST /session: ACP child did not acknowledge the required external tool guard (received: undefined).

So the live-journal assertions never even run — session creation itself fails.

Root cause

#8687 changed the daemon bridge wiring in packages/cli/src/serve/run-qwen-serve.ts from conditionally passing the guard handler…

...(externalToolGuardHandler
  ? { externalToolGuard: externalToolGuardHandler }
  : {}),

…to always passing one:

externalToolGuard: daemonToolGuardHandler,

createDaemonToolGuard() (packages/cli/src/serve/daemon-git-worktree-guard.ts) always returns a truthy handler, and the bridge treats a truthy opts.externalToolGuard as a mandatory handshake: the ACP child must return _meta['qwen-code/external-tool-guard-ready'] === 'required-v1' in its initialize response or channel initialization throws (packages/acp-bridge/src/bridge.ts, around line 3785). The same PR also injects QWEN_CODE_PRIVATE_EXTERNAL_TOOL_GUARD=required-v1 into the child env unconditionally.

The real CLI child acknowledges this in its initialize response (packages/cli/src/acp-integration/acpAgent.ts, around line 4873), but the mock ACP child used by these tests — integration-tests/fixtures/mock-acp-child/agent.mjs — returns a bare initialize response with no _meta, so every POST /session against it now fails.

Timeline corroboration

The last green main E2E run (4ee6a08, run 31790082372) started ~1 minute before #8687 landed; every run since has failed (4257916 → #9159, a29c8b1 → cancelled, 4ade537 → this issue).

Suggested fix

Make the mock fixture mirror the real agent: in its initialize() handler, when process.env.QWEN_CODE_PRIVATE_EXTERNAL_TOOL_GUARD === 'required-v1', include _meta: { 'qwen-code/external-tool-guard-ready': 'required-v1' } in the response. Note that cli/qwen-daemon-loadtest.test.ts also uses this fixture and will hit the same failure whenever it runs.