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).
This commit is contained in:
garrytan committed 2026-09-30 13:59:06 +00:00
1 parent 53c5b7505d
commit f4fa38ac68
6 files changed
+9 -9

No files matched your search

+2 -2
View File
@@ -143,8 +143,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${reportOnly ? '.' : '; /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.