docs(plugins): the plugin-dev catalogue entry lists data and ui among the deliberately empty slots

The drift check flagged plugins/packages.mdx for this change, and the #4126
sentence it carries was made stale by it — the never-stubbed list grew.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018UNGqBQcdJ2RYHtWgntJ9B

Author: claude

content/docs/plugins/packages.mdx

@@ -346,7 +346,7 @@ All services implement contracts from `@objectstack/spec/contracts` and are kern
 
 **Local Development Plugin** — one-line local stack: wires ObjectQL, the in-memory driver, auth, security, the HTTP server, REST and the dispatcher, then fills any still-unclaimed core service slot with an in-memory dev implementation.
 
-- **Features**: Composes the real plugins above; registers dev implementations for unclaimed slots, each declaring what kind of fake it is (`__serviceInfo` — `degraded` when it really does the work in memory, `stub` when it fabricates). Slots that would fabricate an answer over HTTP get no implementation at all: `analytics` and the three `security.*` handles stay empty on purpose.
+- **Features**: Composes the real plugins above; registers dev implementations for unclaimed slots, each declaring what kind of fake it is (`__serviceInfo` — `degraded` when it really does the work in memory, `stub` when it fabricates). Slots whose fake could only mislead get no implementation at all: `analytics`, `data`, `ui` and the three `security.*` handles stay empty on purpose — an empty slot is what production has, and every consumer answers it honestly.
 - **When to use**: Local development only. **`init()` throws under `NODE_ENV=production`** — set `OS_ALLOW_DEV_PLUGIN=1` only if you deliberately want the dev slate under a production `NODE_ENV`.
 - **README**: [View README](https://github.com/objectstack-ai/objectstack/blob/main/packages/plugins/plugin-dev/README.md)