consensus-arbiterlisted

# Consensus Arbiter Closes the MyVibe loop. The orchestrator gave us three verdicts + suggestions; this skill decides **which suggestions belong in the current phase** and produces `.patch` files the operator can apply safely. We never Write to source files here — that's the separate `apply-arbiter-patch` skill's job. ## Phase Contract This skill runs in **any phase** (the decision matrix handles phase-relevance filtering per-suggestion). Before any other step, read `vibeflow.config.json.currentPhase` for context; if it's missing emit `"arbiter needs vibeflow.config.json — run /vibeflow:onboard first"` and stop. ## Input - `$ARGUMENTS` — session id (required, e.g. `1101628e-…`). The orchestrator auto-invokes this skill after `NEEDS_REVISION` verdicts and passes the session id as the argument. When invoked manually, point at the latest session under `.vibeflow/state/consensus/`. Files read (relative to `$(vf_cwd)`): - `.vibeflow/state/consensus/<session>.jsonl` — per-reviewer rows with `suggestions[]` (Sprint 15-E schema) - `.vibeflow/state/consensus/<session>.verdict.json` — aggregated verdict (aggregator's output) - `vibeflow.config.json` — `currentPhase`, `domain`, `riskTolerance`, any `consensus.arbiter` overrides - The original artifact(s) named in suggestion `target.file` — only to sanity-check the line range; no writes. ## Process ### Step 1: Load the session ``` SESSION=$1 CONS_DIR=$(vf_state_dir)/consensus JSONL="$CONS_DIR/$SESSION.jsonl" VER