docs-2979: fix broken anchors across products and versions

Retarget broken anchors to their current heading, or neutralize when the target
section was removed (unlink same-page links; drop the fragment on cross-page links,
keeping the page link). Verified against built-page anchor ids. Covers all built
versions plus next.

Reduces broken anchors from 329 to 72. The remainder live in shared partials and
component/generated reference anchors (e.g. #httpmatch, #selectors, API type refs)
whose validity varies by including page; these need per-page handling and are left
for follow-up. onBrokenAnchors stays 'warn' (DOCS-2978) until they are resolved.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ctauchen

calico-cloud/_includes/content/_rule.mdx

@@ -12,7 +12,7 @@ are executed in order.
 | ipVersion   | Positive IP version match.                                                                 | `4`, `6`                                                     | integer                       |         |
 | source      | Source match parameters.                                                                   |                                                              | [EntityRule](#entityrule)     |         |
 | destination | Destination match parameters.                                                              |                                                              | [EntityRule](#entityrule)     |         |
-| http        | Match HTTP request parameters. Application layer policy must be enabled to use this field. |                                                              | [HTTPMatch](#httpmatch)       |         |
+| http        | Match HTTP request parameters. Application layer policy must be enabled to use this field. |                                                              | HTTPMatch       |         |
 
 After a `Log` action, processing continues with the next rule; `Allow` and `Deny` are immediate
 and final and no further rules are processed.

calico-cloud/get-started/operator-checklist.mdx

@@ -11,7 +11,7 @@ If you have issues getting your cluster up and running, use this checklist.
 - [Check logs for fatal errors](#check-logs-for-fatal-errors)
 - [Check custom resources](#check-custom-resources)
 - [Check pod capacity](#check-pod-capacity)
-- [Check the web console dashboard for traffic](#check-manager-ui-dashboard-for-traffic)
+- [Check the web console dashboard for traffic](#check-the-web-console-dashboard-for-traffic)
 
 ## Check installation start errors
 

calico-cloud/multicluster/kubeconfig.mdx

@@ -275,7 +275,7 @@ A cluster in the mesh can write policy rules that select pods from other cluster
 ### Switch to multi-cluster networking
 The steps above assume that you are configuring both federated endpoint identity and multi-cluster networking for the first time. If you already have federated endpoint identity, and want to use multi-cluster networking, follow these steps:
 
-1. Validate that all [requirements](#calico-enterprise-multi-cluster-networking) for multi-cluster networking have been met.
+1. Validate that all [requirements](#prerequisites-for-calico-cloud-multi-cluster-networking) for multi-cluster networking have been met.
 2. Update the ClusterRole in each cluster in the cluster mesh using the RBAC manifest found in [Generate credentials for cross-cluster authentication](#generate-credentials-for-cross-cluster-resource-synchronization)
 3. In all RemoteClusterConfigurations, set `Spec.OverlayRoutingMode` to `Enabled`.
 4. Verify that all RemoteClusterConfigurations are bidirectional (in both directions for each cluster pair) using these [instructions](#establish-cross-cluster-resource-synchronization).
@@ -371,7 +371,7 @@ If the Typha logs do not yield the expected result, review the warning or error-
 #### Troubleshoot multi-cluster networking
 ##### Basic validation
 * Ensure that RemoteClusterConfiguration and federated endpoint identity are [functioning correctly](#validate-federated-endpoint-identity--multi-cluster-networking)
-* Verify that you have met the [prerequisites](#calico-enterprise-multi-cluster-networking) for multi-cluster networking
+* Verify that you have met the [prerequisites](#prerequisites-for-calico-cloud-multi-cluster-networking) for multi-cluster networking
 * If you had previously set up RemoteClusterConfigurations without multi-cluster networking, and are upgrading to use the feature, review the [switching considerations](#switch-to-multi-cluster-networking)
 * Verify that traffic between clusters is not being denied by network policy
 

calico-cloud/network-policy/recommendations/policy-recommendations.mdx

@@ -44,7 +44,7 @@ Creating and managing policy recommendations is available only in the web consol
 
 ## How to
 
-- [Enable policy recommendations](#enable-policy-recommendations)
+- Enable policy recommendations
 - [Activate and review policy recommendations](#activate-and-review-policy-recommendations)
 - [Review global settings for workloads](#review-global-settings-for-workloads)
 - [Update policy recommendations](#update-policy-recommendations)
@@ -63,7 +63,7 @@ The **Policy Recommendations** board is automatically displayed.
 
 **Notes**:
 
-- A policy recommendation is generated for every namespace in your cluster (unless namespaces are filtered out by an Admin using the [selector](../../reference/resources/policyrecommendations.mdx#namespaceSpec#selector) in the PolicyRecommendationScope resource).
+- A policy recommendation is generated for every namespace in your cluster (unless namespaces are filtered out by an Admin using the [selector](../../reference/resources/policyrecommendations.mdx#namespacespec) in the PolicyRecommendationScope resource).
 - Flow logs are continuously monitored for policy recommendations.
 - Recommended policies are continuously updated until you **Add to policy board** or **Dismiss policy** using the Actions menu.  
 - Policy recommendations are created as **staged network policies** so you can safely observe the traffic before enforcing them.

calico-cloud/network-policy/staged-network-policies.mdx

@@ -178,4 +178,4 @@ spec:
 - For details on how to configure RBAC for staged policy resources, see [Configuring RBAC for tiered policy](policy-tiers/rbac-tiered-policies.mdx)
 - For details on staged policy metrics, see
   - [Flow logs](../observability/elastic/flow/datatypes.mdx)
-  - [Prometheus metrics](../operations/monitor/metrics/index.mdx#content-main)
+  - [Prometheus metrics](../operations/monitor/metrics/index.mdx)

calico-cloud/networking/configuring/bgp-to-workload.mdx

@@ -68,7 +68,7 @@ source traffic.
 ## How to
 
 - [Configure global BGP settings](#configure-global-bgp-settings)
-- [Create BGPFilter resources](#configure-bgpfilter-resources)
+- [Create BGPFilter resources](#create-bgpfilter-resources)
 - [Configure parent cluster BGP topology](#configure-parent-cluster-bgp-topology)
 - [Configure BGP peering with workloads](#configure-bgp-peering-with-workloads)
 - [Configure more than one nested cluster](#configure-more-than-one-nested-cluster)

calico-cloud/networking/configuring/dual-tor.mdx

@@ -208,7 +208,7 @@ For a dual ToR setup, LLGR is helpful, as explained in more detail by [this blog
 - [Prepare YAML resources describing the layout of your cluster](#prepare-yaml-resources-describing-the-layout-of-your-cluster)
 - [Arrange for dual-homed nodes to run $[nodecontainer] on each boot](#arrange-for-dual-homed-nodes-to-run-cnx-node-on-each-boot)
 - [Configure your ToR routers and infrastructure](#configure-your-tor-routers-and-infrastructure)
-- [Install Kubernetes and $[prodname]](#install-kubernetes-and-calico-enterprise)
+- [Install Kubernetes and $[prodname]](#install-kubernetes-and-calico-cloud)
 - [Verify the deployment](#verify-the-deployment)
 
 ### Prepare YAML resources describing the layout of your cluster

calico-cloud/networking/egress/egress-gateway-azure.mdx

@@ -98,7 +98,7 @@ $[prodname] CNI and IPAM are required. The ability to control the egress gateway
 - [Disable the default BGP node-to-node mesh](#disable-the-default-bgp-node-to-node-mesh)
 - [Enable BGP](#enable-bgp)
 - [Provision an egress IP pool](#provision-an-egress-ip-pool)
-- [(Optional) Limit number of route advertisement](#limit-number-of-route-advertisement)
+- [(Optional) Limit number of route advertisement](#optional-limit-number-of-route-advertisements)
 - [Configure route reflector](#configure-route-reflectors)
 - [Enable egress gateway support](#enable-egress-gateway-support)
 - [Deploy a group of egress gateways](#deploy-a-group-of-egress-gateways)

calico-cloud/observability/alerts.mdx

@@ -34,7 +34,7 @@ To turn down aggregation on flow logs, go to [FelixConfiguration](../reference/r
 
 ## How to
 
-- [Manage alerts in the web console](#manage-alerts-in-manager-ui)
+- [Manage alerts in the web console](#manage-alerts-in-the-web-console)
 - [Manage alerts using CLI](#manage-alerts-using-cli)
 
 ### Manage alerts in the web console

calico-cloud/observability/elastic/l7/configure.mdx

@@ -63,7 +63,7 @@ L7 logs require a minimum of 1 additional GB of log storage per node, per one-da
 
 1. Configure L7 log aggregation, retention, and reporting.
 
-   For help, see [Felix Configuration documentation](../../../reference/component-resources/node/felix/configuration.mdx#calico-enterprise-specific-configuration).
+   For help, see [Felix Configuration documentation](../../../reference/component-resources/node/felix/configuration.mdx).
 
 ## Configure L7 logs