@zhuxixi/pi-agent-board 0.6.0 → 0.6.2

package/CHANGELOG.md

@@ -5,6 +5,26 @@ conventional commits by `scripts/release_helper.mjs`. Entries are
 forward-only: they begin with the first release after this file landed —
 for earlier history, see the git log and the pull-request list.
 
+## [0.6.2] - 2026-09-09
+
+### Fixes
+
+- **host**: claim role no longer blocks terminal host replacement (#99) (#100)
+
+[0.6.2]: https://github.com/zhuxixi/pi-agent-board/compare/v0.6.1...v0.6.2
+
+## [0.6.1] - 2026-09-08
+
+### Fixes
+
+- add an unconditional Ctrl+Left detach chord to the attach surface (issue #89) (#97)
+- force full-clear repaint on dashboard mount and content shrink (issue #88) (#96)
+- fail host launch fast on a provably stale defaultModel + exit attribution (issue #90) (#94)
+- finalize provably-dead legacy hosts in attach resolver and self-heal (issue #87) (#93)
+- swallow async spawn errors in detached runner launches (issue #86) (#92)
+
+[0.6.1]: https://github.com/zhuxixi/pi-agent-board/compare/v0.6.0...v0.6.1
+
 ## [0.6.0] - 2026-09-07
 
 ### Features

package/README.md

@@ -93,7 +93,7 @@ From the board:
 - In Peek, press `r` to reply without attaching.
 - Press `v` for a read-only transcript, or `e` for evidence and diagnostics.
 - Press `Enter`, `Right`, or `>` to attach to the real Pi session.
-- In PTY attach mode, press `Left` on an empty child input line to return to the board. `Ctrl+]` is not a detach key — it is passed through to the child Pi editor. When the host is disconnected, `Left` always exits.
+- In PTY attach mode, press `Left` on an empty child input line to return to the board, or `Ctrl+Left` at any time (even mid-draft). `Ctrl+]` is not a detach key — it is passed through to the child Pi editor. When the host is disconnected, `Left` always exits.
 
 ## Dashboard Workflow
 
@@ -192,7 +192,7 @@ The `e` view shows durable session evidence, including changed files, commands a
 
 ### PTY attach
 
-PTY attach opens the real interactive Pi session. On an empty child input line, use `Left` to detach and return to the board; while you are editing text, `Left` is forwarded to the Pi editor, and a disconnected host can always be exited with `Left`. `Ctrl+]` is not a detach key — it is passed through to the child Pi editor. While attached, `PageUp`, `PageDown`, `Home`, `End`, and the mouse wheel scroll local scrollback. Mouse drag or double-click selects and copies text, clicks open detected links, and middle-click paste is available on systems with the required X11 tooling.
+PTY attach opens the real interactive Pi session. On an empty child input line, use `Left` to detach and return to the board; while you are editing text, `Left` is forwarded to the Pi editor, `Ctrl+Left` detaches regardless of editor state, and a disconnected host can always be exited with `Left`. `Ctrl+]` is not a detach key — it is passed through to the child Pi editor. While attached, `PageUp`, `PageDown`, `Home`, `End`, and the mouse wheel scroll local scrollback. Mouse drag or double-click selects and copies text, clicks open detected links, and middle-click paste is available on systems with the required X11 tooling.
 
 The attach surface can forward terminal clipboard and image/file passthrough sequences. These behaviors can be disabled individually in [Configuration](#configuration). Cold hosts may briefly show a loading/reconnect surface while their PTY becomes ready.
 

package/docs/superpowers/plans/2026-09-08-attach-ctrl-left-detach.md

@@ -0,0 +1,30 @@
+# issue #89 plan：Ctrl+← detach 和弦实现
+
+日期：2026-09-08 · spec：docs/superpowers/specs/2026-09-08-attach-ctrl-left-detach-design.md
+
+## 任务拆解
+
+### T1：Ctrl+← 分支 + header 文案（A1, A2, A4）
+
+文件：`src/ui/pty-attach.ts`
+
+1. `handleInput` 在 `Key.left` 分支（~L247）之前插入 Ctrl+← 分支（spec D1 代码原样，含注释）。确认 `Key.ctrl` 已从 pi-tui import（文件顶部现有 `Key` import——matchesKey/Key 都在用，无需新 import）。
+2. header 两处文案（~L282 `← detach`、~L298 `← to detach`）→ `←/Ctrl+← detach` / `←/Ctrl+← to detach`。
+
+### T2：测试扩建（A1-A4）
+
+文件：`test-support/detach-gate-smoke.ts` + `test/pty-attach-detach-gate.test.mjs`
+
+1. harness 加场景（照现有场景范式：makeAttach + writeToTerm + handleInput 注入）：
+   - **ctrlLeftDetachesOnDraft**：造一个 editor_state=draft（或写非空内容行进 buffer——看现有 `leftEditorStateBlocksDetachOnDraft` 场景怎么造 draft）→ `handleInput("\x1b[1;5D")` → didDetach() === true；
+   - **ctrlLeftDetachesOnEmptyInput**：空编辑器场景（照现有 C 场景）→ 同序列 → didDetach() === true；
+   - **headerMentionsCtrlLeft**：`attach.render(80)` 输出行里含 "Ctrl+←"（header 在 render 输出组装；注意 attaching 状态——renderLoading 的 L298 在 loading 时显示，L282 在正常帧。两个都改后任一断言即可，取正常帧：先 writeToTerm 一点输出让组件脱离 loading）。
+2. 测试文件加 3 条断言（照现有断言风格）。
+
+### T3：全量回归（A5）
+
+`npm test`（基线 618）+ `npm run typecheck`。
+
+## 验收对账
+- A1/A2/A4 → T2 · A3 → 现有断言回归 · A5 → T3
+- U1（用户实测，合并后）：attach 活跃 session 输入文字后 Ctrl+← 退出。

package/docs/superpowers/plans/2026-09-08-dashboard-shrink-repaint.md

@@ -0,0 +1,68 @@
+# issue #88 plan：dashboard 花屏修复实现
+
+日期：2026-09-08 · spec：docs/superpowers/specs/2026-09-08-dashboard-shrink-repaint-design.md
+
+## 任务拆解
+
+### T1：dashboard.ts render 包装（A1, A2, A3）
+
+文件：`src/ui/dashboard.ts`（唯一运行时代码改动文件，.ts 层满足 jiti 可重载约束）
+
+1. 组件新增字段（class 字段区，~L126-147 附近）：
+```ts
+/** First frame after mount must clear the screen: pi-tui's first render
+ *  "assumes clean screen" (fullRender(false)) and overlays never get
+ *  clearOnShrink — crash output / dirty bottoms would persist (issue #88). */
+private needsFullClear = true;
+/** Content line count BEFORE fitToHeight padding (padding always fills the
+ *  terminal height, so padded counts never shrink — shrink must be detected
+ *  on content lines). */
+private lastContentLineCount: number | null = null;
+private frameContentLineCount = 0;
+```
+
+2. `fitToHeight` 开头记录 pad 前行数：`this.frameContentLineCount = lines.length;`
+
+3. 现有 `render(width: number): string[]`（L1158 起）整体改名为 `private renderLines(width: number): string[]`，新增包装：
+```ts
+render(width: number): string[] {
+	const lines = this.renderLines(width);
+	// Self-heal frames (issue #88): pi-tui disables clearOnShrink under overlays,
+	// so a content shrink would leave stale rows forever. Force a full clear on
+	// the first frame and on any content-line shrink. requestRender(true) is
+	// nextTick-async — safe to call from inside render.
+	if (this.needsFullClear || (this.lastContentLineCount != null && this.frameContentLineCount < this.lastContentLineCount)) {
+		this.needsFullClear = false;
+		this.tui.requestRender(true);
+	}
+	this.lastContentLineCount = this.frameContentLineCount;
+	return lines;
+}
+```
+
+注意点：
+- `renderLines` 保持原签名与所有 return 分支不变（仅改名）；
+- `this.tui.requestRender` 在 Component 的 TUI 类型上存在（pi-tui 导出类型含它；若类型缺 force 参数签名，用 `(this.tui as any).requestRender(true)` 并在注释说明，或查 TUI 类型定义确认——typecheck 必须过）；
+- 不改 `src/core/dashboard-render.mjs`（requestDashboardRender 保持差分语义，现有测试不动）。
+
+### T2：冒烟测试（A1, A2）
+
+1. 新增 `test-support/dashboard-shrink-render.ts`（范式照搬 dashboard-refs-render.ts：真实 root + createView + service + fake tui/theme/keybindings）：
+   - fake tui 的 `requestRender` 记录调用参数（spy），`terminal.rows` 固定 40；
+   - 造 3 个 view → 第 1 次 render(160)（首帧）；
+   - 第 2 次 render(160)（同数据，无变化）；
+   - 删掉 1 个 view（service 的删除 API——先看 refs-render 或 service 里 deleteView/removeView 叫什么；若无删除 API，用第三个 view 的 cwd folder 折叠/直接操作 store 删目录亦可，目标是让内容行数减少）；
+   - 第 3 次 render(160)（内容行数减少）；
+   - 输出 JSON：`{ calls: [...] , ok: true }`（requestRender 的参数序列）。
+2. `test/dashboard-render.test.mjs` 新增用例（execFileSync + --experimental-transform-types，照抄 refs 用例）断言：
+   - 首帧后 calls 含 `[true]`（D1）；
+   - 第二帧（无变化）无新增 `[true]`；
+   - 第三帧（收缩）后再次出现 `[true]`（D2）。
+
+### T3：全量回归（A4）
+
+`npm test`（基线 617）+ `npm run typecheck`。
+
+## 验收对账
+- A1/A2 → T2 断言 · A3 → diff 审查（运行时改动仅 dashboard.ts）· A4 → T3
+- U1（用户实测，合并后）：密集增删 session 观察无残影。

package/docs/superpowers/plans/2026-09-08-legacy-stale-host-recovery.md

@@ -0,0 +1,125 @@
+# issue #87 plan：legacy 死 host 安全回收实现
+
+日期：2026-09-08 · spec：docs/superpowers/specs/2026-09-08-legacy-stale-host-recovery-design.md
+
+## 任务拆解
+
+### T1：纯决策函数 `canFinalizeLegacyHost`（A1）
+
+**文件**：`src/core/host-coordination.mjs`（新增导出，放 `classifyProbeResult` 附近）
+
+```js
+/**
+ * Whether a legacy (pre-instanceId) host record can be safely finalized as
+ * exited: the runner pid is provably dead (a reused pid reads alive →
+ * conservative false) AND the endpoint is unreachable. Satisfies spec §10.1's
+ * "never recovered" conservatism — recovery only fires when identity is
+ * certain (issue #87).
+ * @param {{ host: HostStatus|null, hostPid: number|null|undefined, hostPidAlive: boolean, probeClassification: string }} input
+ * @returns {boolean}
+ */
+export function canFinalizeLegacyHost({ host, hostPid, hostPidAlive, probeClassification }) {
+	if (!host || host.instanceId != null) return false;
+	if (host.state !== "starting" && host.state !== "alive") return false;
+	if (hostPid == null || hostPidAlive) return false;
+	return probeClassification === "missing" || probeClassification === "stale";
+}
+```
+
+**测试**：`test/host-coordination.test.mjs` 新增真值表用例（在文件既有风格下）：
+- 全条件满足（starting/alive × missing/stale 四组合）→ true
+- instanceId 非 null → false
+- state ∈ {exited, failed, stopping} → false
+- hostPid null / hostPidAlive true → false
+- classification ∈ {ready, starting, occupied, unknown} → false
+- host null → false
+
+### T2：resolver 两处改造（A2-A5）
+
+**文件**：`src/runtime/service.mjs`
+
+1. **import 更新**：`readHostPid` 加入 store.mjs import 列表；`canFinalizeLegacyHost` 加入 host-coordination.mjs import（L28 现有 `canReplaceHost` 同处）。
+
+2. **新增模块内 helper**（resolver 函数前，模块作用域）：
+
+```js
+/**
+ * Finalize a provably-dead legacy host as exited so the resolver loop's next
+ * iteration sees hostActive=false and claims a fresh new-protocol host
+ * (issue #87). Legacy records have no instanceId — no concurrent owner exists,
+ * so an unfenced writeHost is safe; the claim path is serialized by the
+ * host-start lease.
+ * @returns {boolean} true when finalized (caller should `continue` the loop).
+ */
+function finalizeDeadLegacyHost(root, viewId, host, probeClassification) {
+	const hostPid = Object.hasOwn(host, "runnerPid") ? host.runnerPid : readHostPid(root, viewId);
+	if (!canFinalizeLegacyHost({ host, hostPid, hostPidAlive: isAlive(hostPid), probeClassification })) return false;
+	writeHost(root, { ...host, state: "exited", endedAt: Date.now(), lastSeenAt: Date.now(), error: "legacy host finalized: runner pid dead (issue #87)" });
+	try {
+		appendDiagnostic(root, viewId, {
+			source: "service", level: "info", code: "legacy_host_finalized",
+			message: `Finalized stale legacy host (pid ${hostPid} dead, probe ${probeClassification}) — next attach claims a fresh host`,
+			details: { hostPid, probeClassification, previousState: host.state },
+		});
+	} catch { /* best effort */ }
+	return true;
+}
+```
+
+注意：`writeHost` 签名是 `(root, host)`（host 内含 viewId），与 updateOwnedHost 不同。appendDiagnostic 签名参照文件内现有调用（`appendDiagnostic(root, viewId, {...})`，如 recoverHost 附近用法——实现时以现有调用为准）。
+
+3. **resolver legacy alive 分支**（现 L963 附近）：
+
+```js
+} else if (legacy) {
+	// Legacy host unreachable. spec §10.1 says never recover — unless the
+	// runner pid is provably dead, in which case finalize and self-heal
+	// (issue #87).
+	if (finalizeDeadLegacyHost(root, viewId, host, probe.classification)) {
+		await sleepFnImpl(HOST_PROBE_RETRY_MS);
+		continue;
+	}
+	return pending(sessionFile, "legacy host unreachable — manual restart needed");
+}
+```
+
+4. **resolver starting-legacy 分支**（现 L953-957 附近，`withinGrace || legacy` 等待分支）：
+
+```js
+if (withinGrace || legacy) {
+	// A legacy starting host whose runner is provably dead would wait out
+	// the grace window forever (withinGrace is always true for legacy) —
+	// finalize it now instead (issue #87).
+	if (legacy && finalizeDeadLegacyHost(root, viewId, host, probe.classification)) {
+		await sleepFnImpl(HOST_PROBE_RETRY_MS);
+		continue;
+	}
+	// Normal cold start (or a legacy starting host — legacy is never recovered,
+	// spec §10.1): wait out the grace window.
+	await sleepFnImpl(HOST_PROBE_RETRY_MS);
+	continue;
+}
+```
+
+（此分支 probe 已在上方 L939 执行，classification 可得。）
+
+**测试**：`test/host-resolver.test.mjs` 新增 4 个测试（fixtures 复用 hostRecord/scriptProbe/instantSleep/resolverService；launchHost override 模仿现有 adoption 测试的成功 spawn 模式）：
+
+- **A2 自愈闭环**：legacy alive host（hostRecord：instanceId:null、state:"alive"、**无 runnerPid 属性**——用 delete 或构造时排除）+ host-pid.json 写死 pid（writeHostPid 或 readHostPid 对应写法，参照 store.mjs 导出；用不可能存活的 pid 如 999999——注意须确认该 pid 在测试机不存在，现有 fixture aliveHost 已用 999999 表达"死 pid"，同法）+ scriptProbe(["missing"]) + launchHost override 成功 spawn → 断言：resolveAttachTarget 最终返回 kind:"pty"（新 host）；readHost 状态变迁——最终 host 是新 instance（launchHost 写入 starting）；diagnostics 含 legacy_host_finalized。
+  - 实现细节：claim/launch 后 readHost 读到的是新 host 记录，验证 finalize 发生要靠 diagnostics 断言 + resolve 结果非 pending。
+- **A3 保守分支**：同上但 host-pid.json 写 `process.pid`（活 pid）→ 断言返回 pending（reason 含 "legacy host unreachable"）且 host.json 未被改写（state 仍 alive）。
+- **A4 starting-legacy 回收**：legacy starting host（claimAt 久远超 grace，pid 死）+ probe missing + launchHost spawn 成功 → 断言不自 deadline timeout、最终 kind:"pty"、diagnostics 含 legacy_host_finalized。
+- **A5 unknown 不回收**：pid 死 + scriptProbe(["unknown"]) → 断言 pending 且不写盘。
+
+⚠️ fixture 要点：hostRecord 默认写 `runnerPid: null`——这会让 `Object.hasOwn(host, "runnerPid")` 为 true，fallback 不到 host-pid.json。legacy fixture 必须构造**没有 runnerPid 属性**的记录（hostRecord 加 `legacy: true` 选项删除 instanceId/runnerPid 等字段，或新写 `legacyHostRecord` helper），并配 `writeHostPid(root, viewId, pid)` 写镜像。
+
+### T3：全量回归（A6）
+
+`npm test` + `npm run typecheck`（基线 602）。
+
+## 验收对账
+
+- A1 → T1 真值表单测
+- A2/A3/A4/A5 → T2 四个集成测试
+- A6 → T3
+- U1（用户实测，合并前）：本机 6 个真实卡死 legacy view attach 验证——主 session 合并前提示用户执行，或合并后实测反馈。

package/docs/superpowers/plans/2026-09-08-spawn-async-error-swallow.md

@@ -0,0 +1,56 @@
+# issue #86 plan：spawn 异步 error 兜底实现
+
+日期：2026-09-08 · spec：docs/superpowers/specs/2026-09-08-spawn-async-error-swallow-design.md
+
+## 任务拆解
+
+### T1：launch.mjs spawnDetached helper + 4 处收敛（A1, A2）
+
+**改动**（`src/core/launch.mjs`）：
+1. 文件底部（或 import 后）新增模块内 helper：
+```js
+function spawnDetached(command, args, cwd) {
+	const child = spawn(command, args, {
+		cwd,
+		detached: true,
+		stdio: "ignore",
+		env: process.env,
+		// Windows: detached children get their own console window unless
+		// suppressed (CREATE_NO_WINDOW; no-op on POSIX) — issue #49.
+		windowsHide: true,
+	});
+	// Swallow async spawn failures (e.g. transient ENOENT on the node binary):
+	// without an 'error' listener the EventEmitter rethrows as uncaughtException
+	// and takes down the whole host Pi process (issue #86). Callers already
+	// record state "failed" via the pid == null branch.
+	child.on("error", () => {});
+	child.unref();
+	return child;
+}
+```
+2. `launchRun` / `launchHost` / `launchTitle` / `launchAutoState` 四处的 `spawn(...)` + `child.unref()` 收敛为 `const child = spawnDetached(node, [opts.runnerScript, configPath], config.cwd);`，返回值逻辑（`child.pid ?? null`、writePid 等）不变。
+
+**测试**（`test/launch.test.mjs`，复用现有注入模式）：
+- 新增 1 个测试：注入 `node: "/nonexistent/node-ENOENT-test"`，依次调用 4 个入口，断言：各自正常返回 `{ pid: null }`；`process.on("uncaughtException")` spy 不被触发；等待 ~300ms 让异步 error 有机会冒泡（进程崩 = 测试天然失败）。
+- 现有 4 个测试不动（A2 回归）。
+
+### T2：pty-attach.ts openExternalTarget error 兜底（A3）
+
+**改动**（`src/ui/pty-attach.ts` L1150-1167）：三分支统一为：
+```ts
+const child = spawn("xdg-open", [sanitized], { detached: true, stdio: "ignore" });
+child.on("error", () => {});
+child.unref();
+```
+（darwin `open`、win32 `cmd /c start` 同理）。参照 L847-848 xclip 既有模式。
+
+### T3：全量回归（A4）
+
+`npm test` + `npm run typecheck`，568+ 全绿。
+
+## 验收对账
+
+- A1 → T1 新测试
+- A2 → T1 既有测试回归
+- A3 → T2 代码审查 + `rg 'child.on\("error"' src/ui/pty-attach.ts` 断言三分支（A3 static）
+- A4 → T3

package/docs/superpowers/plans/2026-09-08-stale-model-attach-guard.md

@@ -0,0 +1,96 @@
+# issue #90 plan：defaultModel 失效防护实现
+
+日期：2026-09-08 · spec：docs/superpowers/specs/2026-09-08-stale-model-attach-guard-design.md
+
+## 任务拆解
+
+### T1：core 匹配函数 + service 注入（A1, A4）
+
+1. `src/core/launch-options.mjs` 新增导出（spec D1.1 签名原样）：
+```js
+export function modelRefAvailable(modelRef, availableModels) {
+	const ref = String(modelRef ?? "").trim().toLowerCase();
+	if (!ref) return true;                    // no constraint
+	if (!availableModels || availableModels.length === 0) return true;  // can't judge → allow
+	return availableModels.some((m) => `${m.provider}/${m.id}`.toLowerCase() === ref);
+}
+```
+2. 单测：若已有 `test/launch-options*.test.mjs` 则加入，否则新建。真值表：精确匹配（大小写混合）→ true；不匹配 → false；null/空串 → true；availableModels undefined/[] → true；部分匹配（"glm-5.3" 不配 provider）→ false。
+3. `src/ui/dashboard.ts` L1738 `findLaunchModelByRef` 改为内部调用 core 的匹配逻辑（保持返回 LaunchModel 对象：find 复用 `modelRefAvailable` 不可行——它返回 boolean；改为直接复用 core 里新增的共享比较，或最简单：dashboard 本地函数改为 `models.find(m => modelRefAvailable(ref, [m])) ?? null`。选最简单且单一事实源的写法）。
+   - 注：若这步让 diff 变脏（import 路径等），可以跳过，dashboard 本地函数保持——在 plan 偏差里说明即可。优先级低。
+
+### T2：service 校验接线（A2, A3, A5）
+
+1. `createService` opts 新增：`availableModels`（`() => Array<{provider:string,id:string}> | undefined`；默认 undefined → 跳过校验）。JSDoc typedef 更新（文件内 createService opts 注释处）。
+2. service.mjs 模块内新增 helper：
+```js
+/** @returns {string|null} error message when the view's defaultModel is provably unavailable. */
+function validateViewModelMeta(meta) {
+	const model = meta.defaultModel ?? null;
+	if (!model || !optsAvailableModels) return null;
+	const list = optsAvailableModels() ?? undefined;
+	if (modelRefAvailable(model, list)) return null;
+	return `Model "${model}" configured for this session is no longer available — update the view's model (or clear defaultModel) and retry attach.`;
+}
+```
+（注意 availableModels() 调用本身 try/catch → undefined。）
+3. `startHostUnderLease`（L205）：在 canReplaceHost 检查之后、instanceId 生成之前插入：
+```js
+const modelError = validateViewModelMeta(meta);
+if (modelError) return { ok: false, error: modelError };
+```
+（校验失败不留 claim、不 spawn。）
+4. `adoptClaimedHost`（L775 起）：config 构建前插入校验；失败时：
+```js
+updateOwnedHost(root, viewId, instanceId, (h) => ({ ...h, state: "failed", endedAt: nowImpl(), exitCode: 1, error: modelError, claimPid: null, claimIdentity: null }));
+return { ok: true, pending: true, socketPath: null, instanceId };
+```
+（对齐该函数既有 spawnError 失败处理模式。）
+5. `src/index.ts` serviceFor 与 `src/commands/agent-board.ts` flag 路径注入：
+```ts
+availableModels: () => { try { return ctx.modelRegistry.getAvailable(); } catch { return undefined; } },
+```
+（agent-board.ts flag 路径 L115 的 createService 调用同款注入；dashboard 路径 L95 已有 availableModels 变量但那是 UI deps，service 注入仍需单独传。）
+6. 集成测试（`test/host-resolver.test.mjs` 或 `test/service.test.mjs`，看 ensure 测试在哪更顺）：
+   - A2：view meta defaultModel="glm/glm-5.3"，注入 availableModels: () => [{provider:"zai-coding-cn",id:"glm-5.3"}]，launchHost spy → ensureHost("v1") 断言 ok:false、error 含模型名、spy 零调用、readHost 无 starting 残留；
+   - A3 对照：availableModels 含 glm/glm-5.3 → 正常 claim+spawn（断言 started/started pending 路径与现状一致）；
+   - A4：不注入 availableModels → 跳过校验正常 launch；
+   - A5：废弃 starting claim（adopt 路径，参照现有 adoption 测试 fixture）+ 失效模型 → 断言落 failed、不 spawn。
+
+### T3：runner exit 归因（A6, A7）
+
+1. `src/core/heuristics.mjs` 新增导出：
+```js
+/**
+ * Last non-empty visible line of a raw terminal log chunk (ANSI/OSC stripped,
+ * per-line carriage-return resolved). @returns {string|null}
+ */
+export function lastVisibleLogLine(text, maxLen = 200)
+```
+实现：strip `/\x1b\][^\x07\x1b]*(?:\x07|\x1b\\)/g`（OSC）→ `/\x1b\[[0-9;?]*[ -/]*[@-~]/g`（CSI）→ 其他 `\x1b.` 单字符转义 → 按 `\n` 切分 → 每行取最后一个 `\r` 之后段 → trim → 过滤空 → 取最后一行 → truncate(maxLen)（复用同文件 truncate）。
+2. 单测（heuristics 测试文件）：ANSI 颜色、OSC 链接、`\r` 覆盖行、空行跳过、截断、空输入 → null。
+3. `runner/pty-runner.mjs` child exit 回调（L213-223 区域）：
+```js
+if (!crashed) {
+	let exitError = null;
+	if (exitCode !== 0) {
+		try {
+			const tail = readScreenLogTail(screenLog, 8192);  // openSync/readSync seek 尾部
+			exitError = lastVisibleLogLine(tail);
+		} catch { /* best effort */ }
+	}
+	update({ state: "exited", endedAt: Date.now(), exitCode, childPid: null, ...(exitError ? { error: exitError } : {}) });
+	...
+}
+```
+（screenLog 变量在 L62 作用域内可见；确认该回调能访问到。readScreenLogTail 写成 runner 内私有小函数。）
+4. 集成测试（test/pty-runner.integration.test.mjs）：用 test-support/ 下 fake pi 模式（看 fake-slow-start-pi.mjs；若无"立即 exit 1 + 输出错误"的 fake 就新增一个 `fake-failing-pi.mjs`：打印 `Error: Model "glm/glm-5.3" not found.` 后 exit 1）→ spawn runner → 等 exit → 断言 readHost 的 error 含 "Model" / "not found"；对照 exit 0（现有 fake）→ error 字段保持 null。注意 hasNodePty skip 守卫参照现有测试。
+
+### T4：全量回归（A8）
+
+`npm test` + `npm run typecheck`（基线 608）。
+
+## 验收对账
+
+- A1 → T1.2 · A2/A3/A4/A5 → T2.6 · A6 → T3.2 · A7 → T3.4 · A8 → T4
+- U1（用户实测，合并后）：view_539a5e9e20 恢复失效 defaultModel → attach 看 notify + diagnostics 不再累积；改回有效模型 attach 成功。