fix(qa): number the qa value-bar questions from 1 and say reproduced bugs already answer the first two

This commit is contained in:
garrytan committed 2026-09-30 13:31:29 +00:00
1 parent 2b76634831
commit 53c5b7505d
3 files changed
+9 -9

No files matched your search

+3 -3
View File
@@ -554,10 +554,10 @@ Preserve the initial charters under **Charters** after that metadata, before fin
Each proposed test carries a value card; propose it only when it passes this bar:
**Test value bar.** Before writing the test (the reproduced bug answers what it protects and what makes it fail):
**Test value bar.** Before writing or proposing a test, the reproduced bug already answers what it protects and what makes it fail; also answer:
3. Why does existing coverage not already catch that? Prefer adding a row to an existing table-driven test or shared fixture over a near-duplicate.
4. Does it need a production seam (export, flag, wrapper, injection hook) that no production caller needs? If yes, test at the real boundary instead.
1. Why does existing coverage not already catch that? Prefer adding a row to an existing table-driven test or shared fixture over a near-duplicate.
2. Does it need a production seam (export, flag, wrapper, injection hook) that no production caller needs? If yes, test at the real boundary instead.
Value card: `Value: protects=<...>; fails_when=<...>; why_new=<...>; seam=none` (seam: `none` or its name); each field at most 160 UTF-8 bytes here (clamp to 157 plus `...`; JSON keeps full values). Put it in the 8e.5 record (/qa) or under each proposed test (/qa-only). A missing upstream card never blocks: derive it; ignore unknown fields.