Documentation request: producer/build mapping and persisted execution event format

[luiscarlosmellendes]

Hello,

We are assessing documentation for Codex execution records as a possible evidence source for a local synthetic workflow. This is a documentation question; we have not performed runtime validation.

A documentary account describes records using these names: custom_tool_call.input, item_completed/CommandExecution, command, cwd, aggregated_output, exit_code, status, IDs, timestamps and ordinals. We have not established the exact emitting/persisting component or the build used for that episode.

The Codex CLI 0.162.0 changelog includes entries #50402 and #50427 concerning aggregated output and persisted command output. This is a useful lead, but it does not establish which build produced the described records or whether any particular output was truncated.

Reference: https://learn.chatgpt.com/docs/changelog#github-release-407151970

Could you point us to existing documentation for:

1. Producer and persistence: which component emits and persists this record format, and how the original event, stored record and displayed output relate?
2. Episode-to-build mapping: what documented metadata or existing provenance record can associate an episode with its actual producer build? We are not inferring that build from a field name or the latest release.
3. Versioned contract: the corresponding schema/specification edition, stable reference and compatibility rules for the persisted records.
4. Format mapping: any versioned mapping from public App Server/CLI events to the internal persisted format, including renaming, aggregation, omitted fields and framing.
5. Coverage and limits: which channels and bytes are preserved; treatment of loss, truncation, ordering, rotation, flush, closure and retention; and the precise scope and exceptions of the persisted-output limit mentioned in the changelog.
6. Known limitations: which of those properties are explicitly not guaranteed by the component.

If the description is insufficient to identify the build, please indicate the minimum metadata needed and where its origin and interpretation are documented. This request does not ask anyone to collect logs, run diagnostics or generate schemas. Any additional acquisition would be scoped separately before it takes place.

We are looking for documentation tied to the relevant component and edition. Public interface documentation alone would not establish the actual producer build of the historical episode.

Thank you.