Plan Test Runtime Impact Audit

The docs.plans audit requires test-runtime-impact-audit as a plan closeout step and exit criterion. The durable governance records are core-adr-0004 and core-req-0004.

Executor Evidence

The executor should use the step log to list new or changed tests found from git diff, Rack manifest changes, and direct test-file additions. The log should identify the relevant Rack stratum or file, summarize observed timing when available, and record optimization passes or slower-lane routing for tests that are expensive enough to affect normal development.

Reviewer Obligation

External review happens after the runtime-impact audit. The reviewer should inspect the step log, compare it with the test strategy document at docs/test-strategy.html, and challenge unoptimized minute-scale tests that should be made faster or split out of the normal edit-loop path.

Audit Boundary

Dev-std enforces the presence of the step id, the matching exit-criterion id, and the external-review dependency. It does not parse free text timing logs or impose one universal time budget, because acceptable runtime depends on the repository, lane, hardware, and signoff purpose.