feat: propagate RunContextWrapper to session history read/write paths

[HuxleyHu98]

Summary

This PR adds backward-compatible RunContextWrapper propagation to the main session history read/write paths.

Specifically, it:

• adds optional wrapper support to:
  • Session.get_items(...)
  • Session.add_items(...)
• propagates the current runner RunContextWrapper through:
  • prepare_input_with_session(...)
  • save_result_to_session(...)
  • save_resumed_turn_items(...)
• updates both sync and streamed runner flows to pass the current wrapper
• preserves compatibility for existing custom session implementations by falling back to the old call signatures when a session method does not accept wrapper

Why

Issue #2072 is about making runtime context available to session implementations.

The earlier approach in #2488 added optional parameters at the interface level, but it did not actually propagate context from the runner side. This patch focuses on the runner-side propagation path so session implementations that support it can actually receive RunContextWrapper during session history reads/writes.

At the same time, this keeps older custom session implementations working unchanged.

Scope

This PR intentionally keeps the scope narrow.

Included:

• session history read/write paths:
  • get_items
  • add_items
• sync and streamed runner flows
• backward-compatible dispatch for legacy session implementations

Not included:

• pop_item
• clear_session
• broader session lifecycle expansion outside the main history read/write paths

I kept those out on purpose to make the initial change small, testable, and compatibility-focused.

Compatibility

Backward compatibility is handled in the internal dispatch layer.

If a session implementation supports the optional wrapper parameter, the runner passes the current RunContextWrapper.

If it does not, the runner falls back to the existing call shape, so older custom session implementations continue to work without modification.

Tests

Added coverage for:

• new-style custom session implementations that accept wrapper
  • verifies get_items / add_items receive the current RunContextWrapper
  • verifies the wrapper exposes the original run context
• legacy custom session implementations with the old method signatures
  • verifies they still work in:
    • Runner.run
    • Runner.run_sync
    • Runner.run_streamed

Ran:

• tests/test_session.py
• tests/test_agent_runner_streamed.py
• tests/test_soft_cancel.py
• tests/test_hitl_session_scenario.py
• tests/extensions/memory/test_encrypt_session.py
• tests/memory/test_openai_responses_compaction_session.py

Result:

• 146 passed

Static checks:

• pyright → 0 errors
• ruff check → passed

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 53f1c4779f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78e39d7b91

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 33cc084153

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 56794b32ad

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d06a2fe9d3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[HuxleyHu98]

I’ve addressed the review feedback and resolved the outdated Codex conversations. Local checks are passing on my side. Could a maintainer please enable/approve the PR checks when convenient? Thanks!