@lineman-io/mcp 2.3.0 → 2.4.2

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lineman",
-  "version": "2.0.0",
+  "version": "2.4.2",
   "description": "AI-powered code assistant that uses a secondary LLM to handle data-heavy tasks — saves context window tokens on large-file reads, error classification, and build-output triage.",
   "author": {
     "name": "Lineman",

package/README.md

@@ -50,19 +50,42 @@ User config lives at `~/.goodex/lineman.json`:
 
 ```json
 {
-  "serverUrl": "https://api.lineman.sh",
-  "apiToken": "<set by npx lineman-mcp auth>",
+  "dataApiUrl": "https://api-data.lineman.io",
+  "dataStreamApiUrl": "https://api-data-stream.lineman.io",
+  "controlApiUrl": "https://api-app.lineman.io",
+  "apiToken": "<set by /lineman:auth>",
   "userId": "<set after auth>",
   "tier": "free"
 }
 ```
 
-Environment variables take precedence:
+The three URLs map to the three customer-facing Cloud Run services in
+the Lineman API split (see [ADR-0001](../../../docs/adr/0001-api-split.md)):
 
-| Variable | Overrides |
-|----------|-----------|
-| `LINEMAN_SERVER_URL` | `serverUrl` |
-| `LINEMAN_API_TOKEN` | `apiToken` |
+- `dataApiUrl` — sync inference (`/lineman/execute`, `/shape`, `/metrics`, `/hook-config`)
+- `dataStreamApiUrl` — streamed inference (`/lineman/execute/stream`, SSE)
+- `controlApiUrl` — auth (`/auth/device/*`, `/auth/verify`), usage, dashboard
+
+The MCP picks between the data URLs per request based on whether the
+task type is in `STREAMING_TASK_TYPES` (currently `triage_build_output`).
+The legacy `serverUrl` field is still read for backwards compatibility
+on machines that authed pre-split — new writes always populate the
+explicit per-plane fields.
+
+Environment variables take precedence over the on-disk config:
+
+| Variable | Overrides | Purpose |
+|----------|-----------|---------|
+| `LINEMAN_DATA_API_URL` | `dataApiUrl` | Sync inference Cloud Run service |
+| `LINEMAN_DATA_STREAM_API_URL` | `dataStreamApiUrl` | Streaming inference Cloud Run service |
+| `LINEMAN_CONTROL_API_URL` | `controlApiUrl` | Auth + usage + dashboard Cloud Run service |
+| `LINEMAN_API_TOKEN` | `apiToken` | Override the saved token (CI / staging) |
+
+All three URL env vars are required to resolve. Missing any of them at
+boot results in a fatal startup error naming the missing var. There is
+**no** `LINEMAN_API_URL` fallback — the per-plane convention is locked
+in ADR-0001 and silently collapsing to a single URL re-introduces the
+fault lines the split exists to fix.
 
 ### Auth at use time
 
@@ -90,13 +113,22 @@ What we strip before send:
 
 ### Disabling telemetry
 
-Set `LINEMAN_TELEMETRY=off` (or `0` / `false` / `no`) in your shell environment. The MCP will skip Sentry initialisation entirely — no SDK loaded, no events emitted, no install_id sent.
+Two ways, in resolution order:
 
-```sh
-export LINEMAN_TELEMETRY=off
-```
+1. **`/lineman:telemetry off` from inside Claude Code** (recommended). Runs the `telemetry` skill, persists your preference to `~/.goodex/lineman.json::telemetryEnabled`. Restart your Claude Code session for the next MCP boot to pick it up. To re-enable, run `/lineman:telemetry on`.
+
+2. **`LINEMAN_TELEMETRY` env var** (overrides the per-install setting). Useful for shared / regulated environments where the choice should be enforced by config-management rather than per-user.
+
+   ```sh
+   export LINEMAN_TELEMETRY=off
+   ```
+
+   Accepted values:
+   - `0`, `off`, `false`, `no` → telemetry disabled.
+   - `1`, `on`, `true`, `yes` → telemetry enabled (overrides the file setting too).
+   - Anything else / unset → fall through to the file setting / default.
 
-A first-class plugin setting + slash command for this is tracked in LIN-524.
+In both cases the MCP skips `Sentry.init` entirely when disabled — no SDK loaded, no events emitted, no `install_id` sent. There's no silent degraded mode.
 
 ## Troubleshooting