agent-platform release v4.6.1

The kagent line re-pins to v0.11.0-gs.3 (giantswarm/giantswarm#37010): the line’s second automated re-pin (sync-upstream.yaml, 2026-09-11) moved the consumed branch onto upstream kagent-dev/kagent main @ 6a6b54ff — kagent-dev/kagent#2786 (the Go ADK exports a turn’s spans before its terminal event leaves the process), #2785 (the chart disables controller metrics when bindAddress is empty or 0), #2797 (the built-in tool server’s URL uses the kagent-tools namespace) — with the 21 carried patches replayed clean, none dropped. v0.11.0-gs.3 (commit ed07617b) is that head. kagent.tag moves to 0.11.0-gs.3 (the controller and UI image build) and kagent.harness.image to the gs.3 Go ADK index digest (meta and connectivity charts); components.kagent/components.kagent-crds keep the range >=0.11.0-gs.1 <0.11.1-0; the GRPCRoute service list is unchanged (no proto/ change at the pin). Lab-proven on agentlab against the same tree (dev build …hed07617, the re-pinned build as charts, images and both platform Harness digests): platform-test, agents-test, toolsets-test --skip-portal and skills-test all green — agents reach Ready on the new Go ADK Harness, an A2A turn through the edge and a git-skill golden boot included. examples/customer-bom.yaml and tests/verify-kagent-crds.py (KAGENT_LINE_REF) move with the pin. No installation acts — the release stays inert behind the fleet’s <4.0.0 bound.