requestContext not propagated to workflow in networkLoop
Agent
When using agent.network(), the requestContext is not passed to the internal workflow's stream() and resumeStream() calls, causing workflow_run spans to lack metadata (e.g., userId, resourceId). This breaks observability pipelines that rely on span metadata for billing, analytics, or audit logging.
