agents-triager.html 42.4 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675
<!doctype html>
<html lang="zh-CN">
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width,initial-scale=1" />
<title>BugTriager Agent · 完整 Skill 规范 · LemonBoss PRD</title>
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,300;9..144,500;9..144,700&family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet" />
<link rel="stylesheet" href="assets/shell.css" />
</head>
<body data-page="agents-triager.html">
<div class="shell">
  <aside id="sidebar"></aside>
  <main class="page">
    <header class="page-head">
      <div class="crumb"><span class="pill">02 · DESIGN / Agents</span><span class="sep">/</span><span>BugTriager Agent</span></div>
      <h1>BugTriager Agent · 完整 Skill 规范</h1>
      <p class="deck">集成失败的法官。读 Integrator 给的 result.json + http-trace + 涉事 Unit 的 code/contract,决定<b>这是哪类问题、哪些 Unit 要 reset、SDD 是否需要改</b>。归因质量直接决定整个 L2 是否能收敛。</p>
    </header>
    <article class="body">

      <section>
        <div class="agent-hero">
          <div class="avatar" style="background:var(--L2-tint);color:var(--L2)">B</div>
          <div>
            <h2 style="margin:0">BugTriager Agent</h2>
            <p style="margin:6px 0">集成失败归因 · 4 类分类 · 提议 SDD 补丁 · confidence 评分</p>
            <div class="meta">
              <div><b>Loop</b> <span class="tag L2">L2</span></div>
              <div><b>Model</b> <b>Opus 4.7</b>(归因质量决定 L2 收敛性)</div>
              <div><b>Modes</b> triage · resume</div>
              <div><b>沙箱</b> 全项目只读 + integration/runs/{runId}/triage.json 写</div>
              <div><b>会话复用</b> 否</div>
            </div>
          </div>
        </div>
      </section>

      <section>
        <h2>① 功能需求</h2>
        <ol>
          <li><b>定位 root_cause:</b>用一句人话说清楚错在哪。<b>禁止</b>「测试失败」「需要修复」式废话。</li>
          <li><b>4 类归因,必选其一:</b>
            <ul style="padding-left:20px">
              <li><code>contract_mismatch</code> · SDD 双方契约不齐 → 必填 <code>proposed_sdd_patch</code></li>
              <li><code>impl_bug</code> · 代码没遵守 SDD → <b>不</b>改 SDD,只 reset Unit</li>
              <li><code>spec_ambiguous</code> · SDD 描述歧义 → 升 L3,等人</li>
              <li><code>infra_flake</code> · 端口/进程/网络等环境问题 → 直接重跑</li>
            </ul>
          </li>
          <li><b>影响面:</b><code>affected_units</code> 只列<b>需要重写</b>的 Unit;牵连但不必动的不列。</li>
          <li><b>confidence 评分:</b>0–1。<code>&lt; 0.5</code> 自动升 L3,不允许 LoopController 自动 apply。</li>
          <li><b>Evidence 必须可验证:</b>每条 evidence 来自原文件 grep,<code>extract_evidence</code> 工具校验,造假被拒。</li>
          <li><b>不动任何文件除 triage.json。</b>SDD 改由 Architect 在 patch 模式干。</li>
          <li><b>不调 Architect / 其他 Agent。</b>只产 triage.json,决定权交 LoopController。</li>
        </ol>
      </section>

      <section>
        <h2>② Skill 设计</h2>

        <h3>2.1 输出沙箱(极小)</h3>
<pre class="tree">
data/companies/{cid}/projects/{pid}/integration/runs/{runId}/
└── triage.json                <span class="com"># 唯一写入文件 ★</span>

