fix(subagent): propagate parent RuntimeContext to child agents

[chickenlj]

Summary

• DefaultAgentManager.invokeAgent() built a fresh RuntimeContext with only sessionId/userId, discarding all parent context extras (typed attributes, string attributes, ToolExecutionContext, tenant info, outbound addresses, etc.).
• Added overloaded invokeAgent/invokeAgentStream methods that accept an optional parent RuntimeContext and use RuntimeContext.builder(parentRc) to preserve extras while overriding session identity.
• Updated all call sites in AgentSpawnTool (5 locations) to forward the parent context.
• Backward-compatible: existing 4-arg calls still work via delegation.

Fixes #1739
Fixes #1731

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[codecov]

Codecov Report

❌ Patch coverage is 70.58824% with 5 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...pe/harness/agent/subagent/DefaultAgentManager.java	71.42%	2 Missing and 2 partials ⚠️
.../agentscope/harness/agent/tool/AgentSpawnTool.java	66.66%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[AgentScopeJavaBot]

🤖 AI Review

This PR fixes a real and important bug: DefaultAgentManager.invokeAgent() / invokeAgentStream() built a fresh RuntimeContext that discarded all parent context extras (typed attributes, string attributes, ToolExecutionContext, tenant info, etc.), causing child agents to lose critical contextual information. The fix uses RuntimeContext.builder(parentRc) to inherit parent attributes while overriding session identity, and all 6 call sites in AgentSpawnTool are consistently updated. The approach is backward-compatible via delegation from the old signatures. One defensive-programming suggestion: explicitly null out agentState in the child builder to prevent parent state leakage into child agents that don't manage their own state (e.g., HarnessAgent).

[AgentScopeJavaBot]

🤖 AI Review

This PR fixes a real and important bug: DefaultAgentManager.invokeAgent() / invokeAgentStream() built a fresh RuntimeContext that discarded all parent context extras (typed attributes, string attributes, ToolExecutionContext, tenant info, etc.), causing child agents to lose critical contextual information. The fix uses RuntimeContext.builder(parentRc) to inherit parent attributes while overriding session identity, and all 6 call sites in AgentSpawnTool are consistently updated. The approach is backward-compatible via delegation from the old signatures. One defensive-programming suggestion: explicitly null out agentState in the child builder to prevent parent state leakage into child agents that don't manage their own state (e.g., HarnessAgent).

[itxaiohanglover]

Clean implementation — the overloaded invokeAgent and invokeAgentStream methods preserve backward compatibility while allowing parent RuntimeContext propagation. The conditional builder pattern (parentRc != null ? RuntimeContext.builder(parentRc) : RuntimeContext.builder()) is the right approach — it doesn't force callers to pass parentRc.