feat(voyage): wire phase-signal-resolver into 4 downstream commands (closes #9 wiring)

plugins/voyage/commands/trekresearch.md

@@ -54,6 +54,16 @@ Supported flags:
    ```
    Create `{dir}/research/` if it does not already exist.
 
+   When `{dir}/brief.md` exists, ALWAYS run the brief-validator (soft mode)
+   AND the phase-signal-resolver for this command's phase before continuing.
+   The resolver's JSON output is captured as `phase_signal_result` and used
+   at Agent-spawn sites in Phase 4 to inject the brief-resolved model:
+
+   ```bash
+   node ${CLAUDE_PLUGIN_ROOT}/lib/validators/brief-validator.mjs --soft --json "{dir}/brief.md"
+   node ${CLAUDE_PLUGIN_ROOT}/lib/profiles/phase-signal-resolver.mjs --brief "{dir}/brief.md" --phase research --json
+   ```
+
 6. `--gates` — autonomy control. When present, set `gates_mode = true`. The
    research command will pause after each topic completes ("Topic N
    complete. Proceed to topic N+1? (yes/no)"). Default `gates_mode = false`
@@ -447,13 +457,19 @@ model_for_phase  = brief.phase_signals[<phase>]?.model  ?? profile.phase_models[
 ```
 
 The brief signal wins per-phase when present; the profile fills any
-gaps. There is no helper module — composition is documented prose in
-each downstream command.
+gaps. Composition is mechanically resolved via
+`node ${CLAUDE_PLUGIN_ROOT}/lib/profiles/phase-signal-resolver.mjs`
+invoked in Phase 1; the resolved JSON is captured as `phase_signal_result`
+and passed to `Agent` tool calls explicitly. The resolver controls only
+the orchestrator and the model parameter at Agent-spawn sites — sub-agents
+otherwise read `model:` from their own `agents/*.md` frontmatter (still
+pinned to `opus`).
 
 For `/trekresearch` specifically: `effort == 'low'` activates the
 existing `--quick`-equivalent code-path (inline research, no agent swarm).
-`effort == 'standard'` (or absent) → no change. High-effort behavior is
-deferred to v5.1.1 per brief Non-Goal.
+`effort == 'standard'` (or absent) → no change. `effort == 'high'`
+activates the high-effort behavior documented under `### High-effort
+behavior (v5.1.1)` below.
 
 ### Sequencing gate surface
 
@@ -474,7 +490,10 @@ commands surface, don't re-enforce.
   Triangulate AFTER independent research.
 - **Graceful degradation:** If MCP tools are unavailable (Tavily, Gemini, MS Learn),
   proceed with available tools and note limitations in brief metadata.
-- **Cost:** Sonnet for all sub-agents. Opus only in the main command/orchestrator.
+- **Cost:** Sub-agents use their pinned `model:` frontmatter (currently `opus`).
+  When `phase_signals[<phase>].model` is set, the orchestrator AND Agent-spawn
+  sites use the resolved model (`phase_signal_result.model`) for that phase.
+  Frontmatter is the default; brief signal is the per-phase override.
 - **Privacy:** Never log secrets, tokens, or credentials.
 - **Honesty:** If the question is trivially answerable, say so. Don't inflate research.
 - **Scope of codebase:** Only analyze the current working directory for local research.