chore(webapp): trim sentry tenant attribution server-change to one-liner

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: d-cs

.server-changes/sentry-tenant-attribution.md

@@ -3,13 +3,4 @@ area: webapp
 type: feature
 ---
 
-Attach organization / project / environment to every Sentry event so "Users Impacted" counts orgs and events are filterable by tenant.
-
-Mechanism: `AsyncLocalStorage`-backed `tenantContext` + a Sentry `addEventProcessor` that stamps `user.id = orgId`, `user.username = orgSlug`, and tags (`org_id`, `org_slug`, `project_id`, `project_ref`, `environment_id`, `env_slug`, `env_type`, `impersonating`).
-
-Wired at the HTTP entry points:
-
-- API routes — `apiBuilder.server.ts` wraps each handler invocation in `tenantContext.run` using the authenticated `environment`.
-- Dashboard requests — an Express middleware (`tenantContextMiddleware`) resolves org/project/env from the URL pattern `/orgs/:org/projects/:project/env/:env/...` and wraps the Remix handler.
-
-Background workers (redis-worker / schedule-engine) and socket handlers are not yet wired and remain a follow-up. Events from those entry points will continue to ship without tenant attribution until each handler is updated.
+Attach org / project / environment context to Sentry events so "Users Impacted" counts tenants and events are filterable by org.