dsh-agy-link 0.6.34 → 0.6.36
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +28 -0
- package/README.md +2 -2
- package/dist/cli-image.mjs +1359 -621
- package/dist/client.js +428 -166
- package/dist/index.js +21844 -20664
- package/docs/AUTH.md +19 -14
- package/docs/KNOWN-GAPS.md +1 -3
- package/docs/SECURITY-NOTES.md +14 -53
- package/package.json +2 -3
- package/dist/assets/icon.svg +0 -54
- package/dist/assets/mermaid.min.js +0 -3636
- package/dist/mermaid.min.js +0 -3636
- package/docs/REFACTORING-PLAN.md +0 -51
- package/docs/REFACTORING-RESULTS.md +0 -52
- package/docs/adr-012-account-pool.md +0 -58
- package/docs/spec-account-pool.md +0 -229
- package/icon.svg +0 -54
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,33 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.6.36 (2026-11-19)
|
|
4
|
+
|
|
5
|
+
### English
|
|
6
|
+
|
|
7
|
+
- **Fix: an idle-reaped turn no longer loses its final answer (fixes #128 bug 2, addresses #127).** When the 5s idle reaper ended a turn whose final `PLANNER_RESPONSE` was already written to agy's `transcript.jsonl` but had not been flushed to stdout, the synthesized result carried `response: ''` — DSH then rendered a clean "completed" turn with **no reply bubble**, which reads as success for work that was never confirmed. `recoverFinalReply()` now reads a bounded (≤256 KiB) tail of `<brainDir>/.system_generated/logs/transcript.jsonl` and returns the last `PLANNER_RESPONSE` **after the final `USER_INPUT`** whose `content` is non-empty and which carries no pending `tool_calls`; the synthesized result uses it. When nothing can be recovered, a bilingual notice states the background wait ended without a confirmed outcome and that some steps may have run — the turn still finishes cleanly, and turns that already produced an answer are untouched.
|
|
8
|
+
- **Already fixed upstream, verified:** #128 bug 1 (historical subagent banners replayed on `--conversation` resume) is covered by v0.6.35's `SubagentTracker` baseline (`resumed` + `baselineExisting()`), which seeds pre-existing descriptors into `seenStepKeys` and starts transcripts at EOF.
|
|
9
|
+
|
|
10
|
+
### 中文
|
|
11
|
+
|
|
12
|
+
- **修复:被 idle 回收的轮次不再丢失最终答复(修复 #128 bug 2,回应 #127)。** 当 5s 回收发生在「最终 `PLANNER_RESPONSE` 已写入 agy `transcript.jsonl`、但尚未由 stdout 刷出」的时间窗内时,合成的 result 里 `response` 是空串,DSH 因此显示「正常完成」却**没有任何正文气泡**——这会被读成任务成功,而实际结果未确认。新增 `recoverFinalReply()`:有界读取(≤256 KiB)`<brainDir>/.system_generated/logs/transcript.jsonl` 尾部,返回**最后一条 `USER_INPUT` 之后**、`content` 非空且**无待执行 `tool_calls`** 的 `PLANNER_RESPONSE`,并写入合成 result。恢复不到时改为中英双语提示「后台等待已结束、结果未确认、部分操作可能已执行」;该轮仍以正常 finish 收尾,已有答复的回合完全不受影响。
|
|
13
|
+
- **上游已修复并核实**:#128 bug 1(`--conversation` 续接时重放历史子代理横幅)已由 v0.6.35 的 `SubagentTracker` 基线机制覆盖(`resumed` + `baselineExisting()`,把既有描述符预先记入 `seenStepKeys` 并把 transcript 起点设在 EOF)。
|
|
14
|
+
|
|
15
|
+
## 0.6.35 (2026-11-18)
|
|
16
|
+
|
|
17
|
+
### English
|
|
18
|
+
|
|
19
|
+
- **Risk control & quota pacing:** Added quota burn-rate & reset-pacing estimator (`common/quota-pacing.ts`), serialized burst spawns via `spawn-limiter.ts`, tightened false `authRequired` prevention against transient auth-check jitter (`pool-auth.ts`, `failure.ts`), and avoided aggressive/redundant network probes (`http.ts`, `token.ts`, `refresh.ts`, `warmup/service.ts`).
|
|
20
|
+
- **Instant model sync & 1-click reauth:** Pushed live model-catalog updates cleanly to DSH's session picker and added direct per-account 1-click re-authentication (`/pool/begin-add`, `AccountsPanel`, `useAuthFlow`) plus ETag/304 conditional polling on `/plugins/agy-link/status`.
|
|
21
|
+
- **Subagent state consistency & `CANCELED` handling:** `SubagentTracker` now baselines pre-existing descriptors when `conversationId` arrives late via `setConversationId()` on resumed turns (stopping stale `SUBAGENT_STATE_ALIVE` files from re-announcing as newly opened), honors descriptor `state` (never announces `已启动协同专员` for killed/failed descriptors), polls `ALIVE -> KILLED/STOPPED` transitions and transcript `ERROR`/`CANCELED` statuses, and surfaces `CANCELED` tool steps cleanly across `parser.ts`, `EventMapper`, and `tool-watchdog.ts` (including dropping idle-grace exemption when a subagent spawn fails or cancels).
|
|
22
|
+
- **Performance, UI & SSOT architecture:** O(1) SQLite metadata caching & async `git` HEAD lookup (`git-head.ts`), zero unkeyed React array-child warnings across client components, locales split under `src/client/locales/`, zero-redundancy domain consolidation (`quota-pacing.ts`, `countdown.ts`, `models/parse.ts`, `service-helpers.ts`), and living `.spec/` single-source-of-truth specifications across 225 modules.
|
|
23
|
+
|
|
24
|
+
### 中文
|
|
25
|
+
|
|
26
|
+
- **风控与额度节律保护**:新增额度消耗速率与重置节律估算(`common/quota-pacing.ts`)、并发限流启动器(`spawn-limiter.ts`),收紧瞬时鉴权抖动对 `authRequired` 的误判(`pool-auth.ts`、`failure.ts`),避免过度轮询与冗余网络探测。
|
|
27
|
+
- **模型列表实时同步与一键重登**:切换账号/刷新目录时及时同步推送更新到 DSH 会话模型选择器;新增账号池一键原位重登(`/pool/begin-add`、`AccountsPanel`、`useAuthFlow`)及 `/status` ETag/304 条件轮询,减少高频重绘与状态抖动。
|
|
28
|
+
- **子代理状态一致性与 `CANCELED` 收口**:修复 `SubagentTracker` 在续接会话延迟拿到 `conversationId` 时漏做历史基线导致重放旧 `SUBAGENT_STATE_ALIVE` 为「已启动协同专员」的问题;校验描述符 `state`(初始即终止不误报启动)、持续感知 `ALIVE -> KILLED` 跃迁与 `transcript.jsonl` 中的 `ERROR`/`CANCELED` 状态;并在 `parser.ts`、`EventMapper` 与 `tool-watchdog.ts` 中将 `CANCELED` 工具步按异常收口(子代理派发失败/取消时立即解除 idle 回收豁免)。
|
|
29
|
+
- **性能、前端零告警与 `.spec/` 单一事实源**:SQLite 元数据 O(1) 缓存、异步 `git HEAD` 查询(`git-head.ts`)、修复前端数组子元素缺 `key` 告警、拆分 `src/client/locales/`、收敛冗余逻辑,并建立覆盖 225 模块的 `.spec/` 活文档。
|
|
30
|
+
|
|
3
31
|
## 0.6.34 (2026-11-18)
|
|
4
32
|
|
|
5
33
|
### English
|
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
<a href="https://github.com/amlyczz/dsh-agy-link/actions/workflows/ci.yml"><img src="https://github.com/amlyczz/dsh-agy-link/actions/workflows/ci.yml/badge.svg" alt="CI"/></a>
|
|
10
10
|
<img src="https://img.shields.io/badge/license-MIT-lightgrey" alt="MIT"/>
|
|
11
11
|
<img src="https://img.shields.io/badge/node-%3E%3D24-green" alt="node"/>
|
|
12
|
-
<img src="https://img.shields.io/badge/agy
|
|
12
|
+
<img src="https://img.shields.io/badge/agy-%3E%3D1.5-purple" alt="agy >=1.5"/>
|
|
13
13
|
</p>
|
|
14
14
|
|
|
15
15
|
<p align="center">
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
|
|
43
43
|
> 🚨 **【国内用户核心前置:必须开启系统代理 / TUN 模式!】**
|
|
44
44
|
>
|
|
45
|
-
> Google Antigravity 服务及 OAuth 登录需要直连 Google 海外官方服务器(`oauth2.googleapis.com`、`cloudcode-pa.googleapis.com` 等)。
|
|
45
|
+
> Google Antigravity 服务及 OAuth 登录需要直连 Google 海外官方服务器(`oauth2.googleapis.com`、`daily-cloudcode-pa.googleapis.com` 等)。
|
|
46
46
|
>
|
|
47
47
|
> 1. **推荐方式(最稳妥)**:开启代理工具(Clash / Surge / v2rayA / Sing-box / Loon 等)的 **TUN 虚拟网卡模式(或系统代理全局接管)**,确保终端命令、后台 Node.js 进程及浏览器均能顺畅访问 Google 网络。
|
|
48
48
|
> 2. **终端代理环境变量**:若终端未被代理自动接管,启动 DSH 或运行命令前请在终端中执行:
|