Brendan Irvine-Broque

This commit **updates the Bonk GitHub Actions workflow** by adding `pull_request_review` with type `submitted` as a new trigger event. This **chore** ensures that the `Bonk` action is now automatically invoked when a pull request review is formally submitted, rather than solely for individual comments. By expanding the trigger conditions for the **CI/CD automation**, the project's **review process integration** becomes more robust, leveraging the `Bonk` action's existing capabilities for this event type. This change improves the **workflow's responsiveness to review activities** within the development pipeline.

This change affects the `create-cloudflare` (C3) project creation tool; all new projects generated by C3 will now default to having `nodejs_compat` enabled, potentially impacting their runtime environment and compatibility with Node.js APIs.

This commit **introduces a new documentation guide** detailing how to build **microfrontend architectures using Workers**. The guide, located at `src/content/docs/workers/framework-guides/web-apps/microfrontends.mdx`, provides comprehensive instructions on leveraging router workers and service bindings for microfrontend implementation. It covers critical aspects such as routing logic, path rewriting, asset handling, preloading, and deployment workflows. This **enhances the Workers documentation** by offering a complete resource for developers looking to adopt this architectural pattern, alongside a corresponding changelog entry.

This fixes an issue in `workers-utils` where `create-cloudflare` could use an incorrect, hardcoded compatibility date due to a module resolution error. Projects created or updated with `create-cloudflare` will now correctly detect and apply the appropriate `miniflare` compatibility date.

This commit **significantly enhances the visual presentation and customization of Mermaid diagrams** across the platform. It introduces custom theming, Cloudflare branding, and improved styling through new JavaScript logic in `src/scripts/mermaid.ts` and comprehensive CSS updates in `src/styles/mermaid.css`. Specifically, functions like `getFontFamily` and `wrapDiagram` now ensure diagrams are consistently branded and titled. Furthermore, a new **documentation guide** in `src/scripts/MERMAID.md` details the rendering process, usage, and customization options. This **feature enhancement and styling update** provides users with more aesthetically pleasing and readable diagrams, while offering developers clear guidance on their integration.

This commit **enhances the documentation** for **Cloudflare for SaaS**, specifically clarifying how **custom hostname traffic is routed to Workers when used as an origin**. It adds new sections and concrete examples to `src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx`, detailing the traffic flow through the SaaS zone and the relationship between various routing components. The update also clarifies the behavior of wildcard route patterns like `*/*` and rewrites routing options for improved understanding. Furthermore, it includes a scenario for routing only a subset of custom hostnames to a Worker, providing users with a more comprehensive understanding of configuration options and addressing previous ambiguities. This **documentation enhancement** helps users correctly configure and troubleshoot custom hostname routing to Workers.

This commit **updates the documentation** for the **Analytics Engine** to reflect a significant increase in processing capacity. Specifically, it modifies `src/content/docs/analytics/analytics-engine/limits.mdx` to state that the maximum number of data points allowed per **Worker invocation** has been raised from 25 to 250. This is a **documentation update** that provides users with accurate information regarding the expanded capabilities of the Analytics Engine. The change ensures that developers are aware of the higher throughput now supported for data ingestion via Worker invocations.

This commit performs a significant **documentation update** by renaming the existing Svelte framework guide to **SvelteKit** within the **Workers documentation**. The guide's content, title, and description in `src/content/docs/workers/framework-guides/web-apps/sveltekit.mdx` have been updated to consistently refer to SvelteKit, reflecting the modern approach to building Svelte applications. To ensure a seamless user experience and prevent broken links, a **301 redirect** has been added in `public/__redirects` from the old Svelte guide URL to the new SvelteKit URL. Additionally, internal links referencing the guide, such as in the changelog, have been updated to point to the new location. This **maintenance** task improves the accuracy and discoverability of the framework guides for users.

This commit provides a crucial **documentation update** to the `worker-loader.mdx` file, clarifying the production usage requirements for the **Worker Loader API**. It explicitly states that **dynamic Workers** leveraging this API currently necessitate signing up for a **closed beta** to run successfully on Cloudflare. This **maintenance** work ensures users are aware of the current limitations and access requirements for deploying such Workers, preventing potential deployment issues or confusion regarding the **Cloudflare Workers** platform.

