@tea-agent/loop-agent 0.44.0-next.4 → 0.44.0-next.6

package/CHANGELOG.md

@@ -2,11 +2,39 @@
 
 ## [Unreleased]
 
+- 修复 main 分支的 next 发布链在类型检查阶段内存溢出失败的问题：完整源码与测试的类型图已超过 Node 默认约 2 GiB 堆上限，类型检查进程因此中止（exit 134），导致 `next` 发布无法完成。此前该上限只在部分验证入口生效，其余入口直接运行类型检查就会因默认堆不足而失败；现把上限固化到类型检查命令本身，各验证入口与本地开发统一生效，不再依赖各入口自行声明。
+
+- 修复 Operator Chat 冷启动卡在检查面板的问题：模型列表和 runtime-snapshot 改为读工作区目录，不再为了展示技能或系统提示去打开 Pi 历史 JSONL；发消息、切换模型、reload 仍会激活会话。会话栏也不再等 Pi 重开，工作区列表未返回前不再把侧栏滤空。
+
+- 修复 Operator Chat 在工作区尚未选中时抢先请求仓库树和能力目录、浏览器 Network 出现 400 的问题；等 `workspaceId` 就绪后再请求，不再把启动竞态显示成功能异常。
+
+- 修复 Console 成功更新后历史接棒记录仍占用操作位、导致工作区初始化持续被拒绝的问题；通用「需要核对」提示现在引导先核实实际执行结果，不再误导为重新更新程序。
+
+- Console 更新前保留当前实例身份，修复重启断线后首次响应已来自新进程时仍等待超时、无法自动刷新的问题；关闭重开设置保留该身份，所有刷新等待分支均反馈超时。
+- 修复观测页「执行历史」把仍在重试的节点误报为「最终失败」的问题：只要节点最后一个已记录的尝试失败，就会显示「N 次 · 最终失败」，即使该节点仍在运行、重试已经排队，会让人误判运行已结束。现在节点处于运行/已启动/暂停状态时改为「N 次 · 最近一次失败，仍在重试」，真正到达终态才显示「最终失败」；修复轮次的多轮标签同样处理。
+
+- 修复 Console「更新程序」被一条卡住的旧操作永久堵死的问题：停在「等待核对」的操作记录已被启动对账跳过、自身无法再推进，却又被当成「仍在运行」，导致之后每次更新都提示「另一个 Console 操作正在进行」。现将其明确归为已结束、不再占用操作位，并在恢复页保留可见；同时补全「已安装成功但接棒失败」记录的自动收敛，不再永久停留。
+
+- Console 操作文案改为面向操作者的说明并给出下一步：等待超时不再伪装成「需要核对」，改为提示操作可能仍在后台运行；「源内容已变更」「前端拆分状态被并发修改」等原本直接展示英文原文的错误，改为说明原因与具体处理步骤；恢复页按钮与提示去掉 reconcile / supersede / orphan / Human Gate 等术语。
+
+- 修复后端测试 DAG 模板遗漏 `upstream-unavailable` 重试类别的问题：内置模板的 Markdown 计划节点缺少该类别，与运行时生成器不一致，导致照模板配置的项目少一类重试；现已补齐，并把模板漂移检查扩展到重试策略字段，避免同类不一致再次漏过。
+
+- Operator Chat 右侧辅助栏改为三个表面：仓库、会话、工作台。点上下文环进入「会话 / 上下文」，文件和终端不再与会话检查挤在同一条标签上；工作台用内侧图标轨切换终端、浏览器和数据库。
+
+- Operator Chat 侧栏折叠后改为 56px 图标轨：可直接点新建会话、搜索、添加工作区和设置，不再留下空槽。
+- Operator Chat 的 `@` 文件面板改为按当前目录一层浏览：空 `@` 不再倒出整库路径，点文件默认隐藏，Tab 进入目录、Enter 选定，插入仍是 `@path` 文本。文件行改为左对齐菜单，不再被全局按钮样式居中成胶囊；目录右侧常驻进入箭头，浮层圆角与投影贴近 DSH 菜单。
+- Pi SDK 运行时依赖升级：`@earendil-works/pi-ai` 与 `@earendil-works/pi-coding-agent` 从精确 pin `0.83.0` 升到 `0.84.4`（顺带修复其携带的 `undici` 高危漏洞与 `brace-expansion` DoS 告警）。适配 0.84 破坏性变更：`getApiKeyAndHeaders` 返回的 headers 现可含 `null` 删除标记、`setRuntimeApiKey` 第三参改为认证取消选项；扩展加载 fixture 改为 ESM（pi-ai 子路径导出不再提供 CJS 条件）。SDK 契约探针文案、发布包契约测试与自举 canary 同步对齐 0.84.4。
+
+- 修复 Windows 上 pi 节点零提交失败的读写守卫误报：libuv 在 win32 的 `fstat` 返回卷序列号而 `lstat` 恒为 0，跨 API 比较必然失败并误报“文件在打开期间被替换”；现新建共享身份比较 helper，win32 跳过跨 API `dev` 比较但保留 `ino` 与其余全部防护，Console 仓库预览同类比较一并修复（用户 0.42.1/0.43.0 两次实测上报）。
+- 修复研发工作流对 Git submodule 的误拦截：父仓库 `git status` 只能看到 submodule 目录级条目，子仓库内合法写入会被误判 `empty-diff`（脏基线）或越界（净基线），导致 verify/review/closeout 全部跳过；现在状态采集会展开到已初始化子仓库的文件级事实（含嵌套 submodule、中文/带引号路径解码、未初始化与采集失败时如实报错不吞证据），合法子仓库写入正常进入验证链，真实越界仍按文件精确拦截，无 submodule 仓库行为字节级不变。
+
 - Console 新增低饱和的「暮色蓝」深色与「雾光白」浅色主题，保留默认暖纸色；柔和背景、轻量选中态与独立按钮配色减少视觉刺激。顶部仅显示带「主题」悬停提示的紧凑明暗图标按钮，点击后展开「默认 / 深色 / 浅色」，选完自动收起，支持点击外部或 Escape 关闭；初始使用默认主题；即时切换对话、操作与观测界面，刷新后记住选择，浏览器存储不可用时仍可在当前页面切换。
 - Operator Chat 消息流后续对齐：折叠摘要现在统计 retry/step/command/unknown 等 durable 过程节点，Trajectory 与 HTML 导出保留 DAG progress，并使用稳定过程身份避免直播插入导致 Thinking/工具行重挂载。
 - Operator Chat 统一主时间线、Trajectory 与导出使用同一 DSH flow projection：Thinking、工具、重试、命令和完成态节点按事件序交错，保留 completed-turn 折叠；request/unknown 详情改为有界结构化摘要，不再回显裸节点 JSON。
 - Operator Chat 的消息流对齐 DSH Conversation Node：模型步骤、重试、终止错误、输出上限、每次请求上下文、嵌套工具、`/sdd-bingo` 命令回执和未知事件均以稳定节点留痕；同一模型步骤的多次重试聚合为一条紧凑记录，Provider 终态错误改为轻量行且不再暴露原始响应；流式文本按动画帧合并发布，刷新和断线恢复保持同一身份与顺序，轨迹页面和导出同步展示。
