fix(codex-wake): keep seeded thread usable — carry cwd, keep path, skip resume

A thread seeded inside the wake call has no rollout file until its first turn,
so thread/resume always failed on it with 'no rollout found'. That failure left
threadPath null, which silently disabled the session-log completion fallback —
the only path that actually completes a turn on Codex CLI 0.145. Result: Codex
answered, the answer sat in the session JSONL, and the daemon timed out without
relaying it.

- buildThreadStartParams now carries peer cwd/model, so a seeded thread no
  longer starts in / with no project instructions or workspace roots
- the thread/start response path is kept as threadPath (it was discarded)
- a freshly seeded thread is no longer resumed; re-seed shares one code path
- normalizeWakeConfig preserves the resume flag, which it dropped entirely,
  making the injector's resume opt-out unreachable from real config

Tests cover the gap that broke in production: relayFinalToMurmur with no
threadId configured.

Refs #96

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