[Automated] Draft docs (agentgateway): xbackend: avoid collisions with AGWBackend keys

content/docs/kubernetes/main/documentation/about/policies/target-merge.md

@@ -22,7 +22,9 @@ The following table shows which resource types each policy section can target.
 | -- | -- | -- | -- |
 | `frontend` | Gateway | Depends on the field. See [Frontend section restrictions](#frontend-restrictions) for more information. | Applies to all listeners on the targeted Gateway. A `targetRef` or `targetSelector` can also set `port` to scope the policy to a single listener port on the Gateway. |
 | `traffic` | Gateway, HTTPRoute, GRPCRoute, ListenerSet | Optional | When targeting a Gateway, the `sectionName` selects a specific listener. When targeting an HTTPRoute or GRPCRoute, the `sectionName` selects a specific route rule. |
-| `backend` | Gateway, HTTPRoute, GRPCRoute, ListenerSet, Service, {{< reuse "agw-docs/snippets/backend.md" >}} | Optional | When targeting a Service, the `sectionName` selects a specific port. When targeting an {{< reuse "agw-docs/snippets/backend.md" >}}, the `sectionName` selects a specific sub-backend. |
+| `backend` | Gateway, HTTPRoute, GRPCRoute, ListenerSet, Service, {{< reuse "agw-docs/snippets/backend.md" >}}, XBackend | Optional | When targeting a Service, the `sectionName` selects a specific port. When targeting an {{< reuse "agw-docs/snippets/backend.md" >}}, the `sectionName` selects a specific sub-backend. |
+
+To target an XBackend, set `group: gateway.networking.x-k8s.io` and `kind: XBackend` in the `targetRef` or `targetSelector`. These fields distinguish the XBackend from an {{< reuse "agw-docs/snippets/backend.md" >}} that has the same namespace and name.
 
 ### Frontend section restrictions {#frontend-restrictions}
 

content/docs/kubernetes/main/release-notes/release-notes.md

@@ -37,10 +37,12 @@ Review the release notes for agentgateway on Kubernetes.
 <!-- ref: https://github.com/agentgateway/agentgateway/pull/3802 -->
 <!-- ref: https://github.com/agentgateway/agentgateway/pull/3812 -->
 <!-- ref: https://github.com/agentgateway/agentgateway/pull/3746 -->
+<!-- ref: https://github.com/agentgateway/agentgateway/pull/3891 -->
 
 **Traffic management**
 
 - Local gRPC policy call failures, such as DNS errors, unavailable endpoints, refused connections, and timeouts, are reported with the mapped gRPC status instead of `UNKNOWN`.
+- Typed backend targets now keep XBackend resources separate from {{< reuse "agw-docs/snippets/backend.md" >}} resources that have the same namespace and name, so policies and routes attach to the intended backend.
 
 **LLM**
 

content/docs/standalone/main/documentation/configuration/policies/attachment.md

@@ -17,6 +17,8 @@ Policies that are attached at multiple levels are applied at all levels.
 |Route|All Policies|Runs after route selection, before backend selection|
 |Backend|Backend TLS, Backend Authentication, Backend HTTP, Backend TCP, AI/LLM, MCP Authorization, MCP Authentication, External Authorization, Header modification|Runs after backend selection|
 
+Use `policies.target.backend.backend.kind` only when a backend target comes from a typed backend resource that can share a namespace and name with another backend type. For example, set `kind: XBackend` to attach the policy to an XBackend instead of a different backend type with the same name. Omit `kind` for ordinary standalone backend targets.
+
 ## Example policy configuration
 
 Review the following example configuration that uses one of each policy type.

content/docs/standalone/main/release-notes/release-notes.md

@@ -32,10 +32,12 @@ Review the release notes for agentgateway standalone.
 <!-- ref: https://github.com/agentgateway/agentgateway/pull/3774 -->
 <!-- ref: https://github.com/agentgateway/agentgateway/pull/3812 -->
 <!-- ref: https://github.com/agentgateway/agentgateway/pull/3746 -->
+<!-- ref: https://github.com/agentgateway/agentgateway/pull/3891 -->
 
 **Traffic management**
 
 - Local gRPC policy call failures, such as DNS errors, unavailable endpoints, refused connections, and timeouts, are reported with the mapped gRPC status instead of `UNKNOWN`.
+- Typed backend targets now keep XBackend resources separate from {{< reuse "agw-docs/snippets/backend.md" >}} resources that have the same namespace and name, so policies and routes attach to the intended backend.
 
 **LLM**