绿色测试日志失效的原因往往让团队头疼：你在一次建立中看到“PASS”，但随后代码变动后结果是否仍然有效？这正是AET v1 设计的主要——把执行状态和新鲜度分开记录，避免误判。

1️⃣ 为什么绿灯可能不再有效？

绿灯只说“命令当时成功”，而freshness告诉你“当前代码是否仍符合那一次成功”。如果相关文件被改动，旧的绿灯就失效，必须重新跑。

常见痛点

• 误以为绿色即永久通过：
• 忽略文件变化导致的失效：
• AET 报告 “UNKNOWN” 时被误解为成功：

2️⃣ 快速演示：从基础开始验证日志有效性

不污染全局环境，直接用 uvx --from agent-engineering-toolkit==0.1 aet demo stale-proof --format json

输出示例

{
"after_state": "RELEVANT_FILES_CHANGED"。"before_state": "EXACT_MATCH","demo_id": "stale-proof","diagnostics":,"execution_status": "PASS","llm_calls": null,"network_calls": null,"overall_status": "PASS","proof_path": null,"schema_version": "aet-demo-result/v1","workspace_path": null
}

要点：

• execution_status = PASS: 历史命令确实通过。
• freshness = RELEVANT_FILES_CHANGED: 后续文件变动使结果失效。

3️⃣ 演示中的 fixture 做了什么？

The fixture creates a temporary Git repo with:

• /src/calc.py: simple add function.
• /tests/test_calc.py: unit test calling add.
• AET runs aet quick proof --relevant-path ... - python -m unittest discover -s tests.
• The first run yields "EXACT_MATCH". Changing add to subtract without re-running tests changes freshness to "RELEVANT_FILES_CHANGED".
• AET never flips a historic PASS to FAIL;it simply flags that you need to re-run affected checks.

4️⃣ 在自己的仓库记录 Quick Proof

aet quick proof \
--output .aet/proofs/unit-tests.json \
--relevant-path src/app.py \
--relevant-path tests/test_app.py \
-- python -m unittest discover -s tests

The double dash is crucial: everything after it is passed verbatim as argv. AET stores:

• The exact command and exit status.
• The Git workspace snapshot at HEAD.
• The SHA of relevant paths.
• The creation timestamp and schema version.

`aet quick fresh` n reads stored proof and reports wher it still applies—without rerunning tests.

5️⃣ 常见失效与错误方法

Git 信息缺失

If proof lacks a workspace snapshot or its root is missing/unreachable。AET returns `UNKNOWN`** instead of guessing that result is still valid.

Proof 损坏

aet quick fresh --proof .aet/proofs/unit-tests.json

If files are unreadable or JSON binding incomplete,status remains `UNKNOWN`** and diagnostics explain *** .

相关文件、产物或环境变化

状态码	触发原因
RELEVANT_FILES_CHANGED	相关源码内容修改
ARTIFACT_CHANGED	声明产物变化
ENVIRONMENT_CHANGED	运行时或环境绑定变更

这些状态表明适用性失效，但并不否定历史执行成功。​ ​ ​ ​ ​ ​ ​ ​ ​ \t\t\t\t\t\t \t\t\t \t \t \t \t \t   © 2026 Advanced AI Lab All Rights Reserved.\">"

命令失败或超时

If `quick proof` runs an explicit argv that exits non‑zero or times out,`execution_status` will be `FAIL`. AET does not mask failures as passes nor mark m as `PASS` unless y truly succeeded and remain applicable.

---

方法越界风险