Zellij Detached Codex Launch Verification

Check whether the launcher is over-crediting success

• Look at the launcher script and verify whether it only:
  • creates a session, or
  • also creates a pane running Codex.
• If verification only checks zellij list-sessions, that is insufficient.

Validate --dry-run honestly

• Run:
  • start-zellij-session-for-task --project-root <root> --dry-run <ISSUE>
• Confirm whether dry-run only prints the launch plan/script.
• Do not attribute launch-time pane verification failures to --dry-run unless the tool truly performs launch under dry-run.

Fix detached launch behavior

• Creating a detached session plus setting options --default-shell <bootstrap> may not produce a visible pane that can be inspected.
• Preferred fix on this setup:
  1. create the detached session
  2. launch the bootstrap as a real pane command with:
     • ZELLIJ_SESSION_NAME=<session> zellij run -- <bootstrap_path>
• This creates an inspectable pane like terminal_1 that actually runs Codex.

Strengthen verification

• After launch, inspect the real pane (terminal_1 or returned pane) with dump-screen.
• Require evidence such as:
  • OpenAI Codex
  • seeded task prompt like $start-new-task <ISSUE>
  • correct repo cwd visible in UI
• Optionally verify process tree for the Codex child.
• If no visible Codex evidence appears after retries, fail the launcher and do not claim activation.

Normalize ticket state instead of broadening supervision

• If a real verified live Codex session exists for a ticket still in Todo, the cleaner approach is to move the ticket to In Progress.
• Prefer keeping supervision cron scoped to normal active states rather than special-casing Todo live lanes.