This commit **enhances the documentation** for **Tail Workers** by adding a critical note within the `observability/logs` section. The new content clarifies when to utilize **OpenTelemetry** for exporting logs and traces, distinguishing its use cases from those of Tail Workers. This **documentation update** provides users with better guidance on selecting the appropriate tool for their **Cloudflare Workers observability strategy**, improving clarity and preventing potential misconfigurations.

This commit **updates the documentation** for **Node.js compatibility flags**, specifically within the `src/content/compatibility-flags/nodejs-compat.md` file. It **enhances user guidance** by incorporating a new table that outlines API compatibility dates for various features. Additionally, the update provides **recommendations for maximizing compatibility**, offering practical advice to developers. This **documentation improvement** aims to give users a clearer understanding of Node.js API compatibility and how to best manage it.

This commit enhances the internal GitHub workflow helper for auto-assigning issues, introducing a new capability to incorporate issue owners into the assignment logic. This improves the automation of issue management within the repository.

Isolated change to internal development tooling; updates the automatic assignment of issues related to "pages" within GitHub workflows. No production impact.

This commit performs a **documentation update** by removing a specific sentence from the `src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx` guide. The removed sentence previously recommended Cloudflare Workers over Cloudflare Pages for new projects. This change clarifies the guidance within the **Cloudflare Workers** and **Cloudflare Pages migration documentation**, ensuring a more neutral stance on project recommendations. The scope is limited to the documentation, but it impacts how users perceive and choose between these two Cloudflare services.

This commit introduces a new GitHub Action and associated tooling to automate issue assignment based on labels and configured teams. This new capability streamlines issue management workflows by automatically assigning issues, improving efficiency.

This commit **updates the documentation** for **Cloudflare Pages** by adding a new changelog entry to `src/content/changelog/pages/2025-05-30-pages-build-image-v3.mdx`. It formally announces the release of the **Cloudflare Pages build image v3**, highlighting its inclusion of **Node.js v22** as the default runtime. This **documentation update** serves as a critical **maintenance task** to inform users about significant changes to the build environment, enabling them to adapt their projects or leverage the new Node.js version.

This commit provides a crucial **documentation update** for the **Wrangler CLI**, specifically targeting the `wrangler check startup` command. It adds a clarifying note to `src/content/docs/workers/wrangler/commands.mdx`, explaining that the CPU profile generated is produced locally and may not accurately reflect performance in a Cloudflare production environment. This **enhances user understanding** by preventing misinterpretations of startup times and performance variability. The update ensures users are aware of the diagnostic tool's scope and limitations, leading to more informed development decisions.

This commit **enhances the Cloudflare One identity documentation** by adding a **new example demonstrating JWT validation within a Cloudflare Worker**. Specifically, the `src/content/docs/cloudflare-one/identity/authorization-cookie/validating-json.mdx` file is updated to provide practical guidance for developers using Cloudflare Workers for authorization. The existing JavaScript example is also clarified to explicitly specify Node.js, improving the accuracy and specificity of the provided code samples. This **documentation enhancement** helps users implement secure identity solutions more effectively by offering a relevant, platform-specific example.

This commit **updates terminology** within the **Workers Builds limits and pricing documentation** to enhance clarity and accuracy. Specifically, it replaces all mentions of 'CPU' with 'vCPU' in the `src/content/docs/workers/ci-cd/builds/limits-and-pricing.mdx` file. This **documentation update** ensures consistent language regarding resource allocation, improving user understanding of the specifications and costs for Workers Builds.

This commit **introduces a new documentation page** for **AI agents**, detailing common **design patterns** for their implementation. The new page, located at `src/content/docs/agents/patterns.mdx`, provides comprehensive guidance on architectural concepts like prompt chaining, routing, parallelization, orchestrator-workers, and evaluator-optimizer. This **enhances the documentation** by offering valuable educational content, improving user understanding and facilitating the adoption of advanced AI agent architectures. The work involved creating the initial content, integrating images and links, and refining the text based on reviews.