night-market-validation-and-qa

# Validation and QA: what counts as evidence here This skill defines the evidence bar for claiming work complete, the coverage and quality thresholds that gate merges, the golden regression tests that guard settled battles, and the procedure for adding tests. The one-line thesis: a green check proves spec-satisfaction, not correctness, so every completion claim needs cited evidence and every test needs proof it can fail. ## The evidence bar Never claim "should work". Run the thing, capture the output, cite it. The house discipline comes from `Skill(imbue:proof-of-work)`: 1. Number every piece of evidence: `[E1]`, `[E2]`, each with the exact command and its captured output. 2. Map each acceptance criterion to evidence with a verdict: `Criterion: [E2] -> PASS` or `-> FAIL`. 3. Give the overall claim one of three statuses: `COMPLETE` (all criteria passed), `PARTIAL` (list blockers), `BLOCKED` (explain why). A blocked task reported as blocked with evidence is a successful report. A guessed "done" is not. 4. The final response must not contain "should work", "looks right", or any other unverified confidence phrase. ### Verifier integrity: never let the generator judge itself A passing verifier can mislead two ways (from the prover-verifier research, codified in commit `29081fda`, module `plugins/imbue/skills/proof-of-work/modules/verifier-integrity.md`): | Failure mode | What it looks like | |--------------|--------------------| | Wrong spec | The check co...