release: 0.37.0 — codex responses-lite reconstruction, exit auto-merge progress

[lroolle]

Two fixes from Eric's 2026-08-06 reports, released as 0.37.0.

Codex responses-lite session reconstruction

codex-tui >= ~0.146 sends x-openai-internal-codex-responses-lite: response.completed still carries usage/status but its output is [] — the real items only stream as response.output_item.done events. The old adapter returned the hollow completed object, so every assistant reply reconstructed as empty and the session's final answer (10k chars in the reporting trace) was missing entirely.

• openaiCompleted grafts collected output_item.done items into an empty completed output; the truncated-stream fallback also assembles output_text.delta runs into a synthetic partial message (dedup by item id) — under lite, deltas are the only copy of an interrupted answer.
• The leading run of system/developer messages (codex 0.146 opens with five) folds into the system prompt, mirrored exactly between openaiSystemText and normalizeOpenaiTurns; later developer messages still render as context injections.
• turnSnippet / openaiFirstUserText skip the codex harness wrappers (AGENTS.md digest, environment_context, mode banners), so outlines, thread sigs, compact labels, and the registry firstPrompt land on the human's prompt.

Verified on the real trace: turn 0 snippets the actual prompt, the final verdict turn renders and attributes, 50/50 assistant turns attributed, 0 unattributed/rewound.

Exit auto-merge: scan-first + progress

Huge-session exits looked hung: planMerge read and JSON-parsed every trace in the log dir with zero output — measured ~22s at 7GB peak RSS on a 2.5GB dir — even when the answer was "nothing to consolidate".

• Scoped plans substring-scan for the run's session ids before parsing anything (a wire sid is always a verbatim substring of its pair's JSON line): unrelated traces are never parsed, and the common fresh-single-file exit concludes from the scan alone. Same dir: 5.9s, 2.5GB peak, correct empty plan.
• MergeProgress events from plan/apply; the CLI prints steps for files >= 16MB, headed once by "Consolidating session traces — safe to ctrl-c (atomic writes; sources kept until fully merged)". cctrace merge wires the same printer.
• Merged outputs write in 8MB chunks (tmp + rename unchanged).

Tests

623 pass (10 new: lite graft, delta synthesis/dedup, leading-run fold, wrapper skips, scoped-scan never parses unrelated files, scan-only conclusion, .zst prior prefix, write progress).

🤖 Generated with Claude Code