Add session_id to context object

[tgillam-do]

This change adds the ability to send a session_id as a header to an agent and use that session_id to add a trace to that session. This enables the ability to have conversations show up in the DigitalOcean traces properly grouped together.

The implementation utilizes the context parameter to the entrypoint as the holder of the session_id if it is passed. This context parameter will be overloaded with other fields in the future.

[Copilot]

Pull request overview

This PR adds support for passing a session_id through request headers to agent functions via a new RequestContext object. This enables session tracking and correlation of requests across the system.

• Introduces RequestContext dataclass to carry request metadata (currently session_id)
• Updates the entrypoint decorator to extract Session-Id header and pass context to handlers
• Propagates session_id through the tracing system to CreateTracesInput

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
gradient_adk/init.py	Exports RequestContext from the public API
gradient_adk/decorator.py	Defines RequestContext and updates request handling to extract and pass session_id
gradient_adk/runtime/digitalocean_tracker.py	Updates tracker to accept and store session_id, passes it to CreateTracesInput
integration_tests/example_agents/echo_agent/main.py	Updates echo agent to use RequestContext and return session_id in response
integration_tests/run/test_adk_agents_run.py	Adds integration test verifying Session-Id header passthrough
tests/decorator_test.py	Adds comprehensive unit tests for RequestContext and session_id handling
tests/runtime/digitalocean_tracker_test.py	Adds unit tests for session_id in tracker and trace creation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The exception is being caught but the variable 'e' is removed. While silently handling exceptions may be intentional here, consider logging the exception for debugging purposes even if you don't want to break user code.