v0.46.8

Highlights

• The planner boundary now carries executed tool history as canonical ToolOutputs rather than ToolResults, preserving raw payload/result bytes and omitted-result metadata across workflow boundaries.
• Nested agent runs can now finalize with a canonical FinalToolResult, letting child planners own the parent tool contract directly.
• Runtime-side agent-tool aggregation and finalizer shims have been removed, shrinking the runtime surface and keeping parent adaptation focused on durable transport plus child-run linkage.

Upgrade notes

• planner.PlanResumeInput and runtime.PlanActivityInput now expose ToolOutputs as the sole planner-facing execution-history field. Code that previously depended on ToolResults at that boundary must switch to ToolOutputs.
• Nested planners that own the outer tool contract should return PlanResult.FinalToolResult instead of relying on runtime-side agent-tool finalization behavior.
• Runtime-side agent-tool aggregation hooks have been removed. Integrations using AgentToolConfig.JSONOnly, AgentToolConfig.Finalizer, aggregate-key configuration, or the old aggregation payload helpers must move that ownership into the child planner/runtime.
• The runtime now rejects invalid terminal planner results that set both FinalResponse and FinalToolResult.

Verification

• go test ./runtime/agent/runtime
• make lint