rka-oai 9eeac78b3f Refresh environment dates from the configured clock (#36187) ...

## Why

The `<current_date>` in environment context could diverge from the clock used by current-time features, especially when a host provides an external clock.

## What changed

- Read the current time from the session's time provider whenever world state is built, and render its local date in environment context.
- Use each session's own thread ID for clock reads, including guardian sessions.
- Propagate clock-read failures through turn error events and stop before model inference.

## Testing

- Cover date updates across turns and app-server requests.
- Verify guardian clock reads use the corresponding root or guardian thread ID and do not run during prewarm.
- Verify clock failures emit an error without sending an inference request.

GitOrigin-RevId: bb7f32ccc0229b7bc6f14d7356db00bcce78066d

2026-07-30 16:44:18 +00:00

..

common

Track parent turns for nested Codex requests (#35835)

2026-07-28 21:58:33 +00:00

remote_env_windows

Scope runtime workspace roots to execution environments (#32952)

2026-07-14 04:41:08 +00:00

suite

Refresh environment dates from the configured clock (#36187)

2026-07-30 16:44:18 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

responses_headers.rs

Allow custom providers to opt into standalone web search (#34846)

2026-07-23 00:02:15 +00:00