requestContext not propagated to workflow in networkLoop

[daneatmastra]

This issue was created from Discord post 1465416421918904410:

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.

[daneatmastra]

Thank you for reporting this issue! We have labeled it for trio-tnt and we will look into it as soon as possible.

If you're experiencing an error, please provide a minimal reproducible example whenever possible to help us resolve it quickly.