docs(studio-bridge): trim programmatic API and protocol sections from README

Author: Quenty

tools/studio-bridge/README.md

@@ -207,156 +207,6 @@ Commands that target a session accept `--target` and `--context`:
 
 When Studio is in Play mode, a single instance has multiple contexts (Edit + Client + Server). The default is `edit`.
 
-## Programmatic API
-
-### Persistent sessions
-
-```typescript
-import { BridgeConnection } from '@quenty/studio-bridge';
-
-const connection = await BridgeConnection.connectAsync();
-const session = await connection.resolveSessionAsync();
-
-const result = await session.execAsync('return game.PlaceId');
-console.log(result.success, result.returnValue);
-
-const state = await session.queryStateAsync();
-console.log(state.mode, state.placeName);
-
-const screenshot = await session.captureScreenshotAsync();
-// screenshot.base64, screenshot.width, screenshot.height
-
-const logs = await session.queryLogsAsync({ tail: 50 });
-// logs.entries: { level, body, timestamp }[]
-
-const tree = await session.queryDataModelAsync({ path: 'Workspace' });
-// tree.name, tree.className, tree.children
-
-await connection.disconnectAsync();
-```
-
-#### `BridgeConnectionOptions`
-
-| Field | Type | Default | Description |
-|-------|------|---------|-------------|
-| `port` | `number` | `38741` | Port to bind/connect |
-| `timeoutMs` | `number` | `30000` | Connection setup timeout |
-| `keepAlive` | `boolean` | `false` | Prevent idle host shutdown |
-| `remoteHost` | `string` | — | Force client mode (`host:port`) |
-| `local` | `boolean` | `false` | Skip devcontainer auto-detection |
-
-#### `BridgeSession` methods
-
-| Method | Timeout | Description |
-|--------|---------|-------------|
-| `execAsync(code, timeout?)` | 120s | Execute Luau code |
-| `queryStateAsync()` | 5s | Get Studio mode, place name, IDs |
-| `captureScreenshotAsync()` | 15s | Capture viewport PNG |
-| `queryLogsAsync(options?)` | 10s | Retrieve buffered log entries |
-| `queryDataModelAsync(options)` | 10s | Query instance tree |
-| `subscribeAsync(events)` | 5s | Subscribe to push events |
-| `unsubscribeAsync(events)` | 5s | Unsubscribe from events |
-
-### One-shot execution (legacy)
-
-```typescript
-import { StudioBridge } from '@quenty/studio-bridge';
-
-const bridge = new StudioBridge({ placePath: './build/test.rbxl' });
-await bridge.startAsync();
-
-const result = await bridge.executeAsync({
-  scriptContent: 'print("Hello from studio-bridge!")',
-  timeoutMs: 90_000,
-  onOutput: (level, body) => console.log(`[${level}] ${body}`),
-});
-
-console.log(result.success); // boolean
-console.log(result.logs);    // all captured output, newline-separated
-
-await bridge.stopAsync();
-```
-
-The legacy API launches Studio, injects a temporary plugin, executes a script, and tears everything down. Use `BridgeConnection` instead for persistent workflows.
-
-## WebSocket Protocol
-
-All messages are JSON: `{ type, sessionId, payload }`. The plugin sends `register` on connect with its capabilities; the server dispatches actions and the plugin replies via `requestId` correlation.
-
-**Plugin to Server:**
-
-| Type | Payload | Description |
-|------|---------|-------------|
-| `register` | `{ sessionId, capabilities, pluginVersion, … }` | Handshake with capabilities |
-| `scriptComplete` | `{ requestId, success, error?, output? }` | Response to `execute` |
-| `stateResult` | `{ requestId, mode, placeName, placeId, gameId }` | Response to `queryState` |
-| `screenshotResult` | `{ requestId, base64, width, height }` | Response to `captureScreenshot` |
-| `dataModelResult` | `{ requestId, instances }` | Response to `queryDataModel` |
-| `logsResult` | `{ requestId, entries }` | Response to `queryLogs` |
-| `stateChange` | `{ state, previousState }` | Push event on state transition |
-| `heartbeat` | `{ uptimeMs, state, pendingRequests }` | Periodic keep-alive |
-| `registerActionResult` | `{ requestId, name, success, error? }` | Dynamic action registration result |
-| `error` | `{ requestId, code, message }` | Error response |
-
-**Server to Plugin:**
-
-| Type | Payload | Description |
-|------|---------|-------------|
-| `execute` | `{ requestId, script }` | Luau script to run |
-| `queryState` | `{ requestId }` | Request current state |
-| `captureScreenshot` | `{ requestId }` | Request viewport screenshot |
-| `queryDataModel` | `{ requestId, path, depth?, properties?, attributes? }` | Request instance tree |
-| `queryLogs` | `{ requestId, tail?, head?, levels? }` | Request buffered logs |
-| `registerAction` | `{ requestId, name, source, responseType? }` | Push a Luau action module dynamically |
-| `shutdown` | `{}` | Graceful disconnect |
-
-### Capabilities
-
-Negotiated during handshake: `execute`, `queryState`, `captureScreenshot`, `queryDataModel`, `queryLogs`, `subscribe`, `heartbeat`, `registerAction`.
-
-### Output Levels
-
-`"Print"`, `"Info"`, `"Warning"`, `"Error"` — matches `Enum.MessageType`.
-
-### Error Codes
-
-`UNKNOWN_REQUEST`, `INVALID_PAYLOAD`, `TIMEOUT`, `CAPABILITY_NOT_SUPPORTED`, `INSTANCE_NOT_FOUND`, `PROPERTY_NOT_FOUND`, `SCREENSHOT_FAILED`, `SCRIPT_LOAD_ERROR`, `SCRIPT_RUNTIME_ERROR`, `BUSY`, `SESSION_MISMATCH`, `INTERNAL_ERROR`
-
-## Dynamic Action Registration
-
-The bridge plugin ships as a thin runtime — no static Luau action modules. Instead, action code is pushed dynamically over the wire when a plugin connects:
-
-1. Plugin connects and sends `register` with `registerAction` capability
-2. Bridge host scans co-located `.luau` files from `src/commands/<group>/<name>/`
-3. Each action's source is sent via `registerAction` message
-4. Plugin calls `loadstring()` to install the handler at runtime
-
-This means:
-- Adding a new command requires only a `.ts` + `.luau` file in the command directory
-- No plugin reinstallation needed when actions change
-- Hot-reload during development: reconnect pushes updated action code
-
-## Plugin Discovery
-
-The persistent plugin discovers the bridge host automatically:
-
-1. Poll `GET http://localhost:38741/health` (default port)
-2. Health endpoint returns `{ status, port, sessions, uptime }`
-3. Connect to `ws://localhost:{port}/plugin`
-4. Send `register` message with capabilities
-6. Receive `registerAction` messages for each command's Luau action
-
-If the health endpoint is unreachable, the plugin retries with backoff. The plugin survives Studio restarts and reconnects automatically when a host becomes available.
-
-### Role Detection
-
-When a CLI command runs, `BridgeConnection` automatically detects whether to be host or client:
-
-1. If `--remote` specified — connect as client
-2. If inside a devcontainer — attempt remote connection first (3s timeout)
-3. Try to bind the port — success means become host
-4. Port in use — check `/health` — if healthy, become client; if stale, retry
-
 ## Testing
 
 ```bash