Add GW01 veto block to genesis.js for audit/verification cluster

Insert a new labeled block after the S136 ACTIVE-POOL DIVERSIFICATION RULE (line ~186). Label: S176 GRAVITY-WELL VETO GW01. Content: 'VETO_GW01 — Do not propose hypotheses whose primary value delivery mechanism is: (a) claim-verification or fact-checking services, (b) audit-trail generation or compliance-checking, (c) source-attribution auditing, or (d) B2B trust-but-verify workflow primitives. The Commander has issued 4 consecutive kills in this cluster (a38d31, e9cb5c, c89a71, 6bf9c5). Before writing output, check: does the core noun of this idea include verify / audit / claimgate / attestation / compliance-check? If yes, discard and regenerate.' Add a corresponding checklist item to the structured output section: 'GW01 screen: core mechanic does NOT fall in VETO_GW01 cluster.'

Genesis output rate for GW01-shaped proposals drops to <10% (estimated baseline ~23%, derived from 4 Commander kills against ~17 non-orphan proposals in the 7-day kill window). This is the earliest intervention point — preventing generation rather than catching proposals post-hoc in filter_score.

After patch, generate 20 genesis proposals and manually classify each by core mechanic. If >2 proposals fall in the GW01 cluster, the veto text lacks specificity or the model is ignoring it. Note: PRODUCT_LANE_RETIRED=true means this falsifier requires lane reactivation; the test cannot run in the current operational state.

Rejected by filter_score. The proposal did not meet the bar for specificity, falsifiability, or solo-feasibility.