- - Operator Chat 在后台断线重连后不再丢消息：检测到中断会自动补齐缺口内容，也不会把正常的历史回放误判成丢事件而反复重连。
+- Operator Chat 在后台断线重连后不再丢消息：检测到中断会自动补齐缺口内容，也不会把正常的历史回放误判成丢事件而反复重连。
+- Operator Chat 新增独立「上下文洞察」面板：提供当前上下文构成、按步/按轮趋势与累计/增量视图、上下文浏览器（系统提示、工具 Schema、消息、注入、工具结果、技能）、上下文事件筛选、文件活动筛选排序，以及 token/cache/cost/timing 统计；`/context` 与详情栏「洞察」共用同一数据面。
+- 「上下文洞察」新增 token 构成饼图（conic-gradient 渲染）、剪枝/压缩明细（区分 prune 与 compact 事件，展示前/后/回收 tokens、移除项数、原因）；趋势柱 hover/click 实时联动上下文浏览器。
 - Operator Chat 的恢复快照现在只会合并属于目标会话的乐观提交；切换会话后，旧会话尚未确认的输入不会再因延迟重连恢复而显示到新会话中。
 - `/sdd-bingo` 成功提示现在展示上报的 Skill 与 Session ID；轨迹顶部会出现当前会话的常驻 SDD 身份栏，可一键复制、首次请求后自动更新；该上报以独立“操作”事件留痕，刷新或导出后仍在，不再伪装成工具调用。
 - Operator Chat 发送消息后的空白光标改为 Codex 式“正在思考”，真实思考、工具过程或最终回答出现后自然接替；并修复了状态偶发显示在用户输入上方的问题。

