feat(relay): Update docs to clarify that managed mode is available for all and static mode is gone

develop-docs/backend/application-domains/pii/index.mdx

@@ -68,39 +68,6 @@ some SDK. Go to our PII config editor [Piinguin], and:
 3. Paste in other payloads and see if they look fine, go to step **2** if
    necessary.
 
-After iterating on the config, paste it back into the project config located at
-`.relay/projects/<PROJECT_ID>.json`
-
-For example:
-
-```json
-{
-  "publicKeys": [
-    {
-      "publicKey": "___PUBLIC_KEY___",
-      "isEnabled": true
-    }
-  ],
-  "config": {
-    "allowedDomains": ["*"],
-    "piiConfig": {
-      "rules": {
-        "device_id": {
-          "type": "pattern",
-          "pattern": "d/[a-f0-9]{12}",
-          "redaction": {
-            "method": "hash"
-          }
-        }
-      },
-      "applications": {
-        "freeform": ["device_id"]
-      }
-    }
-  }
-}
-```
-
 [advanced data scrubbing]: https://docs.sentry.io/product/data-management-settings/scrubbing/advanced-datascrubbing/
 [relay]: https://github.com/getsentry/relay
 [piinguin]: https://getsentry.github.io/piinguin

develop-docs/backend/application-domains/transaction-clustering/index.mdx

@@ -7,7 +7,6 @@ Sentry attempts to scrub high-cardinality identifiers from URL transactions
 to aggregate performance data and provide more valuable insights.
 
 In terms of user experience, this feature plays a similar role as [Issue Grouping](/backend/grouping/).
-In terms of technical implementation, it is similar to [Data Scrubbing](/backend/pii/).
 
 ## The Problem
 

docs/product/relay/getting-started.mdx

@@ -55,12 +55,6 @@ _"create custom config"_ and customizing these parameters:
 
 - The `mode` setting, which configures the major mode in which Relay operates. For more information on available Relay modes, refer to [Relay Modes](../modes/).
 
-  <Alert level="warning">
-
-  Currently, only `proxy` and `static` mode are available to all organizations. Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).
-
-  </Alert>
-
 - The `upstream` setting configures the server to which Relay will forward the
   events (by default the main `sentry.io` URL).
 
@@ -96,7 +90,7 @@ Configurations are fully documented in [Configuration Options](../options/).
 
 <Alert>
 
-Not applicable in `proxy` or `static` mode.
+Not applicable in `proxy` mode.
 
 </Alert>
 
@@ -120,7 +114,7 @@ Use the `public_key` to register your Relay with the upstream server when runnin
 
 <Alert>
 
-Not applicable in `proxy` or `static` mode.
+Not applicable in `proxy` mode.
 
 </Alert>
 

docs/product/relay/index.mdx

@@ -12,12 +12,6 @@ Relay is specifically designed to:
 - Improve event response time in regions with low bandwidth or limited connectivity
 - Act as an opaque proxy for organizations that restrict all HTTP communication to a custom domain name
 
-<Alert>
-
-Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).
-
-</Alert>
-
 ## Use Cases for Relay
 
 Relay is designed to support organizations that have specific enterprise security requirements for data scrubbing of personally identifiable information (PII), response time, and enterprise domain management.

docs/product/relay/modes/index.mdx

@@ -6,13 +6,7 @@ sidebar_order: 2
 
 Relay can operate in one of several major modes, and it is critical to understand the modes prior if you are configuring the Relay server rather than using the default settings.
 
-The mode is stored in the configuration file, which contains the `relay.mode` field. This field specifies the mode in which Relay will run: `managed`, `static`, or `proxy`. The Relay mode controls the way Relay obtains project settings for events.
-
-<Alert>
-
-Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).
-
-</Alert>
+The mode is stored in the configuration file, which contains the `relay.mode` field. This field specifies the mode in which Relay will run: `managed` or `proxy`. The Relay mode controls whether or not Relay obtains project settings for events.
 
 In Sentry, event processing is configured according to both project and organization settings. Some settings, such as privacy controls, are set at the organization level, then inherited by all projects in that organization; other settings are specified per project. For Relay, events are processed according to the inherited project settings to which the event is sent.
 
