fix(trekresearch): gate Phase 4.5 on VOYAGE_STORM_ENABLED, not effort alone

CLAUDE.md claimed both STORM phases go inert when the flag is unset. Only
Phase 5 did: the flag check lives in research-loop-cap.mjs, and Phase 4.5
never invokes the cap — it was gated on effort: high alone. At high effort
with the flag unset, discovery still mined Phase-4 output and mutated the
dimension list, so `dimensions` diverged from `dimensions_baseline` and the
decline branch was unreachable for half the mechanism.

The code was the deviator, so the guard is fixed rather than the claim: the
Phase 4.5 skip-guard now names both conditions, with the reason inline.

Three surfaces scoped the flag to "the loop" and are corrected with it
(README, docs/command-modes, docs/architecture), plus the orchestrator phase
map. CLAUDE.md's claim is now true, but its stated MECHANISM was not — Phase
4.5's inertness comes from its own guard, not from the cap module — so that
sentence is corrected too.

New doc-consistency pin: the flag must be documented as gating both phases on
all four reference surfaces. Review finding 00a3af1a.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011vPSXe88qp5aqWUqbDNWoF

tests/commands/trekresearch.test.mjs

@@ -182,7 +182,7 @@ test('trekresearch — Phase 4.5 exists between Phase 4 and Phase 5 with the eff
   const slice = text.slice(p45, p5);
   assert.match(
     slice,
-    /\*\*Skip this phase entirely unless `phase_signal_result\.effort == 'high'`\.\*\*/,
+    /\*\*Skip this phase entirely unless `phase_signal_result\.effort == 'high'`/,
     'Phase 4.5 must carry the bolded skip-guard in the Phase 3.5 form',
   );
   assert.match(slice, /query-privacy-gate\.mjs/,
@@ -191,6 +191,25 @@ test('trekresearch — Phase 4.5 exists between Phase 4 and Phase 5 with the eff
     'Phase 4.5 must augment under the existing maxDimensions ceiling, not raise it');
 });
 
+// Phase 4.5 never invokes research-loop-cap.mjs, so the cap's own flag check
+// does not reach it. Gating on effort alone means unsetting VOYAGE_STORM_ENABLED
+// leaves half the mechanism live and the decline branch unreachable — while
+// CLAUDE.md claims both phases go inert. The guard has to name both conditions.
+test('trekresearch — Phase 4.5 skip-guard is gated on VOYAGE_STORM_ENABLED as well as effort', () => {
+  const text = read();
+  const p45 = text.indexOf('## Phase 4.5 —');
+  const p5 = text.indexOf('## Phase 5 —');
+  const slice = text.slice(p45, p5);
+
+  const guard = slice.slice(0, slice.indexOf('\n\n', slice.indexOf('**Skip this phase')));
+  assert.match(guard, /VOYAGE_STORM_ENABLED/,
+    'the Phase 4.5 skip-guard must name VOYAGE_STORM_ENABLED, not effort alone');
+  assert.match(guard, /\bAND\b|\*\*and\*\*/,
+    'the guard must be a conjunction — both conditions, not either');
+  assert.match(slice, /decline/i,
+    'Phase 4.5 must say why the flag gates it: the decline branch has to stay reachable');
+});
+
 test('trekresearch — Independence hard rule carries an explicit Phase 4.5 amendment', () => {
   const text = read();
   const rulesIdx = text.indexOf('## Hard rules');