reproduce-regression

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Reproduce a candidate

复现候选项

When to Use

使用时机

Input: sealed preparation/discovery packages, candidate and registry assignment. Follow project guidance before target work.
输入:已封存的准备/发现包、候选项和注册表分配结果。 在目标工作之前遵循项目指南。

When NOT to Use

不应使用的场景

Independent verification of an existing PoC; use replay.
对现有 PoC 进行独立验证;请使用 replay。

Reproduce

复现

  1. Read the standard and file contract. Verify inputs; read security guidance. Stop execution if prerequisites fail.
  2. Build and run actual S0/S1 with required services. Trace the candidate to a real user/attacker entry point. Build/install CLIs and libraries; exercise supported interfaces. For build findings, execute the supported build workflow.
  3. Create and execute a portable PoC against both live deployments with identical input and comparable configuration. Record whether S0 behaves correctly and S1 exhibits the claimed failure. No mocks, extracted functions or simulated systems.
  4. Save setup, tool/dependency versions, sanitized configuration, input, PoC, revisions, commands and separate logs. Record observations and false-positive checks in
    reproduce.json
    . If blocked, retain attempted setup and exact prerequisites. Build and deploy only inside your attempt directory, and list every build directory in
    build_dirs
    .
  5. Release temporary resources without deleting evidence. Record their disposition, then seal the package.
  1. 读取标准和文件契约。验证输入;阅读安全指南。如果前置条件未满足,停止执行。
  2. 构建并运行实际的 S0/S1 及其所需服务。将候选项追踪至真实用户/攻击者入口点。构建/安装 CLI 和库;演练受支持的接口。对于构建类发现项,执行受支持的构建工作流。
  3. 针对两个实时部署创建并执行可移植 PoC,使用相同输入和可比较的配置。记录 S0 是否表现正确,以及 S1 是否出现所声称的故障。不得使用 mock、提取出的函数或模拟系统。
  4. 保存设置、工具/依赖项版本、脱敏配置、输入、PoC、修订版本、命令和独立日志。在
    reproduce.json
    中记录观察结果和误报检查。如果受阻,保留已尝试的设置和确切的前置条件。只能在尝试目录内构建和部署,并在
    build_dirs
    中列出每个构建目录。
  5. 释放临时资源,但不要删除证据。记录其处置状态,然后封存该包。

Report Back

返回结果

Keep detailed evidence in the sealed package. Return only:
  • Status:
    complete
    or
    blocked
    , matching the record.
  • Record: sealed
    reproduce.json
    path, or why none was produced.
  • Result: one sentence describing observed S0/S1 behavior.
  • Blocker: missing prerequisite or required caller action, if blocked.
Completion means the experiment finished, not that the regression is confirmed.
将详细证据保留在已封存的包中。仅返回:
  • 状态:
    complete
    或
    blocked
    ,与记录一致。
  • 记录:已封存的
    reproduce.json
    路径,或说明未生成该文件的原因。
  • 结果:用一句话描述观察到的 S0/S1 行为。
  • 阻碍项:如果受阻,列出缺失的前置条件或调用方所需执行的操作。
完成意味着实验已结束,而不是回归问题已得到确认。

Rationalizations to Reject

应拒绝的理由

  • “The unit test proves it”: synthetic tests cannot establish a regression.
  • “单元测试证明了这一点”:合成测试无法确立回归问题。