Resolve merge conflict, match HEAD

Author: Oxyjun

public/__redirects

@@ -532,7 +532,7 @@
 /durable-objects/api/hibernatable-websockets-api/ /durable-objects/best-practices/websockets/ 301
 /durable-objects/api/alarms-in-durable-objects/ /durable-objects/api/alarms/ 301
 /durable-objects/api/websockets/ /durable-objects/best-practices/websockets/ 301
-/durable-objects/api/sql-storage/ /durable-objects/api/storage-api/ 301
+/durable-objects/api/sql-storage/ /durable-objects/api/sqlite-storage-api/ 301
 /durable-objects/platform/data-location/ /durable-objects/reference/data-location/ 301
 /durable-objects/platform/environments/ /durable-objects/reference/environments/ 301
 /durable-objects/platform/troubleshooting/ /durable-objects/observability/troubleshooting/ 301
@@ -547,7 +547,7 @@
 /durable-objects/reference/error-handling/ /durable-objects/best-practices/error-handling/ 301
 /durable-objects/reference/troubleshooting/ /durable-objects/observability/troubleshooting/ 301
 /durable-objects/reference/websockets/ /durable-objects/best-practices/websockets/ 301
-/durable-objects/api/transactional-storage-api/ /durable-objects/api/storage-api/ 301
+/durable-objects/api/transactional-storage-api/ /durable-objects/api/sqlite-storage-api/ 301
 /durable-objects/platform/changelog/ /durable-objects/release-notes/ 301
 /durable-objects/changelog/ /durable-objects/release-notes/ 301
 /durable-objects/glossary/ /durable-objects/reference/glossary/ 301

public/robots.txt

@@ -1,11 +1,42 @@
+# As a condition of accessing this website, you agree to
+# abide by the following content signals:
+
+# (a)  If a content-signal = yes, you may collect content
+# for the corresponding use.
+# (b)  If a content-signal = no, you may not collect content
+# for the corresponding use.
+# (c)  If the website operator does not include a content
+# signal for a corresponding use, the website operator
+# neither grants nor restricts permission via content signal
+# with respect to the corresponding use.
+
+# The content signals and their meanings are:
+
+# search: building a search index and providing search
+# results (e.g., returning hyperlinks and short excerpts
+# from your website's contents).  Search does not include
+# providing AI-generated search summaries.
+# ai-input: inputting content into one or more AI models
+# (e.g., retrieval augmented generation, grounding, or other
+# real-time taking of content for generative AI search
+# answers).
+# ai-train: training or fine-tuning AI models.
+
+# ANY RESTRICTIONS EXPRESSED VIA CONTENT-SIGNALS ARE EXPRESS
+# RESERVATIONS OF RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN
+# UNION DIRECTIVE 2019/790 ON COPYRIGHT AND RELATED RIGHTS
+# IN THE DIGITAL SINGLE MARKET.
+
 User-agent: *
 
+Allow: /
 Disallow: /client-ip-geolocation
 Disallow: /plans/
 Disallow: /constellation
 Disallow: /cdn-cgi/
 Disallow: /email-security/
 
 Content-Usage: tdm=y
+Content-Signal: ai-train=yes, search=yes, ai-input=yes
 
-Sitemap: https://developers.cloudflare.com/sitemap-index.xml
+Sitemap: https://developers.cloudflare.com/sitemap-index.xml

src/assets/images/changelog/dns/DNSFW_Analytics_UI.png

@@ -0,0 +1,38 @@
+---
+title: DNS Firewall Analytics — now in the Cloudflare dashboard
+description: Quickly set up common rules with pre-built templates.
+date: 2025-09-16
+---
+
+import { DashButton } from "~/components";
+
+# What's New
+
+Access [GraphQL-powered DNS Firewall analytics](/dns/dns-firewall/analytics/) directly in the Cloudflare dashboard.
+
+![DNS Firewall Analytics UI](~/assets/images/changelog/dns/DNSFW_Analytics_UI.png)
+
+## Explore Four Interactive Panels
+
+- **Query summary**: Describes trends over time, segmented by dimensions.  
+- **Query statistics**: Describes totals, cached/uncached queries, and processing/response times.  
+- **DNS queries by data center**: Describes global view and the top 10 data centers.  
+- **Top query statistics**: Shows a breakdown by key dimensions, with search and expand options (up to top 100 items).  
+
+Additional features:  
+
+- Apply filters and time ranges once. Changes reflect across all panels.  
+- Filter by dimensions like query name, query type, cluster, data center, protocol (UDP/TCP), IP version, response code/reason, and more.  
+- Access up to 62 days of historical data with flexible intervals.  
+
+## Availability
+
+Available to all DNS Firewall customers as part of their existing subscription.
+
+## Where to Find It
+
+- In the Cloudflare dashboard, go to the **DNS Firewall** page. 
+
+ <DashButton url="/?to=/:account/dns-firewall" /> 
+
+- Refer to the [DNS Firewall Analytics](/dns/dns-firewall/analytics/) to learn more.

