Merge branch 'production' into dario/wrangler-versions-wrong-links

Author: kodster28

.github/CODEOWNERS

@@ -138,7 +138,7 @@
 /src/content/docs/workers/observability/ @irvinebroque @mikenomitch @rohinlohe @kodster28 @cloudflare/pcx-technical-writing
 /src/content/docs/workers/static-assets @irvinebroque @GregBrimble @WalshyDev @kodster28 @cloudflare/deploy-config @cloudflare/pcx-technical-writing
 /src/content/docs/workflows/ @elithrar @celso @cloudflare/pcx-technical-writing
-/src/content/docs/sandbox/ @whoiskatrin @ghostwriternr @cloudflare/pcx-technical-writing @ai-agents
+/src/content/docs/sandbox/ @whoiskatrin @ghostwriternr @cloudflare/pcx-technical-writing @cloudflare/ai-agents
 
 # DDoS Protection
 

src/assets/images/workers-ai/ibm.svg

@@ -10,6 +10,7 @@ import qwen from "../../assets/images/workers-ai/qwen.svg";
 import blackforestlabs from "../../assets/images/workers-ai/blackforestlabs.svg";
 import deepgram from "../../assets/images/workers-ai/deepgram.svg";
 import leonardo from "../../assets/images/workers-ai/leonardo.svg";
