fix(otel): propagate incoming trace context for HTTP requests

[Betula-L]

Issue for this PR

Fixes #18801
Related to #219
Related to #12142

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

This propagates incoming W3C trace context at the HTTP boundary.

If a request includes traceparent / tracestate, the server now extracts that context and runs request handling inside it. This lets request traces attach to an upstream trace instead of starting disconnected traces at the server boundary.

I kept this scoped to standard OTel/W3C propagation in core. It does not add a vendor-specific tracing backend.

How did you verify your code works?

• bun test test/server/trace-context.test.ts
• bun run typecheck
• verified against a real sandbox flow with Langfuse via the existing plugin/export path

Screenshots / recordings

Not a UI change.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Hey! Your PR title trace: propagate incoming trace context for HTTP requests doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍

[rekram1-node]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.