AgentScope instrumentation should cap v1 and define v2 support strategy

[sipercai]

Problem

loongsuite-instrumentation-agentscope currently declares agentscope >= 1.0.0 without an upper bound. AgentScope has released 2.0.0 with Requires-Python >=3.11, so py311+ latest installs can resolve to v2 even though the current instrumentation targets v1 APIs.

The current instrumentation wraps v1 symbols such as agentscope.agent.AgentBase, ReActAgent hooks, Toolkit.call_tool_function, TruncatedFormatterBase, and agentscope.tracing.*. AgentScope v2 uses agentscope.agent.Agent, reply/reply_stream, middleware hooks, Toolkit.call_tool, and agentscope.middleware._tracing.TracingMiddleware; the top-level agentscope.tracing package is no longer present.

Current tests also import v1-only APIs, including agentscope.tracing._trace, so v2 can fail at import time or miss instrumentation coverage.

Proposed Scope

1. Short-term: cap the existing v1 instrumentation to agentscope >=1,<2 in package metadata and test requirements.
2. Add explicit test factors for AgentScope v1 and v2. v2 should run only on Python 3.11+.
3. Design v2 support as a middleware-first implementation instead of reusing v1 monkey patches directly.
4. Reuse opentelemetry-util-genai / ExtendedTelemetryHandler for LLM, agent, tool, embedding, content, token, error, TTFT, metrics, and ReActStep behavior. Framework-local code should only adapt AgentScope v2 objects and lifecycle hooks.
5. Evaluate duplicate-span behavior when users also enable AgentScope v2 native TracingMiddleware.

Suggested v2 Contract Tests

• import smoke without agentscope.tracing
• agent reply/reply_stream span tree
• model call span attributes and token usage where available
• tool call spans and tool error handling
• content capture disabled/span/event modes
• error status and exception attributes
• ReAct reasoning/action step mapping if supported by stable v2 events
• concurrent agents/state isolation
• uninstrument restore
• coexistence with native TracingMiddleware without duplicate LoongSuite spans

[ralf0131]

Issue Evaluation

Category: type/enhancement | Status: Evaluated

A timely compatibility issue. AgentScope 2.0.0 dropped the agentscope.tracing package and moved to middleware-based tracing, so the unbounded agentscope >= 1.0.0 constraint can resolve v2 and break at import time.

Feasibility: feasible, with a sensible phasing.
Scope: package metadata (loongsuite-instrumentation-agentscope), test factors (v1/v2 split), and a v2 middleware-first implementation reusing opentelemetry-util-genai.
Compatibility: the short-term agentscope >=1,<2 cap is the right stop-gap to prevent broken installs; v2 support is a larger follow-up.

The proposed v2 contract tests (reply/reply_stream span tree, tool/error handling, content-capture modes) are a solid foundation.

---

Automated evaluation by github-manager-bot