+import ibm from "../../assets/images/workers-ai/ibm.svg";
 
 export const authorData: Record<string, { name: string; logo: string }> = {
 	openai: {
@@ -64,4 +65,8 @@ export const authorData: Record<string, { name: string; logo: string }> = {
 		name: "Leonardo",
 		logo: leonardo.src,
 	},
+	"ibm-granite": {
+		name: "IBM",
+		logo: ibm.src,
+	},
 };

src/components/models/data.ts

@@ -105,7 +105,7 @@ You need to register your bot and its key directory to add your bot to the list
 <Steps>
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Manage Account** > **Configurations**.
-3. Go to the **Verified Bots** tab.
+3. Go to the **Bot Submission Form** tab.
 4. For **Verification Method**: select **Request Signature**.
 5. For **Validation Instructions**: enter the URL of your key directory. You can additionally supply User Agents values (and their match patterns) that will be sent by your bot.
 6. Select **Submit**.

src/content/docs/bots/reference/bot-verification/web-bot-auth.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 10
 ---
 
-Retro Scan allows you to scan up to 14 days of old messages in your Microsoft 365 inboxes and check if your current email security solution missed any threats. 
+Retro Scan allows you to scan up to 14 days of old messages in your Microsoft 365 inboxes and check if your current email security solution missed any threats. Once you receive your Retro Scan report, you will be able to remediate malicious messages.
 
 :::note
 Retro Scan is only available for Microsoft 365 accounts.

src/content/docs/cloudflare-one/email-security/retro-scan.mdx

@@ -85,3 +85,31 @@ In this case, Cloudflare will always resolve the CNAME target based on the value
       C
       end
 ```
+
+### Auth DNS points to `cdn.cloudflare.net`
+
+Considering the following scenario:
+
+- The target zone (Cloudflare zone 2 in this example) is a partial zone and the DNS record on the partial is proxied.
+- The DNS record on the authoritative DNS server points to `cdn.cloudflare.net`
+
+If such setup is in place, the subdomain (`www.partialzone.com` in this example) will resolve to a Cloudflare proxy IP, which will ultimately result in an error. Consider using [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) and [Orange-to-Orange](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) setup instead.
+
+```mermaid
+    flowchart TD
+      accTitle: DNS resolution flow with CNAME target in a zone within the same account and auth DNS pointing to cdn.cloudflare.net
+      A[Request to <code>www\.alice.com</code>] --> B[<code>CNAME</code> record for <code>www\.alice.com</code> to <code>www\.partialzone.com</code>]
+      B --> C[<code>CNAME</code> record for <code>www\.partialzone.com</code> to <code>www\.partialzone.com.cdn.cloudflare.net</code>]
+      C --> D[<code>Cloudflare proxy IP</code>]
+      subgraph Cloudflare account
+        subgraph Cloudflare zone 1
+          B
+        end
+        subgraph Cloudflare zone 2
+        E[Proxied <code>A</code> record for <code>www\.partialzone.com</code> to <code>203.0.113.1</code>]
+        end
+      end
+      subgraph Authoritative DNS
+      C
+      end
+```

src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx

@@ -1,6 +1,10 @@
 ---
-title: Cloudy AI agent
+title: Cloudy AI agent (beta)
 pcx_content_type: reference
+sidebar:
+  label: Cloudy AI agent
+  badge:
+    text: Beta
 ---
 
 Cloudy is Cloudflare's first version of an AI agent, with assistant-like functionality designed to help users understand and improve their Cloudflare configurations in multiple areas of the product suite.

src/content/docs/fundamentals/reference/cloudy-ai-agent.mdx

@@ -7,7 +7,7 @@ sidebar:
   order: 5
 ---
 
-import { Render } from "~/components";
+import { Render, FileTree } from "~/components";
 
 You can use a combination of Super Slurper and Sippy to effectively migrate all objects with minimal downtime.
 
@@ -25,4 +25,36 @@ You can use a combination of Super Slurper and Sippy to effectively migrate all
    - Note that Super Slurper may skip some objects if they are uploaded after it lists the objects to be copied.
 2. Enable Sippy on your R2 bucket, then start using the R2 bucket in your application.
    - New uploads will go to the R2 bucket.
-   - Objects which were uploaded while Super Slurper was copying the objects will be copied on-demand (by Sippy) when they are requested by the application.
+   - Objects which were uploaded while Super Slurper was copying the objects will be copied on-demand (by Sippy) when they are requested by the application.
+
+### Optimizing your Slurper data migration performance
+
+For an account, you can run three concurrent Slurper migration jobs at any given time, and each Slurper migration job can process a set amount of requests per second.
+
+To increase overall throughput and reliability, we recommend splitting your migration into smaller, concurrent jobs using the prefix (or bucket subpath) option.
+
+When creating a migration job:
+
+1. Go to the **Source bucket** step.
+2. Under **Define rules**, in **Bucket subpath**, specify subpaths to divide your data by prefix.
+3. Complete the data migration set up.
+
+For example, suppose your source bucket contains:
+
+<FileTree>
+- photos
+   - 2024
+         - file1.jpg
+         - file2.jpg
+   - 2023
+         - file3.jpg
+   - 2019
+         - file4.jpg
+</FileTree>
+
+You can create separate jobs with prefixes such as:
+
+- `/photos/2024` to migrate all 2024 files
+- `/photos/202` to migrate all files from 2023 and 2024
+
+Each prefix runs as an independent migration job, allowing Slurper to transfer data in parallel. This improves total transfer speed and ensures that a failure in one job does not interrupt the others.

src/content/docs/r2/data-migration/migration-strategies.mdx

@@ -265,7 +265,7 @@ The `.dev.vars` file is automatically gitignored and only used during local deve
 
 ## 5. Expose local server with Cloudflare Tunnel
 
-To test with real GitHub webhooks locally, use [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/) to expose your local development server.
+To test with real GitHub webhooks locally, use [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) to expose your local development server.
 
 Start the development server:
 
@@ -282,7 +282,7 @@ cloudflared tunnel --url http://localhost:8787
 This will output a public URL (for example, `https://example.trycloudflare.com`). Copy this URL for the next step.
 
 :::note
-If you do not have `cloudflared` installed, refer to [Install cloudflared](/cloudflare-one/connections/connect-networks/downloads/).
+If you do not have `cloudflared` installed, refer to [Downloads](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/).
 :::
 
 ## 6. Configure GitHub webhook for local testing

src/content/docs/sandbox/tutorials/code-review-bot.mdx

@@ -1,6 +1,8 @@
 ---
 pcx_content_type: concept
 title: File conventions
+sidebar:
+  order: 6
 ---
 
 Our docs have a few conventions around files.