Gate B reports treated synthetic TV passes as if they satisfied product-state
exit. Soft result words like "not run" also blurred fail-closed reporting.
Encode the seven evidence and process locks in docs/TEST-SPEC.md as closed
vocab tables, required columns, Gate B exit checklist, Build brief refusal
fields, and SoT mutation permit-before-write. Add Evidence class to every
case table. Reclassify gate-b RESULTS so TV-3/6/7/10 vitest passes stay
proxy-synthetic, Gate exit product-state rows are blocked, and "not run"
becomes blocked. Gate B remains not green.
Gitea issues are the only mechanism for reporting issues found during a test
pass. Chat, Slack, and PR comments are not the bug log. On fail, open or
update a Gitea issue with case id and evidence pointer; the report table
blocker column links that issue. Do not invent issues that lack runner
evidence.
- Gate B: Ty confirms TV-3/6/7/10 on real fixtures; unit/API automated
- Gate C: Ty opens SLAB-UAT-* draft in real store admin; mocked-store not exit
- Phase 3: Ty publishes test slab as Woo draft SLAB-UAT-*; automation UI cases
- Phase 5: Ty judgment on species acceptance; automation Call 1/2 cases
- Phase 6: deployment smoke automated; Ty walks UAT-PRACTICE.md for UAT signoff
- Rename 'Cadence summary' to 'When tests are written'
- Phase 1 remainder: agent automation drives calibrated → ready (keep, per #20)
- Add Section 1: case ID naming convention (all prefixes and abbreviations defined)
- Add Section 2: how cases are executed (paths, tools, staging for unit/contract/integration/E2E/ops)
- Restructured every case table to three columns: what must happen, where the rule lives, how verified
- Replaced cadence column with when-written in pyramid overview; cadence summary preserved
- Fixed all exit-evidence lines: agent-written test automation replaces Ty-driven curl
- Expanded all acronyms on first use; no magic acronyms in case descriptions
- Removed Ty-driven manual testing; automation is the verification path
grokbot_ty
grokbot_ty