<span class="com"># 只读 (无沙箱限制,需要看全部上下文做归因):</span>
integration/runs/{runId}/result.json
integration/runs/{runId}/process.log
integration/runs/{runId}/http-trace.ndjson
units.json
sdd/mvcp/**.html
units/*/code/**
units/*/contract.json
units/*/coder.log               <span class="com"># 看 Coder 之前怎么想的</span>
units/*/runs/*/result.json      <span class="com"># Tester 历史</span>
bugs.ndjson                     <span class="com"># 查相似历史 bug</span>
</pre>

        <h3>2.2 完整 System Prompt</h3>
        <p>落 <code>system/templates/devloop-triager.md</code>。LoopController 注入时头部补 <code>## Memory</code> + <code>## Failure Context</code>(含 result.json 节选 + 涉事 Unit 列表)。</p>

<pre class="code"><span class="c"># ROLE</span>
<span class="v">你是 LemonBoss DevLoop 的 BugTriager Agent。本次任务:分析集成测试失败 {runId}。</span>
<span class="v">读 Integrator 写的 result.json + process.log + http-trace,加上涉事 Unit 的</span>
<span class="v">code/contract/coder.log,产出 triage.json,决定下一步动作。</span>

<span class="v">你的归因是 L2 自愈的<b>核心判断</b>。错了会让项目陷入死循环或修错地方,</span>
<span class="v">所以宁可输出低 confidence 让人介入,也不要硬猜。</span>

<span class="c"># OUTPUT (唯一)</span>
<span class="v">integration/runs/{runId}/triage.json (M-9 schema)</span>

<span class="v">字段:</span>
<span class="v">  run_id              来自输入</span>
<span class="v">  root_cause          string, ≥20 字, 含具体行为</span>
<span class="v">  category            "contract_mismatch" | "impl_bug" | "spec_ambiguous" | "infra_flake"</span>
<span class="v">  affected_units      string[], 只列需要 reset 的</span>
<span class="v">  proposed_sdd_patch  object | null (仅 contract_mismatch 必填)</span>
<span class="v">  confidence          number 0..1</span>
<span class="v">  evidence            string[], 来自原文件的引文 (extract_evidence 校验)</span>

<span class="c"># MANDATORY WORKFLOW</span>

<span class="v">## step 0 · 收集证据</span>
<span class="v">  - 读 result.json failures[0] 的 stack/got/expected/involves</span>
<span class="v">  - 读 http-trace.ndjson 失败 case 完整调用链</span>
<span class="v">  - 读 process.log 失败时间窗口前后 50 行 (用 extract_evidence 工具)</span>
<span class="v">  - 对每个 involves Unit, 读 contract.json + coder.log + sdd section</span>

<span class="v">## step 1 · 写 todolist (4 项)</span>
<span class="v">  step-001 收集 4 类证据 (Integrator/SDD/code/历史)</span>
<span class="v">  step-002 用 category_classifier 做粗判 → 自己再审一遍</span>
<span class="v">  step-003 确定 affected_units (基于 involves + root_cause 精修)</span>
<span class="v">  step-004 (如 contract_mismatch) 起草 proposed_sdd_patch</span>
<span class="v">  step-005 写 triage.json + 自检 evidence grep-able</span>

<span class="c"># CATEGORY 判定流程图</span>

<span class="v">  start</span>
<span class="v">    │</span>
<span class="v">    ▼</span>
<span class="v">  stderr 含 EADDRINUSE/ECONNREFUSED/timeout? ──yes──> infra_flake</span>
<span class="v">    │ no</span>
<span class="v">    ▼</span>
<span class="v">  SDD 中相关行为有明确规定? ──no──> spec_ambiguous (升 L3)</span>
<span class="v">    │ yes</span>
<span class="v">    ▼</span>
<span class="v">  code 实现与 SDD 描述一致? ──no──> impl_bug</span>
<span class="v">    │ yes</span>
<span class="v">    ▼</span>
<span class="v">  involves 中两个 Unit 对同一契约理解不一? ──yes──> contract_mismatch</span>
<span class="v">    │ no</span>
<span class="v">    ▼</span>
<span class="v">  unknown → 升 L3 (confidence ≤ 0.4)</span>

<span class="c"># CATEGORY 详细判定准则</span>

<span class="v">[contract_mismatch]</span>
<span class="v">  特征: A Unit 的 contract.json 与 B Unit 的 contract.json (或 SDD) 对同一</span>
<span class="v">        endpoint 的 status/body 表达不一</span>
<span class="v">  典型: auth-be contract 写 "401 invalid_credentials"</span>
<span class="v">        但 SDD 描述写 "403 forbidden"</span>
<span class="v">        auth-fe 期望 403,所以 401 时不工作</span>
<span class="v">  必填: proposed_sdd_patch (统一双方,通常修正 SDD)</span>

<span class="v">[impl_bug]</span>
<span class="v">  特征: SDD 明确写了 X,code 没遵守 (做了 Y 或漏做)</span>
<span class="v">  典型: SDD 写 "user 不存在返 404", code 写 throw new Error()</span>
<span class="v">  proposed_sdd_patch: null (不改 SDD)</span>
<span class="v">  affected_units: 仅那一个</span>

<span class="v">[spec_ambiguous]</span>
<span class="v">  特征: SDD 没写、写得模糊、双解</span>
<span class="v">  典型: SDD 没规定 token 过期后是否自动刷新</span>
<span class="v">  proposed_sdd_patch: null (Architect 不该自己猜)</span>
<span class="v">  confidence: 通常 ≤ 0.5 → 升 L3</span>

<span class="v">[infra_flake]</span>
<span class="v">  特征: 端口冲突、网络超时、进程未起、磁盘满</span>
<span class="v">  典型: stderr 含 EADDRINUSE / ETIMEDOUT</span>
<span class="v">  proposed_sdd_patch: null</span>
<span class="v">  affected_units: [] (直接重跑就行)</span>

<span class="c"># RULES (硬约束)</span>

<span class="v">1. 永远不动任何文件,除 triage.json。Architect 才有改 SDD 的权限。</span>

<span class="v">2. root_cause 必须含具体行为。反例(禁):</span>
<span class="v">     ✗ "测试失败"</span>
<span class="v">     ✗ "auth-be 有问题"</span>
<span class="v">     ✗ "需要修复"</span>
<span class="v">   正例:</span>
<span class="v">     ✓ "auth-be 在 user 不存在时抛 TypeError 返 500,</span>
<span class="v">         但 auth-fe 期望 401 (SDD 规定)"</span>

<span class="v">3. evidence 列表的每条必须能在原文件 grep 到。extract_evidence 工具校验,</span>
<span class="v">   命中失败 → 拒收 triage.json。</span>

<span class="v">4. confidence:</span>
<span class="v">     0.9+ : 证据非常清晰</span>
<span class="v">     0.7-0.9: 主要证据齐,有少量推断</span>
<span class="v">     0.5-0.7: 几条解释都说得通,选一个最可能的</span>
<span class="v">     &lt;0.5: 不确定,自动升 L3 (LoopController 不 auto-apply)</span>

<span class="v">5. category=contract_mismatch 必填 proposed_sdd_patch,</span>
<span class="v">   = impl_bug / spec_ambiguous / infra_flake 必为 null。</span>

<span class="v">6. affected_units:</span>
<span class="v">     contract_mismatch: 通常 ≥2 个 (双方都要重写)</span>
<span class="v">     impl_bug: 通常 1 个</span>
<span class="v">     spec_ambiguous: [] (等 L3 决策后才知道)</span>
<span class="v">     infra_flake: []</span>

<span class="v">7. 不调 call_sub_agent,不写 timeline (LoopController 接管后写)。</span>

<span class="c"># SELF-CHECK</span>
<span class="v">1. triage.json 通过 typebox (M-9)</span>
<span class="v">2. root_cause ≥ 20 字 + 含具体行为词 (返/抛/收/写/读 之一)</span>
<span class="v">3. evidence 每条用 extract_evidence 工具校验 → 全 ok=true</span>
<span class="v">4. category 与 proposed_sdd_patch null 性匹配 (见 §RULES 5)</span>
<span class="v">5. confidence 与 category 合理 (impl_bug 通常 &gt;0.7, spec_ambiguous &lt;0.6)</span>
<span class="v">6. affected_units 引用都在 units.json 中</span></pre>

        <h3>2.3 工具集</h3>
        <table>
          <thead><tr><th>工具</th><th>签名</th><th>用途</th><th>访问</th></tr></thead>
          <tbody>
            <tr><td><code>Read</code></td><td>(path)</td><td>读全项目(只读)</td><td>项目内</td></tr>
            <tr><td><code>Grep</code></td><td>(pattern, path)</td><td>在 code/ / log 中找证据</td><td>项目内</td></tr>
            <tr><td><code>Write</code></td><td>(path, content)</td><td>仅 triage.json</td><td>白名单</td></tr>
            <tr><td><code>extract_evidence</code> <span class="tag NEW">NEW</span></td><td>(pid, evidence: string[]) → {ok, results[], failed[]}</td><td>验证每条 evidence 是否能在 "{file_path}: 引文" 格式中 grep 命中</td><td>—</td></tr>
            <tr><td><code>category_classifier</code> <span class="tag NEW">NEW</span></td><td>(context) → {category, confidence, hints}</td><td>启发式粗判(基于 stderr 关键词 + SDD 一致性扫描)</td><td>—</td></tr>
            <tr><td><code>diff_contract_vs_impl</code> <span class="tag NEW">NEW</span></td><td>(pid, unitId) → {matches, divergences[]}</td><td>code 实际行为 vs contract.json 声明的差异</td><td>—</td></tr>
            <tr><td><code>find_similar_bug</code> <span class="tag NEW">NEW</span></td><td>(pid, signature) → Bug[]</td><td>在 bugs.ndjson 中查相似历史,提升判断准度</td><td>—</td></tr>
            <tr><td><code>write_todolist · update_todo_item · update_runtime_state · timeline_append · record_memory</code></td><td>同上</td><td>持久化</td><td>agent-state/</td></tr>
          </tbody>
        </table>

        <h3>2.4 禁用</h3>
        <div class="callout warn">
          <ul style="margin:0">
            <li><b>不允许 Edit / Write 任何文件</b> 除 triage.json</li>
            <li><b>不允许 Bash</b> — 全 Read/Grep 即可,不需要跑命令</li>
            <li><b>不允许 call_sub_agent</b></li>
            <li><b>不允许造假 evidence</b> — 必须能 grep 命中原文</li>
            <li><b>不允许在 root_cause 用废话</b>(「测试失败」等被自检拒)</li>
          </ul>
        </div>
      </section>

      <section>
        <h2>③ 持久化集成</h2>
        <p>同模式但<b>会话不复用</b>(每次新归因独立)。memory 是 BugTriager 最有价值的累积资产,典型话题:</p>
        <ul>
          <li>"EADDRINUSE 永远是 infra_flake 不是 impl_bug"</li>
          <li>"401 vs 403:401 是凭据无效,403 是有凭据但权限不够"</li>
          <li>"impl_bug 出现 ≥2 次 → 升级为 spec_ambiguous(SDD 描述不够清晰)"</li>
          <li>"vitest 退出码 1 但 raw.json 空 → 测试框架本身崩 = infra_flake"</li>
        </ul>
      </section>

      <section>
        <h2>④ I/O 契约</h2>
<pre class="code"><span class="k">const</span> TriagerInput = Type.<span class="n">Object</span>(<span class="p">{</span>
  pid:        Type.<span class="n">String</span>(),
  run_id:     Type.<span class="n">String</span>(),       <span class="c">// 哪一轮集成失败</span>
  mode:       Type.<span class="n">Union</span>(<span class="p">[</span>Type.<span class="n">Literal</span>(<span class="s">'triage'</span>), Type.<span class="n">Literal</span>(<span class="s">'resume'</span>)<span class="p">]</span>),
  resume_token: Type.<span class="n">Optional</span>(Type.<span class="n">String</span>()),
  call_id:    Type.<span class="n">String</span>(),
  company_id: Type.<span class="n">String</span>(),
<span class="p">}</span>);

<span class="k">const</span> TriagerOutput = Type.<span class="n">Object</span>(<span class="p">{</span>
  ok:           Type.<span class="n">Boolean</span>(),     <span class="c">// 总能产出,除非崩;ok=false 仅指 triage 本身有缺陷</span>
  run_id:       Type.<span class="n">String</span>(),
  triage_ref:   Type.<span class="n">String</span>(),     <span class="c">// path to triage.json</span>

  category:     Type.<span class="n">String</span>(),
  confidence:   Type.<span class="n">Number</span>(),
  affected_units: Type.<span class="n">Array</span>(Type.<span class="n">String</span>()),
  will_auto_apply: Type.<span class="n">Boolean</span>(),  <span class="c">// true 当 confidence≥0.5 且 category 允许</span>

  evidence_verified: Type.<span class="n">Boolean</span>(),   <span class="c">// 所有 evidence grep 命中</span>
  duration_ms:  Type.<span class="n">Number</span>(),
  tokens_used:  Type.<span class="n">Number</span>(),
<span class="p">}</span>);</pre>
      </section>

      <section>
        <h2>⑤ 上下游传递</h2>
        <div class="io-grid">
          <div class="io-box">
            <h4>⬆ 上游</h4>
            <ul>
              <li><b>Integrator</b> · result.json · process.log · http-trace.ndjson</li>
              <li><b>Architect</b>(间接)· sdd/ · units.json · integration/spec.json</li>
              <li><b>所有 Coder</b>(间接)· code/** · contract.json · coder.log</li>
              <li><b>Tester</b>(间接)· 历史 result.json</li>
              <li><b>BugTracker</b>(间接)· bugs.ndjson 历史</li>
              <li><b>LoopController</b> · TriagerInput</li>
            </ul>
          </div>
          <div class="io-box">
            <h4>⬇ 下游</h4>
            <ul>
              <li><b>LoopController</b> · 读 triage.json 决定 ① apply patch 走 Architect ② 仅 reset Unit ③ 重跑 Integrator ④ 升 L3</li>
              <li><b>Architect</b>(如果 will_auto_apply=true)· mode=patch + triage.json 输入</li>
              <li><b>UnitRegistry</b> · reset affected_units</li>
              <li><b>Human (L3)</b>(如 confidence&lt;0.5)· SSE human_intervention_needed</li>
              <li><b>BugTracker</b>(间接)· LoopController 改 bug.category 字段(unknown → 实际值)</li>
            </ul>
          </div>
        </div>
      </section>

      <section>
        <h2>⑥ 完整执行样例</h2>

        <div class="tabs" data-tabs>
          <div class="tabbar" role="tablist">
            <button role="tab" aria-selected="true"  aria-controls="ba">Sample A · contract_mismatch</button>
            <button role="tab" aria-selected="false" aria-controls="bb">Sample B · impl_bug</button>
            <button role="tab" aria-selected="false" aria-controls="bc">Sample C · spec_ambiguous (升 L3)</button>
          </div>

          <div class="tabpanel" id="ba">
<pre class="code"><span class="c"># INPUT</span>
<span class="p">{</span>
  <span class="n">"pid"</span>: <span class="s">"p-test001"</span>,
  <span class="n">"run_id"</span>: <span class="s">"run-int-20260513-1230"</span>,
  <span class="n">"mode"</span>: <span class="s">"triage"</span>, ...
<span class="p">}</span>

<span class="c"># 读 result.json:</span>
<span class="c">#   failure: case "login-then-profile" step 1 fail</span>
<span class="c">#   involves: ["auth-be","profile-be"]</span>
<span class="c">#   got: { status: 200, body: { user_id: 'demo' } }</span>
<span class="c">#   expected: { status: 401 }</span>

<span class="c"># step 1 · 收证据</span>
<span class="c">#  从 http-trace:</span>
<span class="c">#    step 0: POST /api/auth/login → 200 { token: "expired-jwt..." }</span>
<span class="c">#            (注意:token 是测试 fixture 写死,故意过期)</span>
<span class="c">#    step 1: GET /api/profile/me with expired token → 200  ✗ 应 401</span>

<span class="c">#  读 sdd/mvcp/control.html data-unit-id="profile-be":</span>
<span class="c">#    <pre data-contract>... 401 if token expired ...</pre></span>

<span class="c">#  读 profile-be/contract.json:</span>
<span class="c">#    responses: { "200": ..., "404": ... }   ← 没有 401!</span>

<span class="c">#  读 profile-be/code/server.js:</span>
<span class="c">#    没有 JWT 校验,直接信任 Authorization header,从 token 取 user_id</span>

<span class="c"># step 2 · category_classifier</span>
category_classifier(...) → <span class="p">{</span> category: <span class="s">"contract_mismatch"</span>, confidence: <span class="v">0.82</span> <span class="p">}</span>
<span class="c">// 但等等:这是 contract_mismatch 还是 impl_bug?</span>
<span class="c">//   SDD 说要 401, contract.json 没说 → contract 与 SDD 不齐 → contract_mismatch</span>
<span class="c">//   (而非 impl_bug:实现没遵守 contract 的话才是 impl_bug)</span>

<span class="c"># step 3 · affected_units = ["profile-be"]</span>
<span class="c">#   auth-be 不动:它的契约本来就对 (返 token)</span>

<span class="c"># step 4 · 起草 patch</span>
proposed_sdd_patch = <span class="p">{</span>
  target_section: <span class="s">"#unit-profile-be"</span>,
  op: <span class="s">"update_contract"</span>,
  text: <span class="s">"明确:接收 Authorization 头,验证 JWT,失败返 401 invalid_token"</span>
<span class="p">}</span>

<span class="c"># step 5 · 写 triage.json</span>
<span class="p">{</span>
  <span class="n">"run_id"</span>: <span class="s">"run-int-20260513-1230"</span>,
  <span class="n">"root_cause"</span>: <span class="s">"profile-be 没校验 JWT 直接信任 Authorization 头,过期 token 收到 200 而非 SDD 规定的 401"</span>,
  <span class="n">"category"</span>: <span class="s">"contract_mismatch"</span>,
  <span class="n">"affected_units"</span>: <span class="p">[</span><span class="s">"profile-be"</span><span class="p">]</span>,
  <span class="n">"proposed_sdd_patch"</span>: <span class="p">{</span>
    <span class="n">"target_section"</span>: <span class="s">"#unit-profile-be"</span>,
    <span class="n">"op"</span>: <span class="s">"update_contract"</span>,
    <span class="n">"text"</span>: <span class="s">"明确:验证 JWT,过期返 401 invalid_token"</span>
  <span class="p">}</span>,
  <span class="n">"confidence"</span>: <span class="v">0.82</span>,
  <span class="n">"evidence"</span>: <span class="p">[</span>
    <span class="s">"sdd/mvcp/control.html: '401 if token expired'"</span>,
    <span class="s">"profile-be/contract.json: responses 仅含 200/404,无 401"</span>,
    <span class="s">"profile-be/code/server.js:23: 无 jwt.verify 调用"</span>,
    <span class="s">"http-trace step 1: expired token returns 200 not 401"</span>
  <span class="p">]</span>
<span class="p">}</span>

<span class="c"># OUTPUT</span>
<span class="p">{</span>
  <span class="n">"ok"</span>: <span class="v">true</span>, <span class="n">"category"</span>: <span class="s">"contract_mismatch"</span>,
  <span class="n">"confidence"</span>: <span class="v">0.82</span>, <span class="n">"affected_units"</span>: <span class="p">[</span><span class="s">"profile-be"</span><span class="p">]</span>,
  <span class="n">"will_auto_apply"</span>: <span class="v">true</span>,
  <span class="n">"evidence_verified"</span>: <span class="v">true</span>,
  <span class="n">"duration_ms"</span>: <span class="v">28_412</span>, <span class="n">"tokens_used"</span>: <span class="v">9_823</span>
<span class="p">}</span>

<span class="c"># LoopController → callAgent('architect', { mode:'patch', triage:{...} })</span></pre>
          </div>

          <div class="tabpanel" id="bb" hidden>
<pre class="code"><span class="c"># INPUT 同样,但实际场景不同</span>

<span class="c"># 读发现:</span>
<span class="c">#   sdd 明确写: "user 不存在返 404 with {error:'user_not_found'}"</span>
<span class="c">#   contract.json 也写: responses: { "200": ..., "404": ... } ✓</span>
<span class="c">#   code/server.js: user 查不到时 throw new Error('not found') → 500</span>

<span class="c"># 这是<b>实现没遵守 SDD</b>,不是契约不齐</span>

<span class="c"># triage.json</span>
<span class="p">{</span>
  <span class="n">"run_id"</span>: <span class="s">"..."</span>,
  <span class="n">"root_cause"</span>: <span class="s">"profile-be 在 user 不存在时抛 throw 错误返 500,SDD 已规定该返 404 user_not_found"</span>,
  <span class="n">"category"</span>: <span class="s">"impl_bug"</span>,                    <span class="c">// 不是 contract_mismatch</span>
  <span class="n">"affected_units"</span>: <span class="p">[</span><span class="s">"profile-be"</span><span class="p">]</span>,
  <span class="n">"proposed_sdd_patch"</span>: <span class="v">null</span>,                   <span class="c">// impl_bug 不改 SDD</span>
  <span class="n">"confidence"</span>: <span class="v">0.93</span>,                          <span class="c">// 证据非常清晰</span>
  <span class="n">"evidence"</span>: <span class="p">[</span>
    <span class="s">"sdd/mvcp/control.html: '404 with {error:user_not_found}'"</span>,
    <span class="s">"profile-be/contract.json responses 404 已声明"</span>,
    <span class="s">"profile-be/code/server.js:41: throw new Error('not found')"</span>,
    <span class="s">"http-trace step 1: got 500"</span>
  <span class="p">]</span>
<span class="p">}</span>

<span class="c"># LoopController → 不改 SDD, 只 unitRegistry.reset(['profile-be'])</span>
<span class="c">#                  → L1 重跑 profile-be (Coder 反思: SDD 写 404 我做了 throw, 这次改)</span></pre>
          </div>

          <div class="tabpanel" id="bc" hidden>
<pre class="code"><span class="c"># INPUT 同样</span>

<span class="c"># 读发现:</span>
<span class="c">#   失败 case: token 过期 fe 应自动刷新, 但 SDD 没说</span>
<span class="c">#   sdd 关于 token 续期: 没找到 → 翻 prd: 也没说</span>
<span class="c">#   auth-fe/code: 实现了自动刷新, 但没说收到 401 后等多久重试</span>
<span class="c">#   auth-be/code: 接收 refresh_token 也行, 没接收也行 (双解)</span>

<span class="c"># 这种"双方都说得通,SDD 没规定"的情况 = spec_ambiguous</span>

<span class="c"># triage.json</span>
<span class="p">{</span>
  <span class="n">"run_id"</span>: <span class="s">"..."</span>,
  <span class="n">"root_cause"</span>: <span class="s">"SDD 未规定 token 过期后 fe 是否自动刷新及刷新策略,auth-fe 实现刷新 1 次后放弃,auth-be 同时接收 refresh_token 与重新登录两种方式"</span>,
  <span class="n">"category"</span>: <span class="s">"spec_ambiguous"</span>,
  <span class="n">"affected_units"</span>: <span class="p">[]</span>,                            <span class="c">// 等人决策后才知道</span>
  <span class="n">"proposed_sdd_patch"</span>: <span class="v">null</span>,
  <span class="n">"confidence"</span>: <span class="v">0.42</span>,                              <span class="c">// &lt; 0.5 → 升 L3</span>
  <span class="n">"evidence"</span>: <span class="p">[</span>
    <span class="s">"sdd/mvcp/control.html: 搜 'refresh' 0 命中"</span>,
    <span class="s">"prd/product/scope.html: 同上 0 命中"</span>,
    <span class="s">"auth-fe/code/auth-service.js:67: setTimeout 重试 1 次"</span>,
    <span class="s">"auth-be/code/server.js:34: 接收 grant_type=refresh_token"</span>
  <span class="p">]</span>,
  <span class="n">"l3_question"</span>: <span class="s">"Token 过期后:(A) fe 自动刷新 ≤3 次 (B) 提示用户重新登录 (C) 静默续期不感知"</span>
<span class="p">}</span>

<span class="c"># LoopController: confidence&lt;0.5 + category=spec_ambiguous</span>
<span class="c">#                 → SSE human_intervention_needed with l3_question</span>
<span class="c">#                 → 不动 Unit,不改 SDD,等人</span></pre>
          </div>
        </div>
      </section>

      <section>
        <h2>⑦ 助手工具源码</h2>

        <h3>7.1 <code>extract-evidence.js</code> · evidence 真伪验证</h3>
<pre class="code"><span class="c">// server/services/agent-tools/extract-evidence.js · ~60 行</span>
<span class="k">const</span> fs   = <span class="n">require</span>(<span class="s">'fs'</span>);
<span class="k">const</span> path = <span class="n">require</span>(<span class="s">'path'</span>);

<span class="c">/**
 * 验证一条 evidence 是否能在 sources 中 grep 命中。
 * evidence 格式约定: "{file_path}: {引文}"
 * 例如: "sdd/mvcp/control.html: '401 if token expired'"
 */</span>
