@cuylabs/agent-a365-observability 7.1.0 → 7.2.1

package/README.md

@@ -133,7 +133,7 @@ await runWithA365TurnContext(
 );
 ```
 
-If you use `@cuylabs/agent-channel-m365`, this wrapper is built into the channel
+If you use `@cuylabs/channel-m365-agent-core`, this wrapper is built into the channel
 adapter:
 
 ```typescript
@@ -202,7 +202,7 @@ standard Agent 365 identity set. Structured fields such as `tenantId`,
 keys.
 
 Microsoft's baggage processor does not overwrite span attributes that
-agent-core already set. In normal `@cuylabs/agent-channel-m365` usage this is
+agent-core already set. In normal `@cuylabs/channel-m365-agent-core` usage this is
 fine because the channel's default session strategy uses the M365
 `conversation.id` as the agent-core session ID. If you use custom M365 session
 mapping, `gen_ai.conversation.id` reflects the custom agent-core session ID.

package/docs/README.md

@@ -26,7 +26,7 @@ The short version:
 
 - agent-core owns platform-neutral spans for agent turns, tools, and model
   calls.
-- `agent-channel-m365` owns Activity ingress and turn wrapping for M365 hosts.
+- `channel-m365-agent-core` owns Activity ingress and turn wrapping for M365 hosts.
 - Microsoft's Agent 365 observability SDK owns exporter registration and
   baggage-to-span enrichment.
 - this package starts Microsoft observability and wraps callbacks,

package/docs/agent-core-otel.md

@@ -67,7 +67,7 @@ That matters for a few keys:
 - `createA365TracingConfig({ agentId, agentDescription, agentVersion })`
   causes agent-core to set those keys before baggage is copied.
 
-For normal `@cuylabs/agent-channel-m365` usage this is fine because the default
+For normal `@cuylabs/channel-m365-agent-core` usage this is fine because the default
 session strategy uses the M365 `conversation.id` as the agent-core session ID.
 If you use a custom M365 session mapping, `gen_ai.conversation.id` will reflect
 the custom agent-core session ID, not the original M365 conversation ID.

package/docs/architecture.md

@@ -8,7 +8,7 @@ M365-hosted agent to export Agent 365-shaped telemetry.
 | Layer                                          | Owns                                                                                                            | Does not own                                                    |
 | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
 | `@cuylabs/agent-core`                          | Agent runtime, model loop, tool execution, OpenTelemetry span emission                                          | Microsoft exporter startup, Agent 365 baggage, token resolution |
-| `@cuylabs/agent-channel-m365`                  | M365 Activity/CloudAdapter ingress, session mapping, optional per-turn observability wrapper                    | Exporter lifecycle or OpenTelemetry provider registration       |
+| `@cuylabs/channel-m365-agent-core`                  | M365 Activity/CloudAdapter ingress, session mapping, optional per-turn observability wrapper                    | Exporter lifecycle or OpenTelemetry provider registration       |
 | `@microsoft/agents-a365-observability`         | Agent 365 exporter, baggage builder, baggage span processor, per-request export token context                   | agent-core tracing config or channel message handling           |
 | `@microsoft/agents-a365-observability-hosting` | M365 hosting utilities such as `AgenticTokenCache` for OBO authorization                                        | S2S token exchange or agent-core telemetry                      |
 | `@cuylabs/agent-a365-observability`            | Glue that starts Microsoft observability, produces agent-core tracing config, and wraps turns with A365 baggage | Model provider, chat transport, Microsoft SDK internals         |

package/docs/lifecycle-and-limits.md

@@ -148,7 +148,7 @@ M365 per-user hosts can use `refreshA365OboObservabilityToken(...)` and
 
 ## M365 Session Mapping
 
-`@cuylabs/agent-channel-m365` defaults to using M365 `conversation.id` as the
+`@cuylabs/channel-m365-agent-core` defaults to using M365 `conversation.id` as the
 agent-core session ID. That keeps agent-core's `gen_ai.conversation.id` aligned
 with Agent 365 conversation identity.
 

package/docs/microsoft-node-package-comparison.md

@@ -49,7 +49,7 @@ focuses on startup, token resolution, and Agent 365 baggage.
 | `InferenceScope`        | Not used by default. | AI SDK telemetry already emits model spans under the agent turn.                                               |
 | OpenAI Agents extension | Not used by default. | It patches `@openai/agents`; agent-core is the harness we adapt.                                               |
 | LangChain extension     | Not used by default. | It patches LangChain callbacks; agent-core already owns the turn and tool lifecycle.                           |
-| Hosting middleware      | Not used directly.   | `agent-channel-m365` and this package perform the equivalent turn wrapping for cuylabs hosts.                  |
+| Hosting middleware      | Not used directly.   | `channel-m365-agent-core` and this package perform the equivalent turn wrapping for cuylabs hosts.                  |
 
 These are intentional gaps, not missing wiring. The default integration should
 enrich and export the spans agent-core already creates.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cuylabs/agent-a365-observability",
-  "version": "7.1.0",
+  "version": "7.2.1",
   "description": "Microsoft Agent 365 observability adapter for @cuylabs/agent-core",
   "type": "module",
   "main": "./dist/index.js",
@@ -29,7 +29,7 @@
     "typescript": "^5.7.0",
     "vitest": "^4.0.18",
     "zod": "^3.25.76 || ^4.1.8",
-    "@cuylabs/agent-core": "^7.1.0"
+    "@cuylabs/agent-core": "^7.2.1"
   },
   "peerDependencies": {
     "@cuylabs/agent-core": "^7.0.0",