Merge master into sentry-prevent-test-analytics-docs

- Resolved conflicts for directory rename from sentry-prevent-ai to ai-code-review
- Added new image prevent-ai-response.png from master
- Kept renamed sentry-prevent-review.png in new location
- Resolved redirects.js conflicts by keeping both our redirect and master's .NET profiling redirects
- Updated all content to use 'Sentry's AI Code Review' branding
- Incorporated all master updates including error prediction features, enhanced setup instructions, and expanded FAQ

Author: Shannon Anahata

app/[[...path]]/page.tsx

@@ -47,7 +47,12 @@ export const dynamic = 'force-static';
 const mdxComponentsWithWrapper = mdxComponents(
   {Include, PlatformContent},
   ({children, frontMatter, nextPage, previousPage}) => (
-    <DocPage frontMatter={frontMatter} nextPage={nextPage} previousPage={previousPage}>
+    <DocPage
+      frontMatter={frontMatter}
+      nextPage={nextPage}
+      previousPage={previousPage}
+      fullWidth={frontMatter.fullWidth}
+    >
       {children}
     </DocPage>
   )

app/globals.css

@@ -177,6 +177,6 @@ body {
 
 .onboarding-step .step-heading::before,
 .onboarding-step h2::before {
-  content: "Step " counter(onboarding-step) ": ";
+  content: 'Step ' counter(onboarding-step) ': ';
   font-weight: inherit;
 }

develop-docs/backend/application-domains/asynchronous-workers.mdx

@@ -3,6 +3,11 @@ title: Asynchronous Workers
 sidebar_order: 70
 ---
 
+<Alert level="warning" title="Deprecated">
+Celery workers are deprecated, and will be removed as of the 25.10.x self-hosted
+release.
+</Alert>
+
 Sentry comes with a built-in queue to process tasks in a more asynchronous fashion. For example when an event comes in instead of writing it to the database immediately, it sends a job to the queue so that the request can be returned right away, and the background workers handle actually saving that data.
 
 Sentry relies on the [Celery](https://docs.celeryproject.org/) library for managing workers.
@@ -75,7 +80,7 @@ There are a few important points:
   because this is what registers the task by name.  Thus every module
   containing a task must be added to the `CELERY_IMPORTS` and `TASKWORKER_IMPORTS` settings in
   `src/sentry/conf/server.py`.
-  
+
   We have a separate setting for the Taskbroker workers until we fully deprecate the Celery workers.
 
 ## Running a Worker

develop-docs/backend/application-domains/options.mdx

@@ -5,9 +5,15 @@ sidebar_order: 10
 
 Options are a way to store generic system-wide configuration. They serve a similar purpose to configuration files, but they are backed by a database, so it's possible to change them at runtime without a deploy. Options are stored in the database and cached, so they are performant and reliable. This makes options well-suited for rates, quotas, and limits.
 
+While the process for creating and using options in the codebase is universal, the method for *managing their values* differs between Sentry's internal SaaS platform and self-hosted instances.
+
+> **For Sentry Employees**
+>
+> Option management for Sentry's internal SaaS environments is handled via a GitOps workflow. All changes to option values are proposed, reviewed, and deployed through pull requests. For complete details on changing values, handling drift, and deployment, please see the **[sentry-options-automator](https://github.com/getsentry/sentry-options-automator)** repository.
+
 ## Adding New Options
 
-To add a new system option, add it to [`sentry/options/defaults.py`](https://github.com/getsentry/sentry/blob/master/src/sentry/options/defaults.py) by registering it. e.g.,
+The process for registering a new option is the same for all environments and is done in the Sentry codebase. Add your option to [`sentry/options/defaults.py`](https://github.com/getsentry/sentry/blob/master/sentry/options/defaults.py).
 
 ```python
 register("performance.some-feature-rate", default=0.0)
@@ -23,24 +29,23 @@ Follow these rules when adding new options:
 The value of an option can be any pickleable value.
 
 <Alert>
-  It is safe to declare and use an option in the same pull request, you don't need to
-  split them up.
+  It is safe to declare and use an option in the same pull request; you don't need to split them up.
 </Alert>
 
 ## Using Options
+To check the value of an option, import the options module and use the get method. This is universal across all environments.
 
-To check the value of an option, import the `options` module and use the `get` method. e.g.,
 
 ```python
 from sentry import options
 feature_rate = options.get("performance.some-feature-rate")
 ```
 
 ## Setting Options
-
-You can change the value of an option using `sentry shell`, or by using the [options UI](#options-ui).
+For self-hosted instances, you can change the value of an option using `sentry shell`, or by using the [options UI](#options-ui).
 
 ### Sentry Shell
+For direct database manipulation, you can set option values using sentry shell.
 
 You can set option values using `sentry shell`. e.g.,
 
@@ -110,7 +115,9 @@ def test_some_feature(self):
 
 ## Removing Options
 
-If your option is short-lived, you should remove it once it's no longer needed. First, create a pull request to remove the option and its usage. Once it's merged and deployed, remove the option from the database. To do this, you can use the Sentry shell. e.g.,
+If your option is short-lived, you should remove it once it's no longer needed. First, create a pull request to remove the option and its usage. Once it's merged and deployed, remove the option from the database. For self-hosted instances, this is done via the Sentry shell. Otherwise, remove it from the Options Automator repository.
+
+For self hosted instances, you can use the Sentry shell. e.g.,
 
 ```bash
 sentry shell
@@ -122,8 +129,3 @@ then,
 from sentry import options
 options.delete("performance.some-feature-rate")
 ```
-
-<Alert>
-  If you do not have access to the shell, you'll need to contact OPS to remove the option
-  for you.
-</Alert>

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