fix(qa): define evidence.json where it is built, point the preparation gate at the next section, name measured command durations in the report template

Recurring qa/qa-only workflow-judge complaints in CI (clarity/actionability 3.33).

qa/sections/exploratory.md

@@ -81,8 +81,8 @@ Never freeze buggy output, weaken tests or delete valid red tests.
 ## 4. Final report
 
 Use the surface report template; link each checkpoint. Separate browser scores, functional outcomes and proposed/executed tests.
-For evidence.json, Write R/annotations.json: {revision, runtime, cwd, evidence: [{capture, command, contract, expected, classification}], learning: [checkpoint IDs], limits}.
-Run `bun Q materialize R annotations.json` before Markdown; Q fills observed/learning, not classifications. Retain all safe probes, including failures/replays; disclose withheld/incomplete evidence.
+Write R/annotations.json: {revision, runtime, cwd, evidence: [{capture, command, contract, expected, classification}], learning: [checkpoint IDs], limits}.
+Before Markdown, `bun Q materialize R annotations.json` builds evidence.json from it; Q fills observed/learning, not classifications. Retain all safe probes, including failures/replays; disclose withheld/incomplete evidence.
 Evidence is invocation-local; /ship reruns once per invocation.
 Missing prerequisites/expectations/observations, timeouts and refusal never pass.
 Pass requires all required current-input contracts to pass with no required remainder.

qa/templates/functional-report-template.md

@@ -7,7 +7,7 @@
 | Surfaces / scope | {API, CLI, job, worker, webhook; changed and adjacent contracts} |
 | Runtime / native tools | {VERSIONS AND REPOSITORY-SUPPORTED COMMANDS} |
 | Fixture ownership / destinations | {ISOLATED ROOT, STORES, DOWNSTREAM TARGETS} |
-| Duration / stop reason | {MEASURED DURATION, COMPLETE OR BOUND/BLOCKER} |
+| Duration / stop reason | {MEASURED COMMAND DURATIONS, COMPLETE OR BOUND/BLOCKER} |
 
 ## Contract outcomes