venture-decidelisted

# Venture Decide Target venture directory: `$ARGUMENTS` Read `framework/gates.md`, the target venture state, all relevant evidence, and the latest challenge report. When the decision follows a completed experiment, read its locked `preregistration.design.decision_rules` and `results.branch` before the gate. The rule for that branch is the default outcome. The gatekeeper may depart from it only on evidence the preregistration did not anticipate, and the decision file must record the branch, the preregistered outcome and any departure under `## Pre-registered routing`. Before invoking the gatekeeper: 1. invoke `evidence-auditor` when evidence quality, quantitative derivations, supersessions, framework claims, or segment transport could affect the decision; 2. run `npm run evidence:check -- $ARGUMENTS` against the target venture directory; 3. if the consistency check fails, repair the evidence graph/state before making a gate decision; 4. then invoke `gatekeeper`. A failed consistency check is not itself evidence against the venture. It is a Venture OS state-integrity defect that must be corrected before the gate. ## Required outcome Exactly one of: - `PROCEED` - `TEST` - `PARK` ## Canonical state first After the gatekeeper returns: 1. update `venture.yaml` first; 2. set `latest_decision.id`, `latest_decision.outcome`, and `latest_decision.path` using a new stable decision ID; 3. write one structured current `next_action` with a stable `N###` ID, exactly one primary a