Add httpRequestTimeoutMilliseconds option and default enableBaggage to false

[fpfp100]

Summary

• Agent365ExporterOptions: New httpRequestTimeoutMilliseconds option (default 30s) controls the per-HTTP-request timeout for backend calls, distinct from exporterTimeoutMilliseconds which is the BatchSpanProcessor export deadline.
• Agent365ExporterOptions: exporterTimeoutMilliseconds default increased from 30s to 60s to allow sufficient time for retries across multiple identity groups.
• ObservabilityHostingManager: enableBaggage now defaults to false instead of true. Callers must explicitly opt in with { enableBaggage: true }.

Test plan

• All 1050 tests pass
• Updated observability-hosting-manager.test.ts to reflect new default behavior
• Build succeeds across all packages

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR fixes two observability configuration behaviors: ensuring Agent365Exporter honors its configured HTTP timeout, and changing ObservabilityHostingManager so baggage propagation middleware is opt-in by default.

Changes:

• Respect Agent365ExporterOptions.exporterTimeoutMilliseconds when constructing the fetch abort timeout.
• Change ObservabilityHostingManager.enableBaggage default behavior to false (opt-in).
• Update tests and changelog to reflect the new defaults/behavior.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
tests/observability/extension/hosting/observability-hosting-manager.test.ts	Updates expectations for the new default enableBaggage: false behavior and explicit opt-in.
packages/agents-a365-observability/src/tracing/exporter/Agent365Exporter.ts	Removes hardcoded 30s timeout and uses configured exporterTimeoutMilliseconds.
packages/agents-a365-observability-hosting/src/middleware/ObservabilityHostingManager.ts	Switches baggage middleware registration to opt-in (enableBaggage === true) and updates option docs.
CHANGELOG.md	Documents the timeout fix and the behavior change for enableBaggage.

Comments suppressed due to low confidence (2)

packages/agents-a365-observability/src/tracing/exporter/Agent365Exporter.ts:250

• The change to honor exporterTimeoutMilliseconds isn’t covered by an assertion in the existing Agent365Exporter test suite (no tests currently verify the fetch call’s abort signal/timeout). Adding a test that sets a non-default exporterTimeoutMilliseconds and asserts the fetch options use that value would prevent regressions back to a hardcoded timeout.

          body,
          signal: AbortSignal.timeout(this.options.exporterTimeoutMilliseconds)
        });

packages/agents-a365-observability/src/tracing/exporter/Agent365Exporter.ts:250

• AbortSignal.timeout will throw if this.options.exporterTimeoutMilliseconds is undefined, NaN, or negative (e.g., if a caller passes a partial options object at runtime, or Object.assign overwrites the default with undefined). Consider validating/coercing the timeout before calling AbortSignal.timeout, and falling back to the default (30_000ms) when the value is not a finite positive number.

          body,
          signal: AbortSignal.timeout(this.options.exporterTimeoutMilliseconds)
        });

---

You can also share your feedback on Copilot code review. Take the survey.