Add orch Codex launch bridge workflow

docs/orch-cli.md

@@ -12,6 +12,7 @@ In normal operation:
 - `orch` creates and monitors `inbox` threads
 - workers continue using `inbox`
 - a separate worker runtime or worker agent must still consume the assigned inbox thread after `dispatch`
+- Codex-specific launch bridges may sit above `orch`, but they should consume dispatch output rather than change the CLI contract
 
 ## Responsibilities
 
@@ -199,6 +200,11 @@ Behavior:
 - moves the task to `dispatched`
 - does not start a worker runtime on its own
 
+Integration note:
+
+- a higher-level Codex bridge may save this JSON output, render a worker brief, and then spawn a worker sub-agent
+- that bridge should remain outside the core `orch` runtime so the scheduling contract stays portable
+
 Strict-mode recommendation:
 
 - if `--base-ref` is omitted and the repository is clean, default to `HEAD`