Restructure council_verdict.js cheapest_instant_kill_test from string to machine-readable object

In council_verdict.js, change the `cheapest_instant_kill_test` field from a free-text string to a structured object in the VERDICT_SCHEMA_INSTRUCTION: `{"gate_type": "OUTBOUND_SIGNAL_CHECK" | "ARTIFACT_EXISTENCE_TEST" | "MARKET_OBSERVATION" | "BUYER_DIRECT_ACCESS" | "NOT_APPLICABLE", "specific_action": "<30 words: exact action naming platform, ICP title, and quantity threshold>", "pass_criterion": "<20 words: observable result that means proceed>", "time_bound_days": 7 | 14 | 30}`. Prompt instruction: 'Do not write generic tests. Name the platform (LinkedIn, specific Slack workspace, named subreddit), the ICP job title, and the minimum signal count. "Reach out to customers" is insufficient. "Cold DM 12 LinkedIn Heads of Support UK, need 2 replies naming missed-SLA pain within 7 days" is sufficient. gate_type=NOT_APPLICABLE only if this is a STRONG_BUILD verdict and no kill test is needed.' Apply this structure to all verdict_action values. Update the Commander dashboard to render cheapest_instant_kill_test as a structured 'Kill Gate' card with a checkbox to mark as executed.

Every GATHER_MORE_SIGNAL verdict (currently ~55% of verdicts per S157 distribution: 25 ROBUST + 13 MIXED + 4 FRAGILE + 1 STRUCTURALLY FRAGILE out of 43) produces a machine-readable gate condition that Commander can execute without re-reading the full reasoning. The 2 non-convergent verdicts (7199a9, 2ca131) which currently produce 'human decision required' should produce structured OUTBOUND_SIGNAL_CHECK tests that resolve the convergence dispute. Over 30 days, the dashboard will surface a priority queue of pending kill tests sorted by time_bound_days.

Apply updated council to 10 hypotheses. For every non-STRONG_BUILD verdict: gate_type must be a valid enum value (not NOT_APPLICABLE unless STRONG_BUILD); specific_action must name at least one platform, community, or ICP job title; pass_criterion must be parseable as a binary outcome; time_bound_days must be populated. If ≥3 of 10 produce specific_action fields containing only 'validate with potential buyers' or equivalent generic text, the council prompt requires few-shot examples of structured kill tests. Additionally, re-run the 2 known non-convergent hypotheses (7199a9, 2ca131): both should produce gate_type=OUTBOUND_SIGNAL_CHECK or BUYER_DIRECT_ACCESS with a testable 7-day action.

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