refactor(a365): centralize request context in the base scope

[Nikhil Navakiran (nikhilNava)]

Summary

• centralize shared request context in OpenTelemetryScope for invoke-agent, inference, execute-tool, output, and guardrail spans
• map session ID, conversation ID, channel name/link, and operationSource (service.name) consistently across scopes
• retain full last-write-wins behavior for recordAttributes(), including attributes initially set by the span builder or typed scope methods
• ensure explicit request values override baggage-populated values and absent request fields leave baggage values intact

Cross-repository alignment

• ports the live base-scope request cleanup from opentelemetry-distro-dotnet#165
• follows the .NET live-scope last-write-wins behavior for generic attribute recording
• intentionally does not adopt Python's recorded/owned-attribute protection

Notable behavior changes

• Request now supports optional operationSource
• OutputScope and ApplyGuardrailScope now propagate sessionId through the shared base mapping
• guardrail-specific input content and all other scope-specific attributes remain handled by their concrete scopes
• generic recordAttributes() calls may overwrite base, builder, and typed-setter values

Validation

• npm test -- --run test/internal/unit/a365 — 683 passed
• npm run build
• npm run lint — no errors (pre-existing warnings only)
• npm run format
• git diff --check

[Copilot]

Copilot review overview

🟡 Changes recommended

The new tests do not cover a key that becomes scope-owned through a typed setter after creation.

Review effort: Balanced
Findings: 1

Open (1)

• Test generic writes cannot overwrite scope-owned typed values · New

What changed in this PR

This PR makes A365 scope builders’ populated span attributes take precedence over later recordAttributes() calls.

Changes:

• Track keys populated by the span builder or typed setters, while leaving absent keys writable.
• Add precedence tests and a changelog entry.

File	Description
test/​internal/​unit/​a365/​scopes.test.ts	Tests attribute precedence and generic writes.
src/​a365/​scopes/​OpenTelemetryScope.ts	Tracks scope-owned keys and skips generic overwrites.
CHANGELOG.md	Documents the fix.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused changes have relevant tests, and the review identified no unresolved issues.

Review effort: Balanced
Findings: 1

Open (1)

• Test generic writes cannot overwrite scope-owned typed values

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused refactor has relevant tests and no unresolved review findings.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Test generic writes cannot overwrite scope-owned typed values

[Copilot]

Copilot review overview

🟢 Approval recommended

The shared mapping and overwrite behavior match the stated intent, with focused tests and no unresolved findings.

Review effort: Balanced
Findings: None

[Jianbiao Lu (alexlu4250)]

Looks good to me. Approving with a non blocking note from AI:

The PR intentionally keeps generic recordAttributes() as last-write-wins, which is the right design for the stated contract, but it means future callers can still overwrite builder and typed-setter values. That should be treated as a deliberate API behavior, not a bug; I’d keep it documented in the contract/tests, which the PR already does.