@@ -34,43 +28,13 @@ relay:
   mode: managed
 ```
 
-## Static Mode
-
-In static mode, projects must be configured manually. In this mode, Relay will process events for only statically configured projects, and reject events for all other projects.
-
-This mode is useful when you know the projects sending events and you need to explicitly control the projects allowed to send events through this Relay.
-
-<Alert title="Note">
-
-In `static` mode, Relay does not register with upstream since it does not query
-information from it. After processing events for configured projects, it
-forwards them upstream with the authentication information (DSN) set by
-the client that sent the original request.
-
-</Alert>
-
-To activate static mode, set this configuration:
-
-```yaml
-relay:
-  mode: static
-```
-
-To configure projects, add files using the format `projects/<PROJECT_ID>.json` to your Relay configuration folder. For a description of the contents of this file,
-refer to [Project Configuration](/product/relay/projects/).
-
 ## Proxy Mode
 
-Proxy mode is similar to `static` mode, but it forwards events from unknown
-projects. In this mode, events for statically configured projects are handled
-identically to `static` mode. Events for unknown projects -- projects for which
-there are no statically configured settings -- are forwarded (proxied) with
-minimal processing.
+Proxy mode forwards all events with minimal processing and does not receive any project settings from Sentry.
 
 <Alert title="Rate Limiting">
 
-Rate limiting is still applied in `proxy` mode for all projects,
-regardless of whether they are statically configured or proxied.
+Rate limiting is still applied in `proxy` mode for all projects.
 
 </Alert>
 
@@ -80,3 +44,7 @@ To activate proxy mode, set this configuration:
 relay:
   mode: proxy
 ```
+
+## Static Mode
+
+Static mode has been deprecated as of Relay version 25.9.0. Please use `managed` or `proxy` mode instead. When switching to `managed` mode don't forget to migrate any local scrubbing rules by configuring them in the Sentry UI.

docs/product/relay/options.mdx

@@ -24,7 +24,7 @@ Credentials can be initiated as described in the [getting started page](/product
 
 | key                        | type    | value                                                                                         | description                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | -------------------------- | ------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| relay.mode                 | String  | default value: `managed` possible values: `managed, static, proxy, capture` optional: `false` | Controls how Relay obtains the project configuration for events. For detailed explanation of these modes, see [Relay Modes](/product/relay/modes/). `Environment variable: "RELAY_MODE."`                                                                                                                                                                                                                                                       |
+| relay.mode                 | String  | default value: `managed` possible values: `managed, proxy` optional: `false` | Controls how Relay obtains the project configuration for events. For detailed explanation of these modes, see [Relay Modes](/product/relay/modes/). `Environment variable: "RELAY_MODE."`                                                                                                                                                                                                                                                       |
 | relay.upstream             | String  | default value: `https://sentry.io` optional: `false`                                          | Fully qualified URL of the upstream Relay or Sentry instance. `Environment variable: "RELAY_UPSTREAM_URL".` <Alert level="warning" title="Important"> Relay doesn't check for cycles. Don't set this option to an endpoint that will cause events to be cycled back here. </Alert>                                                                                                                                                              |
 | relay.host                 | String  | default value: `0.0.0.0  in Docker, otherwise  127.0.0.1` optional: `false`                   | The host to which Relay should bind (network interface). `Environment variable: "RELAY_HOST".`                                                                                                                                                                                                                                                                                                                                                  |
 | relay.port                 | Integer | default value: `3000` optional: `false`                                                       | The port to which Relay should bind for the unencrypted Relay HTTP server. `Environment variable: "RELAY_PORT".`                                                                                                                                                                                                                                                                                                                                |

src/middleware.ts

@@ -2437,18 +2437,10 @@ const USER_DOCS_REDIRECTS: Redirect[] = [
     from: '/product/security/relay/',
     to: '/product/relay/',
   },
-  {
-    from: '/meta/relay/projects/',
-    to: '/product/relay/projects/',
-  },
   {
     from: '/meta/relay/getting-started/',
     to: '/product/relay/getting-started/',
   },
-  {
-    from: '/meta/relay/pii-and-data-scrubbing/',
-    to: '/product/relay/pii-and-data-scrubbing/',
-  },
   {
     from: '/meta/relay/options/',
     to: '/product/relay/options/',