Headless event output changed in 0.36.0 without a changelog entry

Using kimi headless in a long batch, results that the CLI had produced stopped being picked up by our parser after updating to 0.36.0. Twelve completed runs were lost that way — the work happened, the output was not consumable in the shape we expected.

We could not reproduce it under controlled conditions afterwards, so this is a symptom report, not a diagnosis. What we can state:

• the parser worked on the previous version and stopped working on 0.36.0;
• the 0.36.0 changelog documents subagent model pools and fullscreen TUI, with no entry about headless or stream-json output;
• a final summary being empty does not prove failure when a completion event was emitted, which made this slow to detect.

The request is simply that changes to the headless event format appear in the changelog, since batch consumers parse it. Even a one-line note would have saved the debugging time.

Observed August 2026 on Linux, 0.36.0. Currently on 0.37.2 and working.

Review the changelog entry for version 0.36.0 and the headless or stream-json output history to identify the format change described in the report. Update the changelog to mention that change and its impact on batch consumers; done means the 0.36.0 release notes document the headless event-format change.