verify-hypothesislisted

# /verify-hypothesis — retrieve → contracrow classify → verdict artifact Design Section 8.2 (declared v0, R4) + Section 5.3 (`/verify-hypothesis`) + Section 12 M9 row. This is the ONLY sanctioned path to a `hypothesis` verdict row — never hand-write a verdict, and never let a lit-review answer stand in for this pipeline once a hypothesis is actually being adjudicated. 1. **Preregister first — default for keystones.** Committing the procedure+params BLIND before you see results is what makes the verdict trustworthy; skip it only for a genuinely exploratory, non-keystone check: ``` trialerror prereg commit --title "<hyp title>" --procedure "hypothesis-v1: stratified retrieve + contracrow" \ --params '{"k_total":6,"weights":"40,40,20","far_floor":2}' ``` Then pass `--prereg`/`--prereg-title` to the `hypothesis` action below so the committed record and this run are linked; `prereg_compliant` on the final verdict is stamped from that link, not asserted by hand. 2. **Run the pipeline.** Stratified retrieval forces breadth (near/moderate/far terciles over embedding distance, AMENDMENT-3's 40/40/20 default + far-arm floor — the same machinery `/ideation-round` uses): ``` trialerror verify hypothesis --text "<the hypothesis statement>" \ --by-launch <your launch_id> --k-total 6 --weights 40,40,20 --far-floor 2 \ --mode hybrid --judgments-file <path.json> --prereg --prereg-title "<title>" ``` (Use `--id HYP-xxx` inst