<span class="k">function</span> <span class="n">verifyOne</span>(pid, evidence) <span class="p">{</span>
  <span class="k">const</span> sep = evidence.<span class="n">indexOf</span>(<span class="s">': '</span>);
  <span class="k">if</span> (sep &lt; <span class="v">0</span>) <span class="k">return</span> <span class="p">{</span> ok: <span class="v">false</span>, reason: <span class="s">'malformed: need "path: quote"'</span> <span class="p">}</span>;

  <span class="k">const</span> relPath = evidence.<span class="n">slice</span>(<span class="v">0</span>, sep).<span class="n">replace</span>(<span class="s">/^['"]|['"]$/g</span>, <span class="s">''</span>);
  <span class="k">const</span> quote   = evidence.<span class="n">slice</span>(sep + <span class="v">2</span>).<span class="n">replace</span>(<span class="s">/^['"]|['"]$/g</span>, <span class="s">''</span>);
  <span class="k">const</span> abs     = path.<span class="n">join</span>(<span class="n">projectsDir</span>(pid), relPath);

  <span class="k">if</span> (!fs.<span class="n">existsSync</span>(abs))
    <span class="k">return</span> <span class="p">{</span> ok: <span class="v">false</span>, reason: <span class="s">'file not found: '</span> + relPath <span class="p">}</span>;

  <span class="k">const</span> content = fs.<span class="n">readFileSync</span>(abs, <span class="s">'utf8'</span>);

  <span class="c">// 模糊匹配:去掉过多空白后 includes 即可</span>
  <span class="k">const</span> norm = (s) =&gt; s.<span class="n">replace</span>(<span class="s">/\s+/g</span>, <span class="s">' '</span>).<span class="n">toLowerCase</span>();
  <span class="k">if</span> (<span class="n">norm</span>(content).<span class="n">includes</span>(<span class="n">norm</span>(quote)))
    <span class="k">return</span> <span class="p">{</span> ok: <span class="v">true</span>, hit_file: relPath <span class="p">}</span>;

  <span class="c">// 行号格式 "path:lineno: 引文" 也支持</span>
  <span class="k">const</span> lineMatch = relPath.<span class="n">match</span>(<span class="s">/^(.+):(\d+)$/</span>);
  <span class="k">if</span> (lineMatch) <span class="p">{</span>
    <span class="k">const</span> lines = content.<span class="n">split</span>(<span class="s">'\n'</span>);
    <span class="k">const</span> line  = lines[<span class="n">parseInt</span>(lineMatch[<span class="v">2</span>],<span class="v">10</span>)-<span class="v">1</span>] || <span class="s">''</span>;
    <span class="k">if</span> (<span class="n">norm</span>(line).<span class="n">includes</span>(<span class="n">norm</span>(quote)))
      <span class="k">return</span> <span class="p">{</span> ok: <span class="v">true</span>, hit_file: lineMatch[<span class="v">1</span>], line: lineMatch[<span class="v">2</span>] <span class="p">}</span>;
  <span class="p">}</span>

  <span class="k">return</span> <span class="p">{</span> ok: <span class="v">false</span>, reason: <span class="s">'quote not found in file'</span>, quote, file: relPath <span class="p">}</span>;
<span class="p">}</span>

<span class="k">function</span> <span class="n">verifyAll</span>(pid, evidenceList) <span class="p">{</span>
  <span class="k">const</span> results = evidenceList.<span class="n">map</span>(e =&gt; (<span class="p">{</span> evidence: e, ...<span class="n">verifyOne</span>(pid, e) <span class="p">}</span>));
  <span class="k">return</span> <span class="p">{</span>
    ok: results.<span class="n">every</span>(r =&gt; r.ok),
    results,
    failed: results.<span class="n">filter</span>(r =&gt; !r.ok),
  <span class="p">}</span>;
<span class="p">}</span>

module.<span class="n">exports</span> = <span class="p">{</span> verifyOne, verifyAll <span class="p">}</span>;</pre>

        <h3>7.2 <code>category-classifier.js</code> · 启发式粗判(Agent 还要审)</h3>
<pre class="code"><span class="c">// server/services/agent-tools/category-classifier.js · ~80 行</span>
<span class="k">const</span> fs = <span class="n">require</span>(<span class="s">'fs'</span>);
<span class="k">const</span> path = <span class="n">require</span>(<span class="s">'path'</span>);

<span class="k">function</span> <span class="n">classify</span>(<span class="p">{</span> resultJson, processLog, sddText, codeTexts <span class="p">}</span>) <span class="p">{</span>
  <span class="k">const</span> hints = <span class="p">[]</span>;
  <span class="k">let</span> score = <span class="p">{</span> contract_mismatch:<span class="v">0</span>, impl_bug:<span class="v">0</span>, spec_ambiguous:<span class="v">0</span>, infra_flake:<span class="v">0</span> <span class="p">}</span>;

  <span class="c">// 1) infra_flake 信号 (强)</span>
  <span class="k">const</span> infraSignals = <span class="p">[</span>
    <span class="s">/EADDRINUSE/</span>, <span class="s">/ECONNREFUSED/</span>, <span class="s">/ETIMEDOUT/</span>,
    <span class="s">/EAI_AGAIN/</span>, <span class="s">/Cannot find module/</span>,
    <span class="s">/port already in use/i</span>, <span class="s">/health check timeout/i</span>,
  <span class="p">]</span>;
  <span class="k">if</span> (infraSignals.<span class="n">some</span>(re =&gt; re.<span class="n">test</span>(processLog))) <span class="p">{</span>
    score.infra_flake += <span class="v">3</span>;
    hints.<span class="n">push</span>(<span class="s">'infra signal in process.log'</span>);
  <span class="p">}</span>

  <span class="c">// 2) spec_ambiguous 信号</span>
  <span class="c">//    失败行为相关关键词在 sdd 中找不到 → 强信号</span>
  <span class="k">const</span> failTokens = <span class="n">extractKeyTokens</span>(resultJson);   <span class="c">// "refresh", "token expire", etc</span>
  <span class="k">const</span> sddLc = sddText.<span class="n">toLowerCase</span>();
  <span class="k">const</span> tokensNotInSdd = failTokens.<span class="n">filter</span>(t =&gt; !sddLc.<span class="n">includes</span>(t.<span class="n">toLowerCase</span>()));
  <span class="k">if</span> (tokensNotInSdd.<span class="n">length</span> &gt;= <span class="v">2</span>) <span class="p">{</span>
    score.spec_ambiguous += <span class="v">2</span>;
    hints.<span class="n">push</span>(<span class="s">'key tokens not found in SDD: '</span> + tokensNotInSdd.<span class="n">join</span>(<span class="s">','</span>));
  <span class="p">}</span>

  <span class="c">// 3) contract_mismatch 信号: sdd 说一个 status, contract.json 说另一个</span>
  <span class="c">//    (实现细节略)</span>

  <span class="c">// 4) impl_bug 信号: sdd 明确 + contract 明确 + code 不符</span>
  <span class="c">//    用 5xx in got + 4xx in expected 是强信号</span>
  <span class="k">const</span> got    = resultJson?.failures?.[<span class="v">0</span>]?.got;
  <span class="k">const</span> expect = resultJson?.failures?.[<span class="v">0</span>]?.expect;
  <span class="k">if</span> (got?.status &gt;= <span class="v">500</span> &amp;&amp; expect?.status &gt;= <span class="v">400</span> &amp;&amp; expect?.status &lt; <span class="v">500</span>) <span class="p">{</span>
    score.impl_bug += <span class="v">2</span>;
    hints.<span class="n">push</span>(<span class="s">'5xx got vs 4xx expected → impl_bug'</span>);
  <span class="p">}</span>

  <span class="c">// 选最高分</span>
  <span class="k">const</span> sorted = <span class="n">Object.entries</span>(score).<span class="n">sort</span>(([,a],[,b]) =&gt; b-a);
  <span class="k">const</span> [topCat, topScore] = sorted[<span class="v">0</span>];

  <span class="c">// confidence 启发式</span>
  <span class="k">let</span> confidence;
  <span class="k">if</span> (topScore &gt;= <span class="v">3</span>)      confidence = <span class="v">0.85</span>;
  <span class="k">else</span> <span class="k">if</span> (topScore === <span class="v">2</span>) confidence = <span class="v">0.65</span>;
  <span class="k">else</span> <span class="k">if</span> (topScore === <span class="v">1</span>) confidence = <span class="v">0.45</span>;
  <span class="k">else</span>                  confidence = <span class="v">0.30</span>;

  <span class="k">return</span> <span class="p">{</span> category: topCat, confidence, hints, score <span class="p">}</span>;
<span class="p">}</span>

<span class="k">function</span> <span class="n">extractKeyTokens</span>(rj) <span class="p">{</span>
  <span class="k">const</span> txt = <span class="n">JSON.stringify</span>(rj || <span class="p">{}</span>);
  <span class="c">// 去掉 stack 中的 path/random 字符,取 4 字以上小写单词</span>
  <span class="k">return</span> <span class="p">[</span>...<span class="k">new</span> <span class="n">Set</span>(txt.<span class="n">toLowerCase</span>().<span class="n">match</span>(<span class="s">/[a-z]{4,}/g</span>) || <span class="p">[]</span>)<span class="p">]</span>
    .<span class="n">filter</span>(t =&gt; !<span class="p">[</span><span class="s">'function'</span>,<span class="s">'expected'</span>,<span class="s">'received'</span>,<span class="s">'stack'</span>,<span class="s">'message'</span><span class="p">]</span>.<span class="n">includes</span>(t));
<span class="p">}</span>

module.<span class="n">exports</span> = <span class="p">{</span> classify <span class="p">}</span>;</pre>

        <p class="sig">这是「<b>启发式建议</b>」工具,Agent 必须自己审一遍再写 triage.json。category_classifier 给的 confidence 仅是参考,Agent 输出的 confidence 是基于自己 reasoning 的最终判断。</p>
      </section>

      <section>
        <h2>⑧ 自检 Checklist</h2>
        <table>
          <thead><tr><th>#</th><th>检查项</th><th>命令</th><th>判定</th></tr></thead>
          <tbody>
            <tr><td>1</td><td>triage.json typebox 合规</td><td>schema check (M-9)</td><td>true</td></tr>
            <tr><td>2</td><td>root_cause ≥ 20 字</td><td>length</td><td>true</td></tr>
            <tr><td>3</td><td>root_cause 含行为动词(返/抛/收/写/读/超时之一)</td><td>regex</td><td>命中</td></tr>
            <tr><td>4</td><td>所有 evidence grep 命中</td><td><code>verifyAll(pid, evidence)</code></td><td>ok=true</td></tr>
            <tr><td>5</td><td>category × proposed_sdd_patch null 一致</td><td>逻辑</td><td>contract_mismatch ⇔ patch≠null</td></tr>
            <tr><td>6</td><td>category × confidence 合理</td><td>spec_ambiguous &lt;0.6, impl_bug typically &gt;0.7</td><td>无明显错配</td></tr>
            <tr><td>7</td><td>affected_units ⊆ units.json</td><td>set 包含</td><td>true</td></tr>
            <tr><td>8</td><td>category 非 unknown</td><td>必为 4 选 1</td><td>true</td></tr>
            <tr><td>9</td><td>todolist 全 done</td><td>read</td><td>true</td></tr>
            <tr><td>10</td><td>没写 triage.json 之外的文件</td><td>scanSandbox</td><td>violations=[]</td></tr>
          </tbody>
        </table>
        <p class="sig">任一不过 → 不写 triage.json,retry 1 次。仍不过 → 写一个 confidence=0.3 + category='spec_ambiguous' 的兜底版升 L3。</p>
      </section>

      <section>
        <h2>⑨ 失败模式</h2>
        <table class="dense">
          <thead><tr><th>场景</th><th>处置</th></tr></thead>
          <tbody>
            <tr><td>evidence 引文找不到原文</td><td>extract_evidence 拒;Triager 重生这条 evidence</td></tr>
            <tr><td>category 选错(后续 L2 再次失败)</td><td>第 2 次 triage 自动升 spec_ambiguous(避免死循环)</td></tr>
            <tr><td>root_cause 是「测试失败」类废话</td><td>self-check 3 拒</td></tr>
            <tr><td>affected_units 空 + category=impl_bug</td><td>不合法,拒;Triager 必须列至少 1 个</td></tr>
            <tr><td>proposed_sdd_patch 写错 target_section</td><td>Architect 应用时报错,Triager 重生</td></tr>
            <tr><td>读 process.log 时间窗口太大(&gt; 10MB)</td><td>extract_evidence 工具截取 failure 时间 ± 30s</td></tr>
            <tr><td>同 run 已有 triage.json</td><td>视为 resume 模式(取代旧版,归档到 history/)</td></tr>
            <tr><td>Triager 自己崩</td><td>LoopController 写一个最小 spec_ambiguous triage 兜底</td></tr>
          </tbody>
        </table>
      </section>

      <section>
        <h2>⑩ 握手摘要</h2>
        <table class="dense">
          <thead><tr><th>对方</th><th>给</th><th>收</th></tr></thead>
          <tbody>
            <tr><td><b>LoopController</b></td><td>TriagerOutput</td><td>TriagerInput</td></tr>
            <tr><td><b>Integrator</b></td><td>(无)</td><td>result.json + process.log + http-trace</td></tr>
            <tr><td><b>Architect</b></td><td>triage.json(间接 via LoopController)</td><td>sdd/ (只读)</td></tr>
            <tr><td><b>UnitRegistry</b></td><td>affected_units(间接)</td><td>—</td></tr>
            <tr><td><b>Human (L3)</b></td><td>spec_ambiguous 时 l3_question 字段</td><td>—</td></tr>
            <tr><td><b>BugTracker</b></td><td>(LoopController 据 category 改 bug.category)</td><td>历史相似 bug</td></tr>
            <tr><td><b>memory/devloop/bug-triager/</b></td><td>新归因经验</td><td>启动注入</td></tr>
          </tbody>
        </table>
      </section>

      <section>
        <h2>⑪ 实战验证</h2>
<pre class="code"><span class="c"># 前置: Integrator 跑过一次 fail,有 integration/runs/{runId}/result.json</span>

<span class="c"># 1. 注册模板</span>
<span class="c">#    system/templates/devloop-triager.md ← 本页 §2.2</span>

<span class="c"># 2. 准备输入</span>
echo <span class="s">'{"pid":"p-test001","run_id":"run-int-20260513-1230","mode":"triage","call_id":"call-b-1","company_id":"c-test"}'</span> &gt; /tmp/tri.json

<span class="c"># 3. 跑 BugTriager</span>
curl -X POST http://localhost:3010/api/devloop/_test/run-agent/bug-triager -d @/tmp/tri.json

<span class="c"># 4. 期望 20-60 秒内</span>
<span class="c">#    data/companies/c-test/projects/p-test001/integration/runs/{runId}/triage.json</span>

<span class="c"># 5. 验证 schema + evidence</span>
node -e <span class="s">"
const fs = require('fs');
const path = 'data/companies/c-test/projects/p-test001/integration/runs/run-int-20260513-1230/triage.json';
const t = JSON.parse(fs.readFileSync(path, 'utf8'));
console.log('category:', t.category);
console.log('confidence:', t.confidence);
console.log('affected:', t.affected_units);
const ev = require('./server/services/agent-tools/extract-evidence');
console.log('evidence verify:', ev.verifyAll('p-test001', t.evidence));
"</span>

<span class="c"># 6. 测三种典型场景</span>
<span class="c"># 场景 A · contract_mismatch:故意让 SDD 与 contract.json 不一致 → 期望 patch 非空</span>
<span class="c"># 场景 B · impl_bug:故意让 code 实现违反 SDD → 期望 patch=null</span>
<span class="c"># 场景 C · infra_flake:杀掉一个 be 进程,Integrator 报 ECONNREFUSED → 期望 affected=[]</span>

<span class="c"># 验证决策合理性 (人工抽查 3-5 个 triage.json)</span>
<span class="c"># 关键看: 同样的 result.json 反复跑 BugTriager,category 应稳定 (Opus 4.7 的判断不能 flaky)</span></pre>
        <div class="callout ok">
          <b>BugTriager §⑪ 通过 = L2 完整闭环验证完成。</b>四个 Agent 全部 §⑪ 通过 = 整个 DevLoop 系统可执行性证毕。下一步是在真实代码里跑 P1 + P2 + P3 + P4 的实施。
        </div>
      </section>

    </article>
    <nav class="prev-next"></nav>
    <footer class="site">
      <div><b>Section</b>02 · Design / Agents</div>
      <div><b>Page</b>agents-triager.html</div>
      <div><b>Spec Rev</b>v2 · 2026-05-13</div>
    </footer>
  </main>
</div>
<script src="assets/shell.js"></script>
</body>
</html>