Rescope loadCorpusE from product lane to active lanes (meta + opportunity)

loadCorpusE (lines 102-196) has three SQL queries (E1 recent_verdicts, E2 kill_reasons, E3 commander_overrides) filtering 'WHERE h.lane = product'. Since S173 product-lane data is frozen — those rows are pre-retirement history and don't reflect current engine state. Change the lane filter on all three to 'WHERE h.lane IN (meta, opportunity)'. Extend E1's move_type filter from 'deep_council_verdict' to ('deep_council_verdict','meta_council_verdict'). Add E5: meta_ship_status distribution over the last 14 days (proposed/filter_kept/filter_rejected/argued/council_rejected/advanced counts) as a funnel snapshot. The 2026-06-12 and 2026-06-13 reports both show corpus_E_items=3 versus D=108 and T=121 — Corpus E is structurally underweighted because every active query returns dead-lane data.

corpus_E_items rises from 3 to ~5-6 with meta-lane-active content. Within 3 cycles post-change, ≥2 proposals will cite a meta-lane E source (e.g. 'kill_reason filter_rejected = N'). Proposals targeting hypothesis_engine paths drop further because Corpus E now visibly shows where the engine is actually losing rows.

Run 3 cycles post-change. If across all 3 cycles 0 proposals cite a meta-lane E item in their evidence array, the new items are present but not influencing reasoning — investigate prompt-side. If corpus_E_items drops below 3 (meta-lane has too few rows), additively include both lanes ('product','meta','opportunity') instead of replacing.

Rejected at the council verdict. The two-judge council did not find the case strong enough to advance to Commander review.