jif-oai bd8fc9adb9 api: send hyphenated session and thread headers (#21757) ...

## Why
Some consumers expect conventional hyphenated HTTP headers. Codex
already sends the session and thread IDs on outbound Responses requests,
but it only uses the underscore spellings today, which makes those IDs
harder to consume in systems that normalize or reject underscore header
names.

Full context here:
https://openai.slack.com/archives/C08KCGLSPSQ/p1778248578422369

## What changed
- `build_session_headers` now emits both `session_id` and `session-id`
when a session ID is present.
- It does the same for `thread_id` and `thread-id`.
- Added regression coverage in `codex-api/tests/clients.rs` and
`core/tests/suite/client.rs` so both the lower-level client tests and
the end-to-end request tests assert the two header spellings are
present.

## Test plan
- Added header assertions in `codex-api/tests/clients.rs`.
- Added request-header assertions in `core/tests/suite/client.rs` for
both the `/v1/responses` and `/api/codex/responses` request paths.

2026-05-08 17:11:19 +02:00

..

clients.rs

api: send hyphenated session and thread headers (#21757)

2026-05-08 17:11:19 +02:00

models_integration.rs

1- Add model service tiers metadata (#20969)

2026-05-05 09:51:18 +03:00

realtime_websocket_e2e.rs

realtime: rename provider session ids (#20361)

2026-04-30 13:39:48 +03:00

sse_end_to_end.rs

Support end_turn in response.completed (#19610)

2026-04-25 21:57:42 -07:00