@tea-agent/loop-agent 0.24.2-beta.0 → 0.24.3-beta.0

package/CHANGELOG.md

@@ -2,20 +2,40 @@
 
 ## [Unreleased]
 
-## [0.24.2-beta.0] - 2026-07-28
+### 改进
+
+- 发布工作流改为发布已通过完整门禁并经 SHA-256 校验的 npm tarball，避免 `npm publish` 再次触发全量测试、类型检查与构建。
+
+## [0.24.2] - 2026-07-28
+
+### 重点更新
+
+- 夜间自动发布固定为 patch 通道，不再因功能提交自动跳转次版本号
+- 新增人工次版本发布工作流，支持显式触发 v0.x.0 版本线升级
+- 夜间发布支持幂等恢复，重跑时自动探测并跳过已完成步骤，冲突时安全失败
+- 控制台聊天工作台布局收紧，新增聚焦模式与落地页设计
+
+### 新增
+
+- 新增 manual-minor-release 工作流，仅在显式触发时强制 bump minor 版本
+- 控制台新增 ChatLanding 子组件，提供无会话/空会话模式下的落地页与建议网格
+- 聊天压缩失败分类器新增对 token 预算超限、已压缩、模型缺失、活跃对话及不支持运行时等场景的精确 HTTP 状态码映射
 
 ### 改进
 
-- 夜间自动发布固定为 patch 通道（当前 `0.x.y` 上 +0.0.1，例如 `0.24.1 -> 0.24.2`），不再因 `feat:` 自动跳到 `0.x.0`。
-- 新增人工主版本工作流 `manual-minor-release.yml`，仅在显式触发时强制 bump minor，产出 `v0.x.0`。
-- 发布通道可将文档版本钉死/漂移降为告警（`LOOP_AGENT_DOC_VERSION_REFS=warn`），避免 nightly/prepublish 被安装文档旧精确串误阻塞；结构性文档治理仍 fail-closed。
+- 发布工作流将最终门禁拆分为独立可观测步骤，并去重以提升执行效率
+- 夜间自动发布固定为 --bump=patch，确保版本递增稳定在 0.x.y + 0.0.1
+- 文档版本引用现支持 floating/current/minimum/range/historical 五类语义声明，合法旧文档不再误阻塞发布
+- 控制台聊天界面收紧工作台密度，新增 is-chat-focus 类锁定视口，仅消息区域滚动且输入框固定底部
+- 聊天压缩接口现通过分类器返回类型化错误码，替代原有的通用失败提示
 
 ### 修复
 
-- 发布流程不再被合法的旧版本引用误阻塞：文档 catalog 现可用 `current`/`floating`/`minimum`/`range`/`historical` 五类语义声明版本引用，审查时基线等历史证据保留当时真实精确版本并通过检查，仅当前安装入口的精确钉死仍判为漂移。
-- Nightly Release 现在在版本号与 CHANGELOG 准备完成之后、push/打 tag/发布 npm/创建 GitHub Release 之前运行最终 release tree 门禁（测试、构建、仓库治理、`npm pack` 干跑），避免在未通过最终门禁的发布树产生远端副作用。
-- Nightly Release 的 commit/tag、npm publish、GitHub Release 三步现支持幂等恢复：重跑时探测目标对象是否存在，一致则跳过、冲突则 fail closed（不 force-push、不重写 tag、不重复发布），可补齐半发布状态。
-- 文档版本治理的 `minimum`/`range` 声明现会校验文档正文实际出现的精确版本串与声明门槛/范围一致；仅元数据通过而正文钉死低于门槛或不满足范围的版本时仍判失败，避免安装入口借 minimum/range 声明悄悄钉死旧版本。
+- 修复发布流程接受 GitHub Release 目标时无法正确处理符号引用的问题
+- 修复 GitHub 状态探测缺少认证导致发布恢复判断不准确的问题
+- 修复夜间发布恢复时未针对当前版本标签进行探测的问题
+- 修复夜间发布与手动次版本发布通道混淆的问题，现拆分为独立的 patch 与 minor 通道
+- 修复文档版本治理将合法的旧版本引用误判为漂移并阻塞发布的问题
 
 ## [0.24.1] - 2026-07-27
 

