feat(execute)!: hand waves over as session orders, never start Claude Code (green)

Operator decision 27.09.2026: Voyage works the PM way, so nothing in it
starts Claude Code. Work that needs another session becomes an order plus
a starter line the user gives a session they open themselves; Voyage
never starts the session.

/trekexecute's multi-session path (Phase 2.6) now prepares one wave at a
time: worktree per session, then lib/util/session-orders.mjs writes one
order per session (worktree, steps, done-condition, starter) plus
orders/wave.json, and the run stops. Running the same command again reads
each session's progress file (status mode), merges sequentially with
push-before-cleanup as before, and prepares the next wave. Phase 2.5 skips
the destructive pre-flight while a wave is in flight. Phase 7.6 recovery is
handed over the same way. Hard rule 21: never start Claude Code.

Removed with it, because they existed only for launched children: the
ANTHROPIC_API_KEY billing check (and its dry-run line and Hard rule 1
exception), the hooks-fire version precheck, the safety preamble, the
scoped-tool/turn/budget flags, templates/headless-launch-template.md, the
decomposer's launch.sh (now orders.md), /trekplan's "launch", the README
billing and MCP tuning sections, and scripts/q3-cache-prefix-experiment.mjs
(an experiment that spawned the binary; its results stay in docs/).
/trekresearch's deep-research pre-gate no longer runs the binary for its
version; the post-hoc check was already the authoritative guard.

Chose orders + starters over in-session subagents because the order's done
criterion asks for exactly that, and because /trekexecute disallows the
Agent tool on purpose (Hard rule 10); reopening that is a separate change.

Gate: 54 -> 0 hit lines outside EXEMPT. npm test 1250 (1245 pass, 0 fail,
5 skipped: 3 are the retired-reference scan without its local list).
verify.sh 7/0. The fixture run (tests/lib/session-orders.test.mjs) writes
two orders and wave.json for wave 1 and leaves a trap binary untouched.

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

commands/trekplan.md

@@ -297,7 +297,7 @@ The session-decomposer will:
 4. Identify which sessions can run in parallel (waves)
 5. Generate one session spec file per session
 6. Generate a dependency diagram (mermaid)
-7. Generate a launch script (`launch.sh`)
+7. Write the session orders (`orders.md`): one starter line per session, wave by wave
 
 When the session-decomposer completes, present the summary to the user:
 
@@ -318,16 +318,16 @@ When the session-decomposer completes, present the summary to the user:
 
 - Session specs: .claude/trekplan-sessions/{slug}/session-*.md
 - Dependency graph: .claude/trekplan-sessions/{slug}/dependency-graph.md
-- Launch script: .claude/trekplan-sessions/{slug}/launch.sh
+- Session orders: .claude/trekplan-sessions/{slug}/orders.md
 
 You can:
 - Review individual session specs before running
-- Run all sessions: `bash .claude/trekplan-sessions/{slug}/launch.sh`
-- Run a single session: `claude -p "$(cat .claude/trekplan-sessions/{slug}/session-1-*.md)"`
-- Say **"launch"** to start headless execution from here
+- Run the sessions yourself, wave by wave: open a Claude Code session per spec
+  and give it the starter line from orders.md (`/trekexecute <spec>`). Run the
+  sessions of one wave in parallel only in separate git worktrees.
 ```
 
-If the user says **"launch"**: run the launch script via Bash.
+Voyage does not start these sessions.
 
 Then **stop**. Do not continue to any subsequent phase.
 
@@ -372,8 +372,7 @@ Then continue to the next phase inline.
 > can spawn sub-agents (up to 5 levels deep), so that block no longer holds —
 > a delegated redesign is under evaluation (see
 > `docs/cc-upgrade-2.1.181-decision-matrix.md`, W1/CC-26). Until then, running
-> the phases inline in main context keeps the swarm intact. Use `claude -p`
-> in a separate terminal window for long-running headless work.
+> the phases inline in main context keeps the swarm intact.
 
 ---