agent-platform release v4.7.17

Fixed

• The kagent line re-pins to v0.11.0-gs.4 (giantswarm/giantswarm#37763, giantswarm/giantswarm#37010): the line’s fourth release (commit ca399a3a; the upstream pin stays kagent-dev/kagent main @ 6a6b54ff) carries one more patch, giantswarm/kagent-upstream#15 — the A2A gateway fails a task whose dispatch to the AgentInstance runtime fails (a failing dial, a failing ingester start, or a runtime stream that errors before its first event) instead of leaving it TASK_STATE_SUBMITTED for good, which kept it as the instance’s active task, refused every later message as a conflict and showed every client a turn that never ends; a submitted task the runtime does not know is failed by the reconciler after the one-minute dispatch grace period. kagent.tag moves to 0.11.0-gs.4 (the controller and UI image build) and kagent.harness.image to the gs.4 Go ADK index digest sha256:6e510b241e2d000b7d10879c9fde3dd34a37879854278f0a5d386426049a88bf (meta and connectivity charts); components.kagent/components.kagent-crds keep the range >=0.11.0-gs.1 <0.11.1-0. examples/customer-bom.yaml and tests/verify-kagent-crds.py (KAGENT_LINE_REF) move with the pin. An installation on the 4.x line rolls the kagent controller, UI and the platform Harness to the new build on its next reconcile; the lab proof of the released chart is the audit’s next step (giantswarm/giantswarm#37763). make verify-wiring’s whole-render comparison against origin/main leaves image references out, so a re-pin — which moves kagent.harness.image by design — no longer trips it.