package/dist/build-stamp.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "version": "0.44.0-next.4",
-  "gitSha": "6d1cd2f6dd13854cd48bcd4b38718a53cc24109a",
-  "builtAt": "2026-09-15T17:21:15.173Z"
+  "version": "0.44.0-next.6",
+  "gitSha": "11c9ac87f792e61b1bc31b1ef2aeacb48a6334d4",
+  "builtAt": "2026-09-16T11:49:07.558Z"
 }

package/dist/executors/pi-sdk-executor.js

@@ -40,21 +40,21 @@ export async function installPiProviderRequestBudget(session, reserve, onFailure
     const agent = session.agent;
     const original = agent?.streamFunction;
     if (!agent || typeof original !== "function")
-        throw Error("FRONTEND_PROVIDER_BUDGET_UNSUPPORTED: SDK actual request stream unavailable");
+        throw new Error("FRONTEND_PROVIDER_BUDGET_UNSUPPORTED: SDK actual request stream unavailable");
     const { createAssistantMessageEventStream } = await import("@earendil-works/pi-ai");
     agent.streamFunction = async (...args) => {
         try {
             if (args[2]?.signal?.aborted)
-                throw Error("FRONTEND_PROVIDER_REQUEST_ABORTED");
+                throw new Error("FRONTEND_PROVIDER_REQUEST_ABORTED");
             if (capacity) {
                 const measurement = measureFrontendRequestEnvelope(args[1], args[0], capacity.policy);
                 capacity.observe(measurement);
                 if (measurement.exceedsEstimate)
-                    throw Error(`FRONTEND_CONTEXT_ESTIMATE_EXCEEDED: estimated=${measurement.estimatedTokens} available=${measurement.availableInputTokens}; estimator=${measurement.estimatorVersion}; registry capability is not a measured gateway limit`);
+                    throw new Error(`FRONTEND_CONTEXT_ESTIMATE_EXCEEDED: estimated=${measurement.estimatedTokens} available=${measurement.availableInputTokens}; estimator=${measurement.estimatorVersion}; registry capability is not a measured gateway limit`);
             }
             await reserve();
             if (args[2]?.signal?.aborted)
-                throw Error("FRONTEND_PROVIDER_REQUEST_ABORTED");
+                throw new Error("FRONTEND_PROVIDER_REQUEST_ABORTED");
         }
         catch (error) {
             const message = error instanceof Error ? error.message : String(error);
@@ -124,7 +124,7 @@ export function setPiSdkImportOverrideForTests(fn) {
 export function setPiSdkModuleOverrideForTests(fn) {
     sdkModuleOverrideForTests = fn;
 }
-/** Check whether the Pi SDK runtime dependency satisfies the 0.83.0 runtime contract. */
+/** Check whether the Pi SDK runtime dependency satisfies the 0.84.4 runtime contract. */
 export async function checkPiSdkAvailability(_repoRoot) {
     if (sdkSessionFactoryOverride) {
         return { ok: true, detail: "pi SDK session factory override active" };
@@ -140,10 +140,10 @@ export async function checkPiSdkAvailability(_repoRoot) {
             typeof ModelRuntime?.create !== "function") {
             return {
                 ok: false,
-                detail: "pi SDK incompatible: requires createAgentSession, getAgentDir, and ModelRuntime.create (0.83.0 contract)",
+                detail: "pi SDK incompatible: requires createAgentSession, getAgentDir, and ModelRuntime.create (0.84.4 contract)",
             };
         }
-        return { ok: true, detail: "pi SDK 0.83.0 contract available" };
+        return { ok: true, detail: "pi SDK 0.84.4 contract available" };
     }
     catch (error) {
         const message = error instanceof Error ? error.message : String(error);

package/dist/executors/shell-write-guard.js

@@ -4,6 +4,7 @@ import { constants, createReadStream } from "node:fs";
 import { access, lstat, readlink, unlink } from "node:fs/promises";
 import path from "node:path";
 import { pathMatchesPattern } from "../shared/git-progress.js";
+import { expandWorkspaceStatus, hasGitmodulesFile, synthesizeExpandedPorcelain, } from "../shared/git-workspace-status.js";
 import { ResilientGitCommandError, runResilientGitCommand, } from "../shared/resilient-git.js";
 async function sha256File(filePath) {
     const hash = createHash("sha256");
@@ -411,6 +412,7 @@ async function resolveGitExecutableCandidates(platform, env) {
     return ["git"];
 }
 export async function readGitStatusPorcelain(cwd, options = {}) {
+    let parentPorcelain;
     try {
         const result = await runResilientGitCommand({
             cwd,
@@ -419,9 +421,12 @@ export async function readGitStatusPorcelain(cwd, options = {}) {
             attempts: options.attempts,
             retryDelayMs: options.retryDelayMs,
         });
-        if (result.code === 0)
-            return result.stdout;
-        throw new Error(result.stderr.trim() || result.stdout.trim() || `exit ${result.code}`);
+        if (result.code === 0) {
+            parentPorcelain = result.stdout;
+        }
+        else {
+            throw new Error(result.stderr.trim() || result.stdout.trim() || `exit ${result.code}`);
+        }
     }
     catch (error) {
         if (error instanceof ResilientGitCommandError) {
@@ -436,6 +441,24 @@ export async function readGitStatusPorcelain(cwd, options = {}) {
         }
         throw error;
     }
+    // Submodule workspaces: a parent-only porcelain hides every file inside a
+    // registered submodule behind a single directory-level gitlink entry,
+    // which historically produced false empty-diff and false violations
+    // (plan 2026-09-15-development-workflow-git-submodule). Repositories
+    // without .gitmodules keep the parent bytes verbatim — byte-identical
+    // behavior for every non-submodule workspace.
+    if (!(await hasGitmodulesFile(cwd)))
+        return parentPorcelain;
+    const observation = await expandWorkspaceStatus({
+        rootCwd: cwd,
+        parentPorcelain,
+        hasGitmodulesFile: true,
+    });
+    if (!observation.complete) {
+        const failed = observation.repos.find((repo) => repo.state === "status-read-failed");
+        throw new Error(`workspace status expansion incomplete: submodule ${failed?.repoRelativePath ?? "unknown"} status read failed: ${failed?.errorDetail ?? "unknown error"}`);
+    }
+    return synthesizeExpandedPorcelain(observation.entries);
 }
 export async function readGitStatusPorcelainWithDependencies(cwd, options, dependencies) {
     const candidates = await dependencies.resolveExecutableCandidates();

package/dist/infrastructure/console/operation-store.js

@@ -6,6 +6,24 @@ import { buildFrontendSplitAggregateCloseout, computeFrontendSplitDigest, finali
 import { frontendCloseoutFactsSchema, frontendTestHandoffSchema, } from "../../workflows/dag/frontend-closeout.js";
 import { listJsonFiles, readJsonIfExists, sha256Json, writeSecureJson, } from "./app-data.js";
 export const TERMINAL_OPERATION_STATES = new Set(["succeeded", "failed", "timed-out", "restarting"]);
+/**
+ * Operation states that hold an admission slot. needs-reconcile requires
+ * inspection but does not itself prove a live operation; callers still check
+ * DAG/Worker/chat activity separately. restarting is the terminal receipt of
+ * a successful Console handoff, retained across boots, not a live slot.
+ */
+export const OCCUPIED_OPERATION_STATES = new Set(["queued", "starting", "running"]);
+/** True when the state can still make progress and therefore holds the slot. */
+export function isOperationOccupied(state) {
+    return OCCUPIED_OPERATION_STATES.has(state);
+}
+/**
+ * True when no further state transition will ever occur: a business terminal
+ * (succeeded/failed/timed-out/restarting) or a stranded needs-reconcile.
+ */
+export function isOperationSettled(state) {
+    return TERMINAL_OPERATION_STATES.has(state) || state === "needs-reconcile";
+}
 function operationFile(appData, operationId) {
     return path.join(appData.operations, `${operationId}.json`);
 }
@@ -359,14 +377,11 @@ export class OperationStore {
         for (const op of await this.list()) {
             if (TERMINAL_OPERATION_STATES.has(op.state))
                 continue;
-            // A consoleUpdateAndInit whose record already proves a requested
-            // handoff died before writing its terminal state: the update and
-            // restart themselves succeeded — the booting process IS the
-            // handoff target. Mark it succeeded instead of surfacing the
-            // generic needs-reconcile failure copy to the operator.
+            // A consoleUpdateAndInit that proved its handoff before the process
+            // died must not be reported as a stranded failure: the booting
+            // process IS the handoff target, so the update actually succeeded.
             if (op.action === "consoleUpdateAndInit" &&
-                op.state === "needs-reconcile" &&
-                isProvenConsoleUpdateHandoff(op.result)) {
+                isProvenConsoleUpdateHandoff(op)) {
                 changed.push(await this.update(op.operationId, {
                     state: "succeeded",
                     errorCode: undefined,
@@ -398,17 +413,34 @@ export function isTerminalOperationState(state) {
     return TERMINAL_OPERATION_STATES.has(state);
 }
 /**
- * True when a consoleUpdateAndInit result proves the handoff was requested
- * (install verified + init clean + new Console spawned). Used by boot
- * reconcile to close the record as succeeded even though the old process
- * died before writing its terminal state.
+ * True when a consoleUpdateAndInit record proves the handoff actually
+ * succeeded (install verified + new Console spawned), so boot reconcile can
+ * close it as succeeded even though the dying process never wrote its
+ * terminal state.
+ *
+ * The proof reads the maintenance projection rather than only `result.state`.
+ * The old check required `result.state === "restarting"`, but the executor
+ * writes `state` and `maintenance` together (`console-update-and-init.ts`),
+ * so any path that recorded the handoff proof together with a non-restarting
+ * `state` — most importantly the `needs-reconcile` record that
+ * `acceptConsoleUpdateAndInit` writes when the executor throws *after* a
+ * successful handoff — could never satisfy it. Such records were stranded
+ * forever: boot reconcile skipped them and they blocked later updates.
+ *
+ * `handoff.status === "requested"` is only ever set on the success path, and
+ * `package.status === "failed"` explicitly disqualifies a record, so this
+ * stays fail-closed for genuine failures.
  */
-function isProvenConsoleUpdateHandoff(result) {
+export function isProvenConsoleUpdateHandoff(operation) {
+    if (!operation || operation.action !== "consoleUpdateAndInit")
+        return false;
+    const result = operation.result;
     if (!result || typeof result !== "object")
         return false;
     const shape = result;
-    return (shape.state === "restarting" &&
-        shape.maintenance?.handoff?.status === "requested");
+    if (shape.maintenance?.handoff?.status !== "requested")
+        return false;
+    return shape.maintenance?.package?.status !== "failed";
 }
 export function clipPreview(text, max = 4096) {
     if (text.length <= max)

package/dist/shared/file-identity.js

@@ -0,0 +1,23 @@
+/**
+ * Compare two stat records as the same file identity.
+ *
+ * POSIX: `dev` and `ino` together identify the inode; both must match.
+ *
+ * win32: libuv reports `dev` inconsistently across stat APIs — `fstat()`
+ * (from an open handle) returns the volume serial number while `lstat()`
+ * (from a path) returns 0. A cross-API comparison therefore always fails on
+ * Windows even when the path still refers to the same file, breaking every
+ * guard that rechecks identity after opening (user-reported on 0.42.1 and
+ * 0.43.0, Node 23.x). On win32 the `dev` field is skipped and `ino` plus the
+ * caller-side type/link/realpath checks remain the identity boundary.
+ *
+ * When both stats come from the same API the comparison is exact on every
+ * platform; the win32 relaxation only affects cross-API rechecks.
+ */
+export function sameFileIdentity(opened, current, platform = process.platform) {
+    if (current.ino !== opened.ino)
+        return false;
+    if (platform !== "win32" && current.dev !== opened.dev)
+        return false;
+    return true;
+}