docs(event-client): clarify unset NODE_ENV behavior and fix stale stripping guidance

Author: AlemTuzlak

packages/event-bus-client/README.md

@@ -61,3 +61,5 @@ import { EventClient } from '@tanstack/devtools-event-client/production'
 
 The public API is identical between the two imports — only the production
 runtime behavior differs.
+
+"Outside development" includes when `NODE_ENV` is unset — common in plain Node scripts, some SSR dev servers, and test runners — so the root import resolves to the no-op there too. Set `NODE_ENV=development`, or use the `/production` subpath, to get the real client in those contexts.

packages/event-bus-client/skills/devtools-event-client/SKILL.md

@@ -264,6 +264,8 @@ when `process.env.NODE_ENV !== 'development'`, and the real client is
 tree-shaken out of production bundles. This is the default and what you want for
 most libraries — your `emit()` calls cost nothing in production.
 
+"Outside development" includes when `NODE_ENV` is unset — common in plain Node scripts, some SSR dev servers, and test runners — so the root import resolves to the no-op there too. Set `NODE_ENV=development`, or use the `/production` subpath, to get the real client in those contexts.
+
 ```ts
 // dev: real client — production: no-op, removed from the bundle
 import { EventClient } from '@tanstack/devtools-event-client'

packages/event-bus-client/skills/devtools-instrumentation/SKILL.md

@@ -277,7 +277,7 @@ if (process.env.NODE_ENV !== 'production') {
 }
 ```
 
-**Important:** The Vite plugin strips `@tanstack/react-devtools` from production but does NOT strip `@tanstack/devtools-event-client`. You must guard yourself.
+**Important:** The Vite plugin strips `@tanstack/react-devtools` from production. The root import of `@tanstack/devtools-event-client` also no-ops and is tree-shaken out when `process.env.NODE_ENV !== 'development'`, so `emit()` calls cost nothing in production by default. Import from `@tanstack/devtools-event-client/production` if you deliberately want events in production. The `enabled` option remains available for runtime control.
 
 ### 6. Server/Client Transparent Bridging