src/content/changelog/dns/2025-09-16-DNSFW-Analytics-UI.mdx

@@ -9,7 +9,7 @@ date: 2025-04-07
 
 SQLite in Durable Objects is now generally available (GA) with 10GB SQLite database per Durable Object. Since the [public beta](https://blog.cloudflare.com/sqlite-in-durable-objects/) in September 2024, we've added feature parity and robustness for the SQLite storage backend compared to the preexisting key-value (KV) storage backend for Durable Objects.
 
-SQLite-backed Durable Objects are recommended for all new Durable Object classes, using `new_sqlite_classes` [Wrangler configuration](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class). Only SQLite-backed Durable Objects have access to Storage API's [SQL](/durable-objects/api/storage-api/#sql-api) and [point-in-time recovery](/durable-objects/api/storage-api/#pitr-point-in-time-recovery-api) methods, which provide relational data modeling, SQL querying, and better data management.
+SQLite-backed Durable Objects are recommended for all new Durable Object classes, using `new_sqlite_classes` [Wrangler configuration](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class). Only SQLite-backed Durable Objects have access to Storage API's [SQL](/durable-objects/api/sqlite-storage-api/#sql-api) and [point-in-time recovery](/durable-objects/api/sqlite-storage-api/#pitr-point-in-time-recovery-api) methods, which provide relational data modeling, SQL querying, and better data management.
 
 ```js
 export class MyDurableObject extends DurableObject {

src/content/changelog/durable-objects/2025-04-07-sqlite-in-durable-objects-ga.mdx

@@ -70,7 +70,7 @@ Calling `await this.schedule` returns a `Schedule`, which includes the task's ra
 
 :::note[Maximum scheduled tasks]
 
-Each task is mapped to a row in the Agent's underlying [SQLite database](/durable-objects/api/storage-api/), which means that each task can be up to 2 MB in size. The maximum number of tasks must be `(task_size * tasks) + all_other_state < maximum_database_size` (currently 1GB per Agent).
+Each task is mapped to a row in the Agent's underlying [SQLite database](/durable-objects/api/sqlite-storage-api/), which means that each task can be up to 2 MB in size. The maximum number of tasks must be `(task_size * tasks) + all_other_state < maximum_database_size` (currently 1GB per Agent).
 
 :::
 

src/content/docs/agents/api-reference/schedule-tasks.mdx

@@ -227,7 +227,7 @@ Learn more about the zero-latency SQL storage that powers both Agents and Durabl
 
 :::
 
-The SQL API exposed to an Agent is similar to the one [within Durable Objects](/durable-objects/api/storage-api/#sql-api): Durable Object SQL methods available on `this.ctx.storage.sql`. You can use the same SQL queries with the Agent's database, create tables, and query data, just as you would with Durable Objects or [D1](/d1/).
+The SQL API exposed to an Agent is similar to the one [within Durable Objects](/durable-objects/api/sqlite-storage-api/#sql-api): Durable Object SQL methods available on `this.ctx.storage.sql`. You can use the same SQL queries with the Agent's database, create tables, and query data, just as you would with Durable Objects or [D1](/d1/).
 
 ### Use Agent state as model context
 

src/content/docs/agents/api-reference/store-and-sync-state.mdx

@@ -1,6 +1,8 @@
 ---
 title: AI Gateway Binding Methods
 pcx_content_type: tutorial
+tags:
+  - Bindings
 reviewed: 2025-04-01
 ---
 

src/content/docs/ai-gateway/integrations/worker-binding-methods.mdx

@@ -13,7 +13,7 @@ https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openrouter
 
 ## URL structure
 
-When making requests to [OpenRouter](https://openrouter.ai/), replace `https://openrouter.ai/api/v1/chat/completions` in the URL you are currently using with `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openrouter`.
+When making requests to [OpenRouter](https://openrouter.ai/), replace `https://openrouter.ai/api/v1/chat/completions` in the URL you are currently using with `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openrouter/chat/completions`.
 
 ## Prerequisites
 

src/content/docs/ai-gateway/usage/providers/openrouter.mdx

@@ -1,6 +1,8 @@
 ---
 pcx_content_type: concept
 title: Workers Binding
+tags:
+  - Bindings
 sidebar:
   order: 3
 ---