ref(api): defer incident mutation scope tightening

Remove the incident permission change from the existing-write-scope pass. Incident mutation has an older member-access contract tied to project access, so tightening it cleanly needs a dedicated scope decision instead of being folded into the uncontroversial cleanup.

Also drop an unrelated CODEOWNERS hunk so this branch stays focused on backend mutation scope changes.

Co-Authored-By: OpenAI Codex <noreply@openai.com>

Author: dcramer

.github/CODEOWNERS

@@ -437,7 +437,6 @@ tests/sentry/api/endpoints/test_organization_attribute_mappings.py          @get
 /static/app/components/analyticsArea.spec.tsx  @getsentry/app-frontend
 /static/app/components/analyticsArea.tsx       @getsentry/app-frontend
 /static/app/components/loading/                @getsentry/app-frontend
-/static/app/components/markdownTextArea.tsx    @getsentry/app-frontend
 /static/app/components/events/interfaces/      @getsentry/app-frontend
 /static/app/components/forms/                  @getsentry/app-frontend
 /static/app/locale.tsx                         @getsentry/app-frontend

src/sentry/api/bases/incident.py

@@ -20,9 +20,9 @@ class IncidentPermission(OrganizationPermission):
             "project:write",
             "project:admin",
         ],
-        "POST": ["org:write", "org:admin", "project:write", "project:admin"],
-        "PUT": ["org:write", "org:admin", "project:write", "project:admin"],
-        "DELETE": ["org:write", "org:admin", "project:write", "project:admin"],
+        "POST": ["org:write", "org:admin", "project:read", "project:write", "project:admin"],
+        "PUT": ["org:write", "org:admin", "project:read", "project:write", "project:admin"],
+        "DELETE": ["org:write", "org:admin", "project:read", "project:write", "project:admin"],
     }