package/dist/application/dag/generate-task-dag.js

@@ -239,10 +239,8 @@ export async function generateTaskDagUseCase(input) {
         reasons: ["dag run-task validate did not report governanceProfile"],
     });
     const hasExplicitSpecializedTaskKind = candidateResult.templateSelection.source === "taskKind";
-    const hasSafeAutomaticTaskSourceRoute = candidateResult.templateSelection.source === "task-source" &&
-        profileRouting.selectedByProfile !== "supervised" &&
-        profileRouting.selectedTemplate !== "supervised-implementation";
-    if (hasExplicitSpecializedTaskKind || hasSafeAutomaticTaskSourceRoute) {
+    const hasAutomaticTaskSourceRoute = candidateResult.templateSelection.source === "task-source";
+    if (hasExplicitSpecializedTaskKind || hasAutomaticTaskSourceRoute) {
         profileRouting.selectedTemplate = candidateResult.template;
         profileRouting.source = hasExplicitSpecializedTaskKind
             ? "taskKind"
@@ -256,10 +254,9 @@ export async function generateTaskDagUseCase(input) {
             profileRouting.selectedByProfile = parsed.profile;
         }
     }
-    // Persist only a safe automatic route. Explicit supervised/profile policy
-    // must remain authoritative and must not be weakened by this convenience
-    // marker. Keep taskId stable; frontend-implementation is the taskKind.
-    if (hasSafeAutomaticTaskSourceRoute && candidateResult.template === "frontend-implementation") {
+    // Persist the automatic business workflow route while preserving the
+    // governance profile as a separate routing dimension.
+    if (hasAutomaticTaskSourceRoute && candidateResult.template === "frontend-implementation") {
         const taskConfig = await loadTaskConfig(repoRoot, parsed.taskId);
         if (!taskConfig.taskKind || taskConfig.taskKind === "standard") {
             await writeTaskConfig(repoRoot, parsed.taskId, {

package/dist/commands/init.js

@@ -2053,7 +2053,7 @@ function buildTargetFeatureWorkflow(input) {
         "- An implicit frontend demand selects the frontend DAG only when project or frontend-path evidence is paired with product-delivery semantics; framework evidence alone is insufficient. Backend, mixed, negated, documentation/test maintenance, and unknown demands keep the template selected by the normal governance profile.",
         "- `frontend-mock-assess-pi` reads Mock/API/schema evidence and selects `native|browser-intercept|request-adapter|not-needed|blocked` before frontend planning; its deterministic gate rejects blocked or malformed output, while the existing frontend implementer remains the only writer.",
         "- Mock-backed verification never proves real API integration. When the backend was not exercised, closeout must retain the gap and name `<task-id>-real-api-integration-verify`; that follow-up is explicitly created/run after backend readiness, never automatic.",
-        "- Automatic frontend classification never replaces a supervised template selected by an explicit profile, workflowPolicy, or the supervised quality gate.",
+        "- Automatic frontend classification selects the frontend implementation workflow and persists taskKind; explicit profiles, workflowPolicy, and supervised quality gates record governance strength without switching the business workflow back to a generic DAG.",
         "- A backend implementation does not select the backend test DAG. `backend-test` remains an explicit test-engineering workflow.",
         "- Explicit specialized `taskKind` values remain compatible and take precedence over task-source classification.",
         "",

package/dist/task/task-demand-routing.js

@@ -402,13 +402,6 @@ export function resolveTaskDagTemplateSelection(input) {
             reasons: [],
         };
     }
-    if (requestedTemplate !== "standard-dag") {
-        return {
-            template: requestedTemplate,
-            source: "requested-template",
-            reasons: [],
-        };
-    }
     const classification = classifyTaskDemand(input);
     if (classification.kind === "frontend") {
         const frontendSignals = classification.signals
@@ -423,6 +416,14 @@ export function resolveTaskDagTemplateSelection(input) {
             classification,
         };
     }
+    if (requestedTemplate !== "standard-dag") {
+        return {
+            template: requestedTemplate,
+            source: "requested-template",
+            reasons: [],
+            classification,
+        };
+    }
     return {
         template: requestedTemplate,
         source: "requested-template",