[codex] impl delivery_mode: current time reminders on response boundaries

[rka-oai]

Summary

• track user-like input and tool-output boundaries in current-time reminder state
• gate reminder injection when delivery_mode is after_user_or_tool_output
• preserve interval debounce and forced reminders after context-window changes

Why

Training can request reminders only after user or tool-output items while keeping the existing canonical pre-inference history-injection path.

Validation

• just test -p codex-core current_time_reminders_can_follow_only_user_or_tool_outputs
• just test -p codex-core current_time_reminders_follow_time_interval_and_persist_in_history
• just test -p codex-core current_time_reminder_is_refreshed_after_compaction
• just fix -p codex-core

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 74916d0d9e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid reading the clock for suppressed reminders

When delivery_mode is AfterUserOrToolOutput and an assistant-only continuation has no pending user/tool-output boundary, this gate correctly returns false, but it runs only after maybe_record_current_time_reminder has already awaited time_provider.current_time() and mapped failures to a fatal turn error. In that ineligible-continuation scenario, an external clock outage can still abort the model request even though no reminder could be injected; split the boundary/window eligibility check so suppressed reminders do not read the clock.

Useful? React with 👍 / 👎.