{
  "internal_sources": [
    {
      "path": "system/agents/unit-tester/agent.md",
      "used_for": "现状硬约束1-7原文摘录，第一节现状规则盘点",
      "verified": true
    },
    {
      "path": "system/agents/unit-tester/soul.md",
      "used_for": "现状工作原则1-6原文摘录，第一节现状规则盘点",
      "verified": true
    },
    {
      "path": "system/agents/unit-tester/config.json",
      "used_for": "确认 status 至今为 training，从未走完 FDE 全流程",
      "verified": true
    },
    {
      "path": "docs/todo/system-design/35-validation-rigor-and-body-readiness-proposal.md",
      "used_for": "第二节全部内容：unit-tester 空白_base骨架事故案例（§1.2）、执行侧完整性闸门架构缺口（§1.3）、不是能力问题的复盘结论（§1.4）、提案A/D的实现记录",
      "verified": true
    },
    {
      "path": "system/agents/coder-methodology-trial/SKILL.md",
      "used_for": "第四节可迁移训练方法论：清单A/清单B结构、D1信号词黑名单、D5三支判断机械动作",
      "verified": true
    },
    {
      "path": "system/agents/coder-methodology-trial/train/hunt/knowhow_v1.md",
      "used_for": "第四节：coder训练的外部方法论调研结构与仓库内证据分析方式，作为可迁移方法论的参照",
      "verified": true
    },
    {
      "path": "system/agents/coder-methodology-trial/train/fde_report.md",
      "used_for": "第四节：诚实标注训练局限的方法论（A类/B类结论区分），可迁移到本次训练的自省方式",
      "verified": true
    },
    {
      "path": "data/companies/e2e-demo/runs/run_b962ea87f58f/nodes/rn_956c699f1160/test.log",
      "used_for": "第三节真实历史样本1：p-iyshuc apple风格官网，40/40 PASS，独立重跑+仓库标准工具交叉验证",
      "verified": true,
      "verification_method": "grep timeline.ndjson 确认 system_agent_id=unit-tester"
    },
    {
      "path": "data/companies/e2e-demo/runs/run_b962ea87f58f/nodes/rn_84d4651597bc/test.log",
      "used_for": "第三节真实历史样本2：p-iyshuc，infra_flake中断后重跑，mtime/diff核实实践，会话中断阶段核实技巧",
      "verified": true,
      "verification_method": "grep timeline.ndjson 确认 system_agent_id=unit-tester"
    },
    {
      "path": "data/companies/e2e-demo/runs/run_fa4d7e2bec49/nodes/rn_fc9155c598ef/test.log",
      "used_for": "第三节真实历史样本3：p-cgfdcr，四维度全PASS，动画真实性补测（scrollY时间序列采样）",
      "verified": true,
      "verification_method": "grep timeline.ndjson 确认 system_agent_id=unit-tester"
    },
    {
      "path": "data/companies/e2e-demo/runs/run_c7d233619784/nodes/rn_9d48ea87f326/test.log",
      "used_for": "第三节真实历史样本4：p-pyjha7，attempt-4，明确写明不采信coder自我汇报；sections_completeness维度用grep判定，暴露正则解析边界问题",
      "verified": true,
      "verification_method": "grep timeline.ndjson 确认 system_agent_id=unit-tester"
    }
  ],
  "external_sources": [
    {
      "topic": "ATDD / 验收测试驱动开发",
      "urls": [
        "https://www.testlio.com/blog/what-is-acceptance-test-driven-development",
        "https://www.geeksforgeeks.org/software-engineering/acceptance-test-driven-development-atdd-in-software-engineering/",
        "https://blog.logrocket.com/product-management/acceptance-test-driven-development/",
        "https://www.browserstack.com/guide/what-is-atdd"
      ],
      "verified": true,
      "note": "多方独立来源交叉一致，核心主张明确（验收标准先行、可测量语言、协作定义）"
    },
    {
      "topic": "测试证据留痕规范（test evidence / traceability）",
      "urls": [
        "https://testcollab.com/blog/building-a-test-evidence-strategy-that-scales",
        "https://www.testrail.com/blog/test-coverage-traceability/",
        "https://testsigma.com/blog/test-evidence/"
      ],
      "verified": true,
      "note": "核心论点'没有记录，通过声明本身没有意义'与本仓库test.log设计理念一致"
    },
    {
      "topic": "pytest skip/xfail 语义（工具/依赖不可用时的业界惯例）",
      "urls": [
        "https://docs.pytest.org/en/stable/how-to/skipping.html"
      ],
      "verified": true,
      "note": "官方文档，权威来源。核心发现：pytest将依赖不可用归为skip，与本仓库unit-tester硬约束6的blocked语义相反——用于第五节(c)对照分析，不是照搬依据"
    },
    {
      "topic": "工具不可用时的组织/流程层面诚实降级汇报方法论",
      "urls": [],
      "verified": false,
      "note": "未核实。搜索结果多集中在系统可用性/性能监控语境的'降级'（degradation），与'测试工具本身不可用如何汇报'不是同一议题，未找到直接对应的高权威来源，未采纳为训练依据"
    },
    {
      "topic": "单次编码任务内部代码分段粒度的增量交付方法论",
      "urls": [],
      "verified": false,
      "note": "承接coder-methodology-trial knowhow_v1.md已有标注，本次未重新调研，仅引用其结论：搜到的是系统级迁移语境而非细粒度编码任务切分，证据强度弱"
    }
  ],
  "not_found": [
    {
      "item": "unit-tester 真实判定 blocked（工具跑不起来）的历史样本",
      "note": "全仓库搜索 data/companies/e2e-demo 下所有 test.log，只找到4份，均为PASS结果，未发现blocked案例，如实说明未找到，不编造"
    },
    {
      "item": "unit-tester 真实发现acceptance fail并打回coder的历史样本",
      "note": "同上，4份样本均为全PASS，未见fail/打回记录"
    },
    {
      "item": "同一acceptance维度内部分子项有检测工具、部分没有的混合场景历史样本",
      "note": "4份样本均落在'全部维度都有工具覆盖'的情况，此路径在仓库历史数据中无真实先例"
    }
  ]
}