fix(local): correct misleading docs in run subcommand

Remove the false claim that `sentry local run` auto-starts a server.
The run subcommand is an env-var wrapper — users start the server
separately via `sentry local serve`. Also adds `local` to the
completions property test.

Author: MathurAditya724

docs/src/fragments/commands/local.md

@@ -1,16 +1,16 @@
 
 
-[Spotlight](https://spotlightjs.com) is "Sentry for Development" — a lightweight local proxy that ingests Sentry envelopes from SDKs running in your dev stack and surfaces them in real time. `sentry local` runs a minimal [Hono](https://hono.dev/) HTTP server that's wire-compatible with Spotlight's protocol, so your existing SDKs and the [Spotlight overlay](https://spotlightjs.com/about/) work without any changes.
+`sentry local` runs a local development server that captures Sentry SDK envelopes from your dev stack and surfaces errors, traces, and logs in real time — right in your terminal. No authentication required.
 
-No authentication is required — the server binds to `localhost` by default and is purely a development tool.
+If a server is already running on the port, the command attaches as an SSE consumer instead of starting a duplicate.
 
 ## Examples
 
 ```bash
 # Start the server and tail events (default)
 sentry local
 
-# Run your app with Spotlight auto-enabled
+# Run your app with the local server auto-enabled
 sentry local run -- npm run dev
 sentry local run -- python manage.py runserver
 
@@ -40,7 +40,7 @@ Env vars injected into the child process:
 
 | Method | Path                            | Description                                        |
 |--------|---------------------------------|----------------------------------------------------|
-| `POST` | `/stream`                       | Spotlight-compatible envelope ingest               |
+| `POST` | `/stream`                       | Envelope ingest                                    |
 | `POST` | `/api/{projectId}/envelope/`    | Sentry SDK ingest path                             |
 | `GET`  | `/stream`                       | Server-Sent Events feed of incoming envelopes      |
 | `GET`  | `/health`                       | Liveness check (returns `OK`)                      |
@@ -63,4 +63,4 @@ Use `--filter` / `-f` to narrow the output to specific event types (repeatable):
 sentry local -f error -f log    # only errors and logs
 ```
 
-Use `--quiet` to suppress tail output entirely if you only need the SSE stream for the Spotlight overlay.
+Use `--quiet` to suppress tail output entirely if you only need the SSE stream.

plugins/sentry-cli/skills/sentry-cli/SKILL.md

@@ -470,10 +470,10 @@ Initialize Sentry in your project (experimental)
 
 ### Local
 
-Run a local Spotlight server for development
+Sentry for local development
 
 - `sentry local serve` — Run a local Spotlight server to capture dev SDK events
-- `sentry local run <command...>` — Run a command with Spotlight enabled
+- `sentry local run <command...>` — Run a command with the local dev server enabled
 
 → Full flags and examples: `references/local.md`
 

plugins/sentry-cli/skills/sentry-cli/references/local.md

@@ -1,15 +1,15 @@
 ---
 name: sentry-cli-local
 version: 0.35.0-dev.0
-description: Run a local Spotlight server for development
+description: Sentry for local development
 requires:
   bins: ["sentry"]
   auth: true
 ---
 
 # Local Commands
 
-Run a local Spotlight server for development
+Sentry for local development
 
 ### `sentry local serve`
 
@@ -23,19 +23,19 @@ Run a local Spotlight server to capture dev SDK events
 
 ### `sentry local run <command...>`
 
-Run a command with Spotlight enabled
+Run a command with the local dev server enabled
 
 **Flags:**
-- `-p, --port <value> - Port for the Spotlight server (default 8969) - (default: "8969")`
-- `--host <value> - Hostname for the Spotlight server (default localhost) - (default: "localhost")`
+- `-p, --port <value> - Port for the local server (default 8969) - (default: "8969")`
+- `--host <value> - Hostname for the local server (default localhost) - (default: "localhost")`
 
 **Examples:**
 
 ```bash
 # Start the server and tail events (default)
 sentry local
 
-# Run your app with Spotlight auto-enabled
+# Run your app with the local server auto-enabled
 sentry local run -- npm run dev
 sentry local run -- python manage.py runserver
 

src/commands/local/index.ts

@@ -9,10 +9,10 @@ export const localRoute = buildRouteMap({
   },
   defaultCommand: "serve",
   docs: {
-    brief: "Run a local Spotlight server for development",
+    brief: "Sentry for local development",
     fullDescription:
-      "Run a local Spotlight-compatible server to capture Sentry SDK\n" +
-      "events from your dev stack.\n\n" +
+      "Run a local development server to capture Sentry SDK events\n" +
+      "from your dev stack.\n\n" +
       "Commands:\n" +
       "  serve      Start the server and tail events (default)\n" +
       "  run        Run a command with SENTRY_SPOTLIGHT auto-injected",

src/commands/local/run.ts

@@ -1,10 +1,9 @@
 /**
  * sentry local run
  *
- * Run a command with Sentry Spotlight enabled. Starts the local Spotlight
- * server (or connects to an existing one), injects `SENTRY_SPOTLIGHT` into
- * the child process environment so the Sentry SDK auto-sends envelopes to
- * the local server, then tails events to the terminal.
+ * Run a command with the local dev server enabled. Injects
+ * `SENTRY_SPOTLIGHT` into the child process environment so the Sentry SDK
+ * auto-sends envelopes to the local server.
  */
 
 import type { SentryContext } from "../../context.js";
@@ -33,14 +32,13 @@ function parsePort(value: string): number {
 
 export const runCommand = buildCommand({
   docs: {
-    brief: "Run a command with Spotlight enabled",
+    brief: "Run a command with the local dev server enabled",
     fullDescription:
       "Run a command with the SENTRY_SPOTLIGHT environment variable\n" +
       "injected so the Sentry SDK automatically sends envelopes to the\n" +
-      "local Spotlight server.\n\n" +
-      "If no server is running on the port, one is started automatically\n" +
-      "in the background. The child process inherits all current env vars\n" +
-      "plus SENTRY_SPOTLIGHT and SENTRY_TRACES_SAMPLE_RATE=1.\n\n" +
+      "local server.\n\n" +
+      "The child process inherits all current env vars plus\n" +
+      "SENTRY_SPOTLIGHT and SENTRY_TRACES_SAMPLE_RATE=1.\n\n" +
       "Example:\n" +
       "  sentry local run -- npm run dev\n" +
       "  sentry local run -- python manage.py runserver",
@@ -58,13 +56,13 @@ export const runCommand = buildCommand({
       port: {
         kind: "parsed",
         parse: parsePort,
-        brief: `Port for the Spotlight server (default ${DEFAULT_PORT})`,
+        brief: `Port for the local server (default ${DEFAULT_PORT})`,
         default: String(DEFAULT_PORT),
       },
       host: {
         kind: "parsed",
         parse: String,
-        brief: "Hostname for the Spotlight server (default localhost)",
+        brief: "Hostname for the local server (default localhost)",
         default: "localhost",
       },
     },

src/commands/local/server.ts

@@ -705,7 +705,7 @@ function feedSSELine(
 }
 
 /**
- * Consume SSE events from an upstream Spotlight server and print them.
+ * Consume SSE events from an upstream server and print them.
  *
  * Bun doesn't have a global `EventSource`, so we use `fetch` with a
  * streaming body and parse the SSE wire format manually.

test/lib/completions.property.test.ts

@@ -192,6 +192,7 @@ describe("proposeCompletions: Stricli integration", () => {
     "trace",
     "span",
     "log",
+    "local",
   ]);
 
   test("subcommands match extractCommandTree for each group without defaultCommand", async () => {