Merging to release-5.12: DX-2362: Fix 163 broken internal anchor fragment links 2 (#1867)

DX-2362: Fix 163 broken internal anchor fragment links 2 (#1867)

Author: buger

.github/workflows/check-external-links.yml

@@ -1,7 +1,8 @@
 name: Check External Links
 
 on:
-  pull_request:
+  schedule:
+    - cron: '0 9 * * 1'  # Every Monday at 09:00 UTC
   workflow_dispatch:
 
 permissions:
@@ -20,4 +21,4 @@ jobs:
       uses: lycheeverse/lychee-action@v2
       with:
         args: --config lychee.toml '**/*.md' '**/*.mdx'
-        fail: true
+        fail: false

ai-management/ai-studio/analytics.mdx

@@ -29,7 +29,7 @@ The primary point of data collection is the **[Proxy & API Gateway](/ai-manageme
 
 1.  **Request Details:** Information about the incoming request is captured (e.g., user ID, application ID, requested LLM/route, timestamp).
 2.  **LLM Interaction:** Details about the interaction with the backend LLM are recorded (e.g., model used, prompt tokens, completion tokens, latency).
-3.  **Cost Calculation:** Using data from the [Model Pricing System](/ai-management/ai-studio/llm-management#model-pricing), the cost of the interaction is calculated based on token counts.
+3.  **Cost Calculation:** Using data from the [Model Pricing System](/ai-management/ai-studio/ai-studio#model-pricing), the cost of the interaction is calculated based on token counts.
 4.  **Tool Usage:** If the interaction involved [Tools](/ai-management/ai-studio/tools), relevant details might be logged (e.g., which tool was called, success/failure).
 5.  **Chat Context:** For interactions originating from the [Chat Interface](/ai-management/ai-studio/chat-interface), metadata about the chat session might be included.
 
@@ -89,6 +89,6 @@ Administrators typically access analytics data via dashboards within the Tyk AI
 ## Integration with Other Systems
 
 *   **[Budget Control](/ai-management/ai-studio/budgeting):** Analytics data (specifically cost) is likely used by the Budget Control system to track spending against defined limits.
-*   **[Model Pricing](/ai-management/ai-studio/llm-management#model-pricing):** The pricing definitions are crucial for calculating the cost metric within the analytics system.
+*   **[Model Pricing](/ai-management/ai-studio/ai-studio#model-pricing):** The pricing definitions are crucial for calculating the cost metric within the analytics system.
 
 By providing detailed analytics, Tyk AI Studio enables organizations to effectively manage costs, understand usage patterns, and ensure the optimal performance of their AI interactions.

ai-management/ai-studio/budgeting.mdx

@@ -70,7 +70,7 @@ This provides **eventually-accurate** budget control. There may be a slight over
 ## Integration with Other Systems
 
 *   **[Analytics & Monitoring](/ai-management/ai-studio/analytics):** The Analytics system provides the cost data used to track spending against budgets. The current spent amount for a budget period is derived from aggregated analytics data.
-*   **[Model Pricing](/ai-management/ai-studio/llm-management#model-pricing):** The pricing definitions are essential for the Analytics system to calculate costs accurately, which in turn feeds the Budget Control system.
+*   **[Model Pricing](/ai-management/ai-studio/ai-studio#model-pricing):** The pricing definitions are essential for the Analytics system to calculate costs accurately, which in turn feeds the Budget Control system.
 *   **[Notification System](/ai-management/ai-studio/notifications):** Budgets trigger notifications when spending reaches defined thresholds. The system supports alerts at **50%**, **80%**, **90%**, and **100%** of the budget limit. Administrators receive notifications when these thresholds are crossed.
 
 ## Benefits

ai-management/ai-studio/plugins/edge-gateway.mdx

@@ -101,10 +101,10 @@ Intercepts data before database storage. Use for:
 - Real-time monitoring and alerting
 
 **Working Examples**:
-- [`examples/plugins/unified/data-collectors/file-analytics-collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/unified/data-collectors/file-analytics-collector) (unified SDK)
-- [`examples/plugins/unified/data-collectors/file-budget-collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/unified/data-collectors/file-budget-collector) (unified SDK)
-- [`examples/plugins/unified/data-collectors/file-proxy-collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/unified/data-collectors/file-proxy-collector) (unified SDK)
-- [`examples/plugins/gateway/elasticsearch_collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/gateway/elasticsearch_collector)
+- [`examples/plugins/data-collectors/file-analytics-collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/data-collectors/file-analytics-collector) (unified SDK)
+- [`examples/plugins/data-collectors/file-budget-collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/data-collectors/file-budget-collector) (unified SDK)
+- [`examples/plugins/data-collectors/file-proxy-collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/data-collectors/file-proxy-collector) (unified SDK)
+- [`examples/plugins/gateway/legacy-collectors/elasticsearch_collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/gateway/legacy-collectors/elasticsearch_collector)
 
 ### 6. CustomEndpointHandler
 
@@ -500,7 +500,7 @@ func main() {
 }
 ```
 
-**Working Example**: See [`community/plugins/llm-firewall/`](https://github.com/TykTechnologies/ai-studio/tree/main/community/plugins/llm-firewall) for a production-ready content filtering plugin using this pattern.
+**Working Example**: See [`plugins/llm-firewall/`](https://github.com/TykTechnologies/ai-studio-community-plugins/tree/main/plugins/llm-firewall) for a production-ready content filtering plugin using this pattern.
 
 ### Example 2: Elasticsearch Data Collector
 

ai-management/ai-studio/plugins/examples.mdx

@@ -26,7 +26,7 @@ The following plugins in `community/plugins/` and `enterprise/plugins/` are **pr
 
 #### LLM Cache
 
-**Path**: [`community/plugins/llm-cache/`](https://github.com/TykTechnologies/ai-studio/tree/main/community/plugins/llm-cache)
+**Path**: [`plugins/llm-cache/`](https://github.com/TykTechnologies/ai-studio-community-plugins/tree/main/plugins/llm-cache)
 
 **Capabilities**: PostAuth, Response, StreamComplete, UI, RPC, EdgePayloadReceiver, SessionAware, Config
 
@@ -51,7 +51,7 @@ The following plugins in `community/plugins/` and `enterprise/plugins/` are **pr
 
 #### LLM Firewall
 
-**Path**: [`community/plugins/llm-firewall/`](https://github.com/TykTechnologies/ai-studio/tree/main/community/plugins/llm-firewall)
+**Path**: [`plugins/llm-firewall/`](https://github.com/TykTechnologies/ai-studio-community-plugins/tree/main/plugins/llm-firewall)
 
 **Capabilities**: PreAuth, PostAuth, Config
 
@@ -75,7 +75,7 @@ The following plugins in `community/plugins/` and `enterprise/plugins/` are **pr
 
 #### GitHub RAG Ingest
 
-**Path**: [`community/plugins/github-rag-ingest/`](https://github.com/TykTechnologies/ai-studio/tree/main/community/plugins/github-rag-ingest)
+**Path**: [`plugins/github-rag-ingest/`](https://github.com/TykTechnologies/ai-studio-community-plugins/tree/main/plugins/github-rag-ingest)
 
 **Capabilities**: UI, RPC, Scheduler, SessionAware
 
@@ -103,8 +103,6 @@ The following plugins in `community/plugins/` and `enterprise/plugins/` are **pr
 
 #### LLM Load Balancer
 
-**Path**: [`enterprise/plugins/llm-load-balancer/`](https://github.com/TykTechnologies/ai-studio/tree/main/enterprise/plugins/llm-load-balancer)
-
 **Capabilities**: PostAuth, Response, UI
 
 **Description**: Intelligent request distribution across multiple LLM backends with health checking and failover.
@@ -115,8 +113,6 @@ The following plugins in `community/plugins/` and `enterprise/plugins/` are **pr
 
 #### Advanced LLM Cache
 
-**Path**: [`enterprise/plugins/advanced-llm-cache/`](https://github.com/TykTechnologies/ai-studio/tree/main/enterprise/plugins/advanced-llm-cache)
-
 **Capabilities**: PostAuth, Response, UI
 
 **Description**: Extended caching with semantic similarity matching, cache invalidation policies, and advanced analytics. Extends the community LLM Cache.
@@ -422,7 +418,7 @@ The following examples in `examples/plugins/` demonstrate specific patterns and
 
 ### Elasticsearch Collector
 
-**Path**: [`examples/plugins/gateway/elasticsearch_collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/gateway/elasticsearch_collector)
+**Path**: [`examples/plugins/gateway/legacy-collectors/elasticsearch_collector/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/gateway/legacy-collectors/elasticsearch_collector)
 
 **Capabilities**: DataCollector
 
@@ -500,7 +496,7 @@ The following examples in `examples/plugins/` demonstrate specific patterns and
 
 ### File Data Collectors (Unified SDK)
 
-**Path**: [`examples/plugins/unified/data-collectors/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/unified/data-collectors)
+**Path**: [`examples/plugins/data-collectors/`](https://github.com/TykTechnologies/ai-studio/tree/main/examples/plugins/data-collectors)
 
 **Capabilities**: DataCollector
 

ai-management/ai-studio/plugins/studio-ui.mdx

@@ -97,7 +97,7 @@ my-ui-plugin/
 
 ### 2. Create Manifest
 
-[server/plugin.manifest.json](https://github.com/TykTechnologies/ai-studio/blob/main/examples/plugins/studio/custom-auth-ui/server/plugin.manifest.json):
+[server/manifest.json](https://github.com/TykTechnologies/ai-studio/blob/main/examples/plugins/studio/custom-auth-ui/server/manifest.json):
 
 ```json Expandable
 {

ai-management/mcps/tyk-docs-mcp.mdx

@@ -7,7 +7,7 @@ sidebarTitle: "Tyk Docs MCP"
 
 ## Overview
 
-*Tyk Docs MCP* is a tool [MCP server](https://github.com/modelcontext/spec) exposing the Tyk documentation to connected AI assistants. It enables the users of AI assistants "talk to" Tyk's documentation. Instead of searching manually, users can ask natural-language questions — and get answers backed by Tyk official docs. The tool makes AI-assisted support, troubleshooting, and documentation exploration fast and reliable.
+*Tyk Docs MCP* is a tool [MCP server](https://modelcontextprotocol.io/introduction) exposing the Tyk documentation to connected AI assistants. It enables the users of AI assistants "talk to" Tyk's documentation. Instead of searching manually, users can ask natural-language questions — and get answers backed by Tyk official docs. The tool makes AI-assisted support, troubleshooting, and documentation exploration fast and reliable.
 
 
 Here you can see the AI assistant chooses to use Tyk Docs MCP (*Cline* in VS Code) while answering the query *How do I set a rate limit for a Tyk API?*:

api-management/authentication/bearer-token.mdx

@@ -117,7 +117,7 @@ You can use your own identity provider to generate access tokens, then import th
   *Dynamic mTLS* became a standalone authentication method in Tyk 5.12.0 and is now more accurately called [Certificate Authentication](/api-management/authentication/certificate-auth)
 </Note>
 
-Prior to Tyk 5.12.0, [Dynamic mTLS](/api-management/implement-tls#configuring-mtls-with-a-dynamic-allow-list) was configured via the Auth Token method by setting the `enableClientCertificate` flag (Tyk Classic: `auth_configs.authToken.use_certificate`).
+Prior to Tyk 5.12.0, [Dynamic mTLS](/api-management/implement-tls#using-a-dynamic-client-certificate-allow-list) was configured via the Auth Token method by setting the `enableClientCertificate` flag (Tyk Classic: `auth_configs.authToken.use_certificate`).
 
 ```json
 server:
@@ -129,7 +129,7 @@ server:
           enableClientCertificate: true
 ```
 
-This was later changed to Certificate Authentication, as explained [here](/api-management/implement-tls#dynamc-mtls-problem).
+This was later changed to Certificate Authentication, as explained [here](/api-management/implement-tls#legacy-dynamic-mtls-mode).
 
 ### Auth Token with Signature
 

api-management/authentication/jwt-authorization.mdx

@@ -15,7 +15,7 @@ sidebarTitle: "Authorization"
 
 [JSON Web Tokens (JWT)](https://www.jwt.io/introduction) are a popular method for client authentication and authorization that can be used to secure access to your APIs via Tyk's [JWT Auth](/basic-config-and-security/security/authentication-authorization/json-web-tokens) method.
 
-After the JWT signature has been [validated](/basic-config-and-security/security/authentication-authorization/json-web-tokens#signature-validation), Tyk uses the **claims** within the token to determine which security policies (access rights, rate limits and quotas) should be applied to the request.
+After the JWT signature has been [validated](/basic-config-and-security/security/authentication-authorization/json-web-tokens), Tyk uses the **claims** within the token to determine which security policies (access rights, rate limits and quotas) should be applied to the request.
 
 From Tyk 5.10, Tyk can perform optional [validation](/api-management/authentication/jwt-claim-validation) of these claims.
 

api-management/authentication/jwt-claim-validation.mdx

@@ -85,7 +85,7 @@ JWT claims can be categorized into two types:
 
 ### How Tyk Processes JWT Claims
 
-After [verifying](/basic-config-and-security/security/authentication-authorization/json-web-tokens#signature-validation) that the token hasn't been tampered with, Tyk processes claims in this order:
+After [verifying](/basic-config-and-security/security/authentication-authorization/json-web-tokens) that the token hasn't been tampered with, Tyk processes claims in this order:
 
 1. **Claims Extraction**: All claims from the JWT payload are extracted and stored in [context variables](/api-management/traffic-transformation/request-context-variables) with the format `jwt_claims_CLAIMNAME`. For example, a claim named `role` becomes accessible as `jwt_claims_role`.