cross-reviewlisted

Provide a cross-model second opinion on the current diff before PR creation. ## Goals - Catch blind spots that single-model review may miss - Leverage a different model's perspective for cross-validation - Triage findings using implementation context to reduce noise - Present findings as advisory — never auto-apply ## Steps 1. **Resolve active plan identity and read cycle counter** (standard flow cap enforcement): a. Read `.harness/state/standard-pipeline/active-plan.json` to get the pinned plan path. - **If present**: proceed to step 1.b (persisted-identity mode). - **If missing**: warn the user and continue in **fallback mode** — no persisted identity. In fallback mode: skip step 1.b entirely (do NOT read or create `cycle-count.json`, to avoid reusing stale counters from other plans or leaking orphan state) and set `cycle=1`, `cap=∞` for step 7 (cap cannot be enforced). b. (Persisted-identity mode only) Confirm `active-plan.json` includes the task worktree metadata written by `/work`: `plan_path`, `worktree_path`, `branch`, and `worktree_state_id`. If `plan_path` no longer exists, try `./scripts/ralph-worktree.sh resume --id <worktree_state_id>` and recover the plan from the recorded canonical reference before falling back. Do not rescan `docs/plans/active/` while valid pinned state exists. c. (Persisted-identity mode only) Read `.harness/state/standard-pipeline/cycle-count.json`. If its `plan_path` matches `active-plan.json`, use its `cycle`. If mi