knittel-openai b794182ea7 Populate workspace kind on Codex turn events (#25135) ...

## Summary
- carry `workspace_kind` from Responses API client metadata into the
turn resolved analytics fact
- serialize the optional value on `codex_turn_event`
- cover both the turn metadata source and turn event serialization

The `workspace_kind` tells us whether a thread had a project attached vs
projectless. this is an indicator for who is adopting Codex for
knowledge work outside of coding

## Testing
- `env UV_CACHE_DIR=/private/tmp/uv-cache
/private/tmp/cargo-tools/bin/just fmt`
- `env PATH=/private/tmp/cargo-tools/bin:$PATH
CARGO_HOME=/private/tmp/cargo-home UV_CACHE_DIR=/private/tmp/uv-cache
/private/tmp/cargo-tools/bin/just test -p codex-analytics`
- `env PATH=/private/tmp/cargo-tools/bin:$PATH
CARGO_HOME=/private/tmp/cargo-home UV_CACHE_DIR=/private/tmp/uv-cache
/private/tmp/cargo-tools/bin/just test -p codex-core turn_metadata`

Paired with openai/openai#970661, which keeps forwarding the same
metadata key through Responses API headers.

b794182ea7 · 2026-06-02 12:46:14 -07:00

History

..

src

Populate workspace kind on Codex turn events (#25135)

2026-06-02 12:46:14 -07:00

BUILD.bazel

Extract codex-analytics crate (#15748)

2026-03-25 11:08:05 -07:00

Cargo.toml

refactor: route Codex auth through AuthProvider (#18811)

2026-04-23 17:14:02 -07:00