Adapt Sol 6.1 native multi-agent and workflow compatibility

docs/behavior-scenarios.md

@@ -71,6 +71,17 @@ These are static expected decisions, not live executions or benchmarks.
 | Mostly cached input and cost-sensitive routing | Use the cached-input category: Luna is 1/10 of 6.1 Sol, not 1/20; total task savings need actual usage |
 | New Sol is officially positioned near Astra | Use Sol for its work shape; retain useful Astra depth without mandatory participation or an unmeasured equivalence claim |
 | Archived synthetic packet requests gpt-6-sol | Validate it unchanged; never rewrite its requested identity as 6.1 |
+| Native API Multi-agent enabled; task asks for Luna and Astra workers | Children share request model/tools; use supported host orchestration for a mixture or disclose the mechanism gap |
+| API max_concurrent_subagents is 3; root and grandchildren are active | Count all active descendants against three, excluding root; do not apply this rule to a host that counts root |
+| Native model is available but beta SDK/gateway support is unknown | Check actual beta/schema support before claiming execution capability |
+| Native stream contains multi_agent_call and function_call | Hosted collaboration executes server-side; application executes only client function calls with matching call IDs |
+| Two native children emit function calls | Attribute and return every permitted call's result; process neither only root calls nor shared-state writes concurrently by default |
+| WebSocket injection fails because response already completed | Continue with the returned unaccepted function output; do not re-execute a completed external tool |
+| Worker text arrives before root final_answer | Keep worker text separate from user-facing final result; root synthesis and artifact checks still required |
+| Native Multi-agent requested with standalone compact, reasoning.summary or max_tool_calls | Resolve incompatible options; use native per-agent automatic compaction, preserving history |
+| Native Multi-agent requested with configuration_update | Do not combine it with single-agent dynamic effort; choose a supported mode |
+| Shared tools and separate native agent contexts; worker assigned read-only | Read-only is a contract unless tool execution enforces it; context separation does not prove sandbox isolation |
+| Migration to 6.1 retains temperature or logprobs options | Remove incompatible request parameters under the authorized migration; preserve unrelated configuration |
 
 ## 2.0 escalation scenarios (manual forward evaluation)