[yeongseon]

Summary

Explain when structured invocation logging complements Azure Monitor OpenTelemetry, and when the host integration alone is enough.

Changes

• Separate logging enrichment from Microsoft's instrumentation/exporter distribution.
• Describe optional host-context activation, preservation of active local spans and context restoration without claiming exclusive runtime capabilities.
• Link exporter-first integration guidance; update the API introduction consistently.

Validation

• Verified activation/restoration and local-span precedence against _otel.py and existing integration contracts.
• Python 3.11.15 make check-all and make build passed: 952 passed, 4 skipped, 4 deselected, 13 warnings in 11.48s; coverage 96.40%.
• No live Azure ingestion or docs-site build was run. No runtime behavior changed.

Related Issues

Closes #639

[yeongseon]

Reviewed exact head 3ae3610: required bandit, semgrep, Analyze, PR title and ci-required are completed/success; no review threads remain. Claims are grounded in local-span precedence and attach/detach behavior in _otel.py and existing contracts. No exclusive worker capability or exporter ownership claim remains. Merge authorized by the maintainer’s explicit instruction.