feat(voyage): define high-effort behavior + amend brief Non-Goal/SC1 + coordinator normalization (Decision B)

Wave 6 / Step 10 — autonomy-gated. Operator confirmed: gemini-bridge
substitution for plan-critic doubling AND SC1 amendment to
resolver-invariant encoding (decisions.local.json recorded).

- commands/trekplan.md: gemini-bridge plan-review Pass 2 on
  post-revision plan in high-effort mode (replaces fragile
  plan-critic doubling per risk-assessor).
- commands/trekresearch.md: full swarm + contrarian-researcher +
  gemini-bridge always-on.
- commands/trekreview.md: skip Pass 3 reasonableness + invoke
  coordinator normalization rule.
- commands/trekexecute.md: gates_mode = closed (strict manifest-audit,
  main-merge pauses); flag override still wins.
- agents/review-coordinator.md: Pass 3 high-effort normalization —
  substitute unknown rule_key with PLAN_EXECUTE_DRIFT, preserve
  original in original_rule_key.
- .claude/projects/2026-05-13-trekflow-solo-lane/brief.md (gitignored,
  not committed): Non-Goal amendment locks low/high tiers; SC1
  amendment authorizes resolver-invariant interpretation.
- tests/lib/doc-consistency.test.mjs: +4 pins for the
  "### High-effort behavior (v5.1.1)" heading per command.

Tests: 578 pass, 0 fail, 2 skipped (+4 from 574).

Closes #7 (operator-gated decisions captured + coordinator
normalization landed).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

plugins/voyage/commands/trekplan.md

@@ -934,6 +934,25 @@ one-line message: `Brief is brief_version 2.1 but does not carry phase_signals
 — re-run /trekbrief to commit them (Phase 3.5).` Enforcement is
 validator-only; this surface just makes the friendly hint readable.
 
+### High-effort behavior (v5.1.1)
+
+When `phase_signal_result.effort == 'high'` for the `plan` phase, after
+Phase 9 (plan-critic + scope-guardian dedup pass) runs to completion on
+the post-revision plan, run an ADDITIONAL `gemini-bridge` plan-review
+pass on the post-revision plan. Surface its findings as a separate
+`## Adversarial Pass 2 (gemini-bridge, v5.1.1 high-effort)` section
+appended to plan.md before the trailing JSON block.
+
+Rationale (per risk-assessor finding + Decision B substitution
+2026-05-14): the originally-considered "extra plan-critic-iterasjon"
+risked a revision-loop because plan-critic dedup keys on
+`(file, line, rule_key)` triplets and post-revision line numbers shift.
+The gemini-bridge pass is independent (different agent, different
+perspective) and does not re-tread the same dedup space — it surfaces
+genuinely new findings rather than re-emitting closed ones.
+
+Standard and low effort: do NOT run the additional pass.
+
 ## Hard rules
 
 - **Brief-driven**: Every plan decision must trace back to a section of the