@whyshu/argent-engine 0.7.2 → 0.7.4

package/engine/scripts/patches/verify-transport-diagnostics.mjs

@@ -1,227 +0,0 @@
-#!/usr/bin/env node
-/**
- * TRANSPORT 诊断补丁校验（2026-10-02，任务 D）。
- *
- * 补丁：`dsh-llm-deepseek--transport-diagnostics.patch`
- * 目标：`@deepseek-ai/dsh-llm-deepseek/lib/index.js`（官方 Messages 适配器；
- *       **问述代理复用同一份**，见 `plugins/argent-core/src/llm-whyshu.js`）。
- *
- * ## 为什么要有它
- * 线上现象：Web 回合偶发 `This turn failed / DeepSeek Messages transport failed`。
- * 实测（session-06732069 / session-878f3e3b 的会话日志）该 failure 落进 `llm/retry`
- * 事件时**只有 `{message, code}`**，没有 cause、没有请求标识、没有"已产出多少"
- * ⇒ 事后既分不清 ECONNRESET / 提前关闭 / 5xx 断流，也无法判断"这次到底产出了没有"。
- * 补丁只做**可观测性**（判定语义不变）。
- *
- * ## 本脚本验什么
- *   ① 源码语义断言：三分支判定**未被改动**（顺序、code、`instanceof LlmError` 直通都还在）；
- *   ② 行为断言：把补丁插入的纯函数**取出来真跑**，逐个覆盖
- *      ECONNRESET / socket hang up / ETIMEDOUT / 非 2xx + 响应体片段 / AbortError，
- *      以及"已产出长度"的累加（文本/思维链/工具参数/块）；
- *   ③ 装配断言：`registerDeepSeekProvider` 里确实把 `onTransportFailure` 接上了 logger；
- *   ④ 覆盖断言：`failure.requestId` 会被写进 LlmError（从而随 `llm/retry` 落进会话日志）。
- *
- * 用法：`node scripts/patches/verify-transport-diagnostics.mjs`（只读，不碰任何 session 文件）
- */
-import { readFileSync, existsSync } from 'node:fs'
-import { requireDshScope } from '../lib/dsh-scope.mjs'
-
-// 0.6.0 F1 修复批（2026-10-14）：探不到 scope ⇒ 响亮失败（⛔ 不用假路径 —— 否则本脚本会
-// 一路"目标不在 ⇒ 跳过"，把"没验"报成"通过"）。
-let SCOPE
-try { SCOPE = requireDshScope({ what: '补丁校验（verify-transport-diagnostics）' }) }
-catch (e) { console.error(`  ❌ ${e.message}`); process.exit(1) }
-const TARGET = `${SCOPE}/dsh-llm-deepseek/lib/index.js`
-const LLM = `${SCOPE}/dsh-llm/lib/index.js`
-
-let pass = 0, fail = 0
-const ok = (c, n) => { c ? (pass++, console.log(`  ✅ ${n}`)) : (fail++, console.log(`  ❌ ${n}`)) }
-
-console.log('【TRANSPORT 诊断补丁】dsh-llm-deepseek/lib/index.js')
-
-if (!existsSync(TARGET)) {
-  ok(false, `目标存在（${TARGET}）`)
-} else {
-  const src = readFileSync(TARGET, 'utf8')
-
-  // ── ① 判定语义不变（这是补丁的红线：只加可观测字段，不动三分支）────────────────
-  console.log('\n  ── ① 判定语义未变 ──')
-  const catchBlock = (src.match(/\/\* Argent hotfix \(2026-10-02\)：\*\*判定不变\*\*[\s\S]*?\n\t\t\t\} finally \{/) || [''])[0]
-  ok(/Argent hotfix \(2026-10-02\)/.test(src), '补丁标记存在')
-  const branches = [
-    /if \(timeoutOf\(watchdog\.signal, "MESSAGES_IDLE"\) !== void 0\) throw new LlmError\("DeepSeek Messages stream idle timeout", "TIMEOUT", \{ cause: error \}\);/,
-    /if \(options\.signal\?\.aborted\) throw new LlmError\("DeepSeek Messages request aborted", "ABORTED", \{ cause: error \}\);/,
-    /if \(error instanceof LlmError\) throw error;/,
-  ]
-  ok(branches.every((re) => re.test(src)), 'TIMEOUT / ABORTED / LlmError-直通 三个分支**逐字未变**')
-  const order = [
-    src.indexOf('if (timeoutOf(watchdog.signal, "MESSAGES_IDLE") !== void 0) throw new LlmError("DeepSeek Messages stream idle timeout"'),
-    src.indexOf('if (options.signal?.aborted) throw new LlmError("DeepSeek Messages request aborted"'),
-    src.indexOf('if (error instanceof LlmError) throw error;'),
-  ]
-  ok(order.every((i) => i > -1) && order[0] < order[1] && order[1] < order[2],
-    `三分支**顺序不变**（TIMEOUT → ABORTED → LlmError 直通；实测 ${JSON.stringify(order)}）`)
-  ok(/throw new LlmError\("DeepSeek Messages transport failed", "TRANSPORT", \{/.test(src),
-    'TRANSPORT 仍是"其余一律"的兜底（message 与 code 逐字未变）')
-  ok(catchBlock !== '', 'catch 块里带"判定不变"注释（人改这里时会被提醒）')
-
-  // ── ② 行为断言：把补丁插入的纯函数取出来真跑 ────────────────────────────────
-  console.log('\n  ── ② cause 形态与"已产出长度"（真跑补丁插入的函数） ──')
-  const start = src.indexOf('let argentTransportCallSeq = 0;')
-  const end = src.indexOf('/** DeepSeek provider using Messages content and native thinking replay. */', start)
-  const body = start === -1 || end === -1 ? '' : src.slice(start, end)
-  let H = null
-  try {
-    H = new Function(`${body}
-const ProviderRequestId = (id) => id;
-return { argentTransportDiagnostics, argentRecordProducedChunk, argentProducedSummary, argentRequestIdOf, argentNoteResponse, argentNoteHttpFailure, argentDescribeTransportCause, argentTransportReport, argentTransportLogLine };`)()
-  } catch (e) { ok(false, `补丁函数可独立求值（${e.message}）`) }
-  ok(H !== null && typeof H.argentTransportReport === 'function',
-    '补丁插入的纯函数可独立求值（用它们做行为断言，不依赖完整 ctx）')
-
-  if (H !== null) {
-    const conn = { streamIdleTimeoutMs: 300000 }
-    const diagFor = (opts = { provider: 'whyshu', model: 'deepseek-flash' }) => H.argentTransportDiagnostics(opts, conn)
-    const resp = (status, headers = {}) => ({ status, headers: new Headers(headers) })
-
-    // ── cause 分类 ──
-    const cases = {
-      reset: Object.assign(new TypeError('fetch failed'), { cause: Object.assign(new Error('read ECONNRESET'), { code: 'ECONNRESET', errno: -54, syscall: 'read' }) }),
-      hangup: Object.assign(new Error('socket hang up'), { code: 'ECONNRESET' }),
-      etimedout: Object.assign(new Error('connect ETIMEDOUT 1.2.3.4:443'), { code: 'ETIMEDOUT', syscall: 'connect', errno: -60 }),
-      earlyClose: Object.assign(new TypeError('terminated'), { cause: Object.assign(new Error('other side closed'), { code: 'UND_ERR_SOCKET' }) }),
-      aborted: Object.assign(new Error('This operation was aborted'), { name: 'AbortError', code: 'ABORT_ERR' }),
-      refused: Object.assign(new TypeError('fetch failed'), { cause: Object.assign(new Error('connect ECONNREFUSED'), { code: 'ECONNREFUSED' }) }),
-    }
-    // `report.cause` = 描述 `error.cause ?? error` —— undici 常把真因藏在 cause 上，
-    // 所以断言一律走 report（这才是真正写进日志的那个形态）。
-    const kindOf = (e) => H.argentTransportReport(diagFor(), e, conn).cause.kind
-    const kinds = Object.fromEntries(Object.entries(cases).map(([k, e]) => [k, kindOf(e)]))
-    ok(kinds.reset === 'ECONNRESET', `ECONNRESET（undici 常见形态：TypeError fetch failed + cause.code）⇒ kind=${kinds.reset}`)
-    ok(kinds.hangup === 'ECONNRESET', `socket hang up ⇒ kind=${kinds.hangup}`)
-    ok(kinds.etimedout === 'ETIMEDOUT', `ETIMEDOUT ⇒ kind=${kinds.etimedout}`)
-    ok(kinds.earlyClose === 'EARLY_CLOSE', `提前关闭（terminated / other side closed / UND_ERR_SOCKET）⇒ kind=${kinds.earlyClose}`)
-    ok(H.argentTransportReport(diagFor(), cases.earlyClose, conn).causeChain[1]?.code === 'UND_ERR_SOCKET',
-      '内层原始 code（UND_ERR_SOCKET）仍逐字保留在 causeChain 里（kind 只是给人看的上位分类）')
-    ok(kinds.aborted === 'AbortError', `AbortError 可区分（不误判成网络错）⇒ kind=${kinds.aborted}`)
-    ok(kinds.refused === 'ECONNREFUSED', `ECONNREFUSED ⇒ kind=${kinds.refused}`)
-    // 单节点版只看自己：外层 `fetch failed` 没有 code 时归 FETCH_FAILED（链在 report.causeChain 里）
-    ok(H.argentDescribeTransportCause(cases.reset).kind === 'FETCH_FAILED',
-      '单节点描述不被内层 cause 污染（外层 fetch failed 归 FETCH_FAILED，真因在 causeChain 里）')
-    const chain = H.argentTransportReport(diagFor(), cases.reset, conn).causeChain
-    ok(chain.length === 2 && chain[0].kind === 'FETCH_FAILED' && chain[1].kind === 'ECONNRESET',
-      `cause 链被完整摊开（外层 fetch failed → 内层 ECONNRESET；实测 ${JSON.stringify(chain.map((c) => c.kind))}）`)
-    ok(chain[1].errno === '-54' && chain[1].syscall === 'read', 'errno/syscall 被带上（定位连接层用）')
-
-    // ── 已产出长度 ──
-    const d0 = diagFor()
-    const r0 = H.argentTransportReport(d0, cases.hangup, conn)
-    ok(r0.produced.chunks === 0 && r0.produced.anyOutput === false,
-      '**尚无任何输出**的回合：chunks=0 且 anyOutput=false（这正是"可安全重试"的判据）')
-
-    const d1 = diagFor()
-    H.argentRecordProducedChunk(d1, { type: 'block-start', index: 0, blockType: 'text' })
-    H.argentRecordProducedChunk(d1, { type: 'text-delta', index: 0, text: '你好世界' })
-    H.argentRecordProducedChunk(d1, { type: 'reasoning-delta', index: 1, text: '想一想' })
-    H.argentRecordProducedChunk(d1, { type: 'tool-call-delta', index: 2, id: 'c1', name: 'flow_failures', argumentsDelta: '{"flow":' })
-    const r1 = H.argentTransportReport(d1, cases.earlyClose, conn)
-    ok(r1.produced.chunks === 4 && r1.produced.anyOutput === true,
-      `**已产出内容**的回合被识别出来（${JSON.stringify(r1.produced)}）`)
-    ok(r1.produced.textChars === 4 && r1.produced.reasoningChars === 3 && r1.produced.toolCallChars === 8,
-      `分类计数正确：text=${r1.produced.textChars} reasoning=${r1.produced.reasoningChars} toolArgs=${r1.produced.toolCallChars}`)
-    ok(r1.produced.toolCallNames.length === 1 && r1.produced.toolCallNames[0] === 'flow_failures',
-      '工具名被记下（判断"是否已经开始产生副作用"用）')
-    H.argentRecordProducedChunk(d1, { type: 'finish', reason: { kind: 'stop' } })
-    ok(H.argentProducedSummary(d1).settled === true, 'finish/usage 会标记 settled')
-
-    // ── 请求标识（streamId）与 HTTP 状态 ──
-    const d2 = diagFor()
-    H.argentNoteResponse(d2, resp(200, { 'x-request-id': 'req-abc-123' }))
-    const r2 = H.argentTransportReport(d2, cases.earlyClose, conn)
-    ok(r2.requestId === 'req-abc-123' && r2.httpStatus === 200,
-      `响应头里的 provider 请求标识被抓到（requestId=${r2.requestId}, status=${r2.httpStatus}）`)
-    const d3 = diagFor()
-    H.argentNoteResponse(d3, resp(200, { 'request-id': 'rid-1' }))
-    H.argentNoteResponse(d3, resp(200, { 'x-deepseek-request-id': 'rid-2' }))
-    ok(H.argentRequestIdOf(new Headers({ 'request-id': 'a' })) === 'a'
-      && H.argentRequestIdOf(new Headers({ 'x-request-id': 'b' })) === 'b'
-      && H.argentRequestIdOf(new Headers({})) === undefined,
-      '三个头按同一优先级取值（request-id → x-request-id → x-deepseek-request-id）')
-
-    // ── 非 2xx + 响应体片段 ──
-    const d4 = diagFor()
-    H.argentNoteHttpFailure(d4, resp(502, { 'x-request-id': 'gw-1' }), '<html><body>502 Bad Gateway</body></html>')
-    const r4 = H.argentTransportReport(d4, Object.assign(new Error('invalid response status'), { code: 'HPE_INVALID_STATUS' }), conn)
-    ok(r4.httpStatus === 502 && /502 Bad Gateway/.test(r4.bodySnippet),
-      `非 2xx 的状态码与响应体片段被记下（status=${r4.httpStatus}, snippet=${JSON.stringify(r4.bodySnippet)}）`)
-    const longBody = 'x'.repeat(5000)
-    const d5 = diagFor()
-    H.argentNoteHttpFailure(d5, resp(500), longBody)
-    ok(H.argentTransportReport(d5, cases.hangup, conn).bodySnippet.length === 400,
-      '响应体片段被截断到 400 字符（不刷屏）')
-
-    // ── 日志行：可 grep + 关键字段齐全 ──
-    const line = H.argentTransportLogLine(r2)
-    ok(line.startsWith('[argent-transport] '), '日志行以固定前缀 `[argent-transport]` 开头（便于 grep）')
-    for (const field of ['route=whyshu/deepseek-flash', 'callId=', 'providerRequestId=req-abc-123', 'httpStatus=200', 'cause=EARLY_CLOSE', 'produced={chunks:', 'elapsedMs=', 'idleTimeoutMs=300000']) {
-      ok(line.includes(field), `日志行含字段 ${field}`)
-    }
-    ok(!line.includes('\n'), '单行输出（不会被日志系统按多行拆散）')
-    const line4 = H.argentTransportLogLine(r4)
-    ok(line4.includes('bodySnippet='), '非 2xx 时日志行附 bodySnippet')
-    const line0 = H.argentTransportLogLine(r0)
-    ok(line0.includes('providerRequestId=(none)') && line0.includes('httpStatus=(no response)'),
-      '连响应都没拿到时也明确标注 (none)/(no response)，不假装有值')
-  }
-
-  // ── ③ 装配：onTransportFailure 接到 logger ────────────────────────────────
-  console.log('\n  ── ③ 装配与落盘 ──')
-  ok(/onTransportFailure: \(report\) => \{/.test(src) && /ctx\.logger\.warn\(argentTransportLogLine\(report\)\)/.test(src),
-    'registerDeepSeekProvider 把 onTransportFailure 接到 ctx.logger.warn')
-  ok(/ctx\.logger\.warn\("llm-deepseek: TRANSPORT detail %o"/.test(src),
-    '同时打一份结构化 detail（%o，供日志详情/工具解析）')
-  ok(/this\.dependencies\.onTransportFailure\?\.\(transportReport\)/.test(src),
-    '适配器侧用可选链调用（第三方复用 registerDeepSeekProvider 时不会因缺回调而炸）')
-  ok(/\.\.\.transportReport\.requestId === void 0 \? \{\} : \{ requestId: transportReport\.requestId \}/.test(src),
-    'requestId 被写进 LlmError 的字段 ⇒ `failure.requestId` 随 `llm/retry` 事件落进会话日志')
-  ok(/const transportDiagnostics = argentTransportDiagnostics\(options, connection\);/.test(src)
-    && /argentRecordProducedChunk\(transportDiagnostics, next\.value\);/.test(src),
-    'generate() 里每产出一片就记一次（`yield` 之前，故计数与消费端所见一致）')
-
-  // ── ④ LlmError 真的保留 requestId（跨包契约，非本补丁可改）──────────────────
-  if (existsSync(LLM)) {
-    const llmSrc = readFileSync(LLM, 'utf8')
-    ok(/\.\.\.options\?\.requestId === void 0 \? \{\} : \{ requestId: options\.requestId \}/.test(llmSrc),
-      'dsh-llm 的 LlmError 会把 requestId 保留进 .failure（本补丁依赖该既有契约，未改动它）')
-    // 但"落进会话日志"还差三段链路，逐一钉住（否则 requestId 会停在内存里）：
-    //   适配器 throw ⇒ LlmRuntime 的 adapterFailureChunk 转成终态 finish 块
-    //   ⇒ normalizeLlmFailure 取 error.failure 快照 ⇒ failureSnapshot 白名单里必须有 requestId
-    ok(/function adapterFailureChunk\(error, signal\)/.test(llmSrc)
-      && /kind: "error",\s*\n\s*failure/.test(llmSrc),
-      '抛出的适配器错误被 LlmRuntime 转成终态 finish 块（这才是 `agent/request-error` 被触发的路径）')
-    ok(/function normalizeLlmFailure\(value\)/.test(llmSrc)
-      && /const carried = ownFailureSnapshot\(error\);\s*\n\s*if \(carried !== void 0 && carried\.code === ownErrorCode\(error\)\) return carried;/.test(llmSrc),
-      'normalizeLlmFailure 直接复用 LlmError 自带的 .failure 快照（code 一致时）—— requestId 不会被丢掉')
-    ok(/const requestId = candidate\.requestId;/.test(llmSrc)
-      && /\.\.\.requestId === void 0 \? \{\} : \{ requestId \}/.test(llmSrc),
-      'failureSnapshot 的白名单里有 requestId（也校验类型，非空字符串才放行）')
-    // 端到端（真造一个 LlmError，走同一段 normalize 逻辑）：确认 requestId 真的留在 failure 里
-    const { LlmError } = await import(LLM)
-    const probe = new LlmError('DeepSeek Messages transport failed', 'TRANSPORT', {
-      cause: new Error('read ECONNRESET'),
-      requestId: 'req_probe_1',
-    })
-    ok(probe.failure.requestId === 'req_probe_1' && probe.failure.code === 'TRANSPORT' && probe.failure.message === 'DeepSeek Messages transport failed',
-      `端到端：TRANSPORT 的 LlmError 带出 {code, message, requestId}（实测 ${JSON.stringify(probe.failure)}）`)
-    const noId = new LlmError('DeepSeek Messages transport failed', 'TRANSPORT', { cause: new Error('x') })
-    ok(noId.failure.requestId === undefined && Object.keys(noId.failure).sort().join(',') === 'code,message',
-      '没拿到请求标识时不会伪造：failure 仍是 {message, code}（与既有行为一致）')
-  }
-}
-
-console.log(`\n── 合计：通过 ${pass} / 失败 ${fail}`)
-if (fail > 0) {
-  console.log('❌ TRANSPORT 诊断补丁校验未通过：补丁可能没打上或上游已改动 —— 先别重启，见 docs / AGENTS.md')
-  process.exit(1)
-}
-console.log('✅ TRANSPORT 诊断补丁校验通过：cause / streamId / 已产出长度均可观测，判定语义未变')