apply-arbiter-patchlisted

# Apply Arbiter Patch This is the operator-in-the-loop half of the MyVibe closed review cycle. `consensus-arbiter` wrote patches without touching source; this skill shows the diffs, waits for explicit approval, and applies them one-by-one via `git apply` with automatic rollback on failure. ## Phase Contract This skill runs in **DEVELOPMENT** or **TESTING** when applying code patches, and in any phase when applying markdown/doc patches — the existing phase-write-guard hook (Sprint 13) gates by target path, not by skill, so the patches themselves decide what's legal in the current phase. Before any step, read `vibeflow.config.json.currentPhase`. If the manifest lists patches targeting `src/**` and current phase is pre-DEVELOPMENT, emit the phase-write-guard's standard rejection and stop — don't attempt an apply that will partially land and then fail mid-session. ## Input Positional: - `$ARGUMENTS[0]` — session id. Optional; defaults to the most recent directory under `.vibeflow/state/patches/`. Flags: - `--yes` (or `-y`) — skip the interactive confirmation and apply immediately. Use in CI. - `--run-tests` — after successful apply, run the project's test command (detected from `vibeflow.config.json.tech.testRunner` or package.json scripts). On failure, print the `git checkout` command that rolls back the last patch set. - `--dry-run` — show the diff summary and exit without applying. - `--no-chain` — skip Sprint 19-E auto-chain (Step 9). Apply the patch, recor