report-regressions
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseReport a campaign
报告 campaign
When to Use
使用场景
Input: frozen , campaign index, progress ledger, sealed stage packages
and registry assignment.
Follow project guidance for every scoped change before reporting.
scope.json输入:冻结的 、campaign 索引、进度账本、已封存的阶段包和 registry 分配。
在报告之前,针对每项范围内的变更遵循项目指导。
scope.jsonWhen NOT to Use
不适用场景
Adjudicating evidence or repairing records; return those needs to the caller.
裁定证据或修复记录;应将这些需求交还调用方处理。
Report
报告
- Read the standard, labels and file contract. Reconcile the index against frozen scope, assigned changes and discovered candidates. Preserve PR/commit IDs and accepted duplicate mappings.
- Run report.py via with the campaign directory and
uv run --no-projectto render HTML, Markdown and JSON. Exit 1 means changed evidence or an invalid index; return its diagnostics and record the stage as blocked. Exit 0 may include--output ASSIGNED_DIRECTORY/reportsfindings; report eachUNRESOLVEDand theunresolved_reasonlevel of confirmed findings. Never repair decisions, invent evidence or edit hashes to pass validation.verification - Inspect counts and links. Preserve adjudicated outcomes/ratings. Separate incomplete fixes, latent/pre-existing bugs, rejected claims and unresolved work from confirmed totals.
- Ensure reports include coverage gaps, setup/execution evidence, rating reasons
and pending human review. Report missing information; do not claim completion
while required content is absent.
Seal with the assigned inputs and generated reports as artifacts; record validation failures as blocked.
report-stage.json
- 阅读标准、标签和文件约定。根据冻结的范围、已分配的变更和发现的候选项核对索引。保留 PR/commit ID 以及已接受的重复项映射。
- 通过 使用 campaign 目录和
uv run --no-project运行 report.py,以生成 HTML、Markdown 和 JSON。 退出码 1 表示证据发生变化或索引无效;返回相应的诊断信息,并将该阶段记录为--output ASSIGNED_DIRECTORY/reports。退出码 0 仍可能包含blocked发现项;报告每个UNRESOLVED,以及已确认发现项的unresolved_reason级别。绝不能为了让验证通过而修复决策、编造证据或编辑哈希。verification - 检查计数和链接。保留经裁定的结果/评级。将未完成的修复、潜在/预先存在的 bug、被驳回的主张和未解决的工作与已确认总数区分开来。
- 确保报告包含覆盖缺口、安装/执行证据、评级原因和待人工审核事项。报告缺失信息;所需内容缺失时,不得声称已完成。
将已分配的输入和生成的报告作为 artifacts 封存至 ;将验证失败记录为
report-stage.json。blocked
Report Back
回报
Keep detailed findings in the reports. Return only:
- Status: or
completefor report production.blocked - Reports: sealed and validated output paths; identify incomplete outputs.
report-stage.json - Result: one sentence describing campaign coverage and unresolved work.
- Blocker: affected records, validation errors or required caller action.
A complete report may describe an incomplete campaign.
将详细发现项保留在报告中。仅返回:
- 状态:报告生成状态为 或
complete。blocked - 报告:已封存的 和验证通过的输出路径;标明不完整的输出。
report-stage.json - 结果:用一句话描述 campaign 的覆盖情况和未解决的工作。
- 阻塞项:受影响的记录、验证错误或调用方需要采取的操作。
完整的报告可以描述尚未完成的 campaign。
Rationalizations to Reject
需要拒绝的判定理由
- “All agents finished”: that does not establish coverage or resolved candidates.
- “所有 Agent 都已完成”:这并不能证明覆盖情况或候选项已解决。