Subagent orchestration can mark dependent work complete without waiting for spawned plan/review agents

## Summary LazyCodex / OMO subagent orchestration can spawn planning, review, or audit agents and then move dependent work forward without collecting or integrating their result. The user-visible failure is that root agents appear to "send a plan/review agent and naturally move on" instead of enforcing the documented short `wait_agent` polling + follow-up + inconclusive/respawn behavior before marking dependent work complete. ## Environment - LazyCodex version: `lazycodex-ai 4.7.5` - Codex version: `codex-cli 0.137.0` - OS: macOS 26.5.1 (Build 25F80) - Install method: `npx lazycodex-ai` / local OMO plugin cache - Relevant config: OMO plugin enabled; bundled rules inject Hephaestus / ultrawork / review-work guidance. Relevant skill docs: - `skills/review-work/SKILL.md`: says plan/reviewer agents should be spawned in background, root should poll with short `wait_agent` cycles, follow up after two waits with no substantive result, and not count silent/ack-only lanes as pass. - `components/ultrawork/directive.md`: same subagent reliability guidance. ## Reproduction This was observed from real LazyCodex session logs, not a synthetic repro. 1. Run a multi-step task that spawns a dependent audit/research/planning subagent. 2. Inspect the resulting session JSONL for `spawn_agent`, `wait_agent`, `send_message`/`followup_task`, `close_agent`, and `update_plan` ordering. 3. Observe cases where the root agent marks dependent steps complete, starts implementation, runs tests, or w...