refactor(zed): port setup CLI to Node, drop the Python dependency (#2599)

* refactor(zed): port setup CLI to Node, drop the Python dependency

The Zed integration is configuration-only — it writes the `context_servers`
entry into Zed's settings.json and a recall/retain rule into AGENTS.md — and the
MCP server it configures runs via `npx mcp-remote`, so Node.js was already a hard
requirement. Requiring Python *as well* just to write two config files meant
users needed two runtimes.

Port the `hindsight-zed` CLI to a zero-dependency Node CLI so the integration
needs only Node:

- Node CLI under `src/` + `bin/hindsight-zed.js`, shipped via `package.json`
  (matches the existing TypeScript integrations; release-integration.yml already
  detects package.json for npm publishing).
- Behavior-preserving: same commands (`init`/`status`/`uninstall`), flags,
  `--print-only`, env/file/flag config resolution, JSONC-safe settings edits,
  and fenced AGENTS.md rule block.
- Tests ported to Node's built-in runner (`node --test`) — 21 tests.
- CI (`test.yml`) updated to run `npm test` on Node 22 instead of pytest.
- Removes the Python package (`hindsight_zed/`, `pyproject.toml`, `uv.lock`,
  Python `tests/`).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(zed): make the Node package publishable by the release workflow

The release workflow classifies any integration with a package.json as
`type=typescript` and unconditionally runs `npm ci` + `npm run build` in
the integration dir. This zero-dependency, no-build JS package had neither,
so `integrations/zed/v*` would fail at release time (invisible in test CI,
which only runs `npm test`):

- add a no-op `build` script so `npm run build` succeeds
- commit package-lock.json so `npm ci` succeeds (it refuses to run without
  one, even with zero deps); lockfile has no node_modules entries, so
  check-integration-lockfiles.sh passes trivially
- drop the stray settings.json (a local `init` scaffold accidentally
  committed) and gitignore it

Verified locally: node --test (21/21), npm ci, npm run build, and
npm publish --dry-run all pass; tarball ships only bin/src/README.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WEHyNxWfn1miSWRW6NUtEW

* docs(zed): update setup to Node/npx (drop pip install)

* refactor(zed): scope npm package as @vectorize-io/hindsight-zed

Match the scoped-name convention of the other TS integrations
(@vectorize-io/hindsight-ai-sdk, -chat, -openclaw). CLI/bin command stays
'hindsight-zed'; npx/global-install references updated to the scoped name.

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: DK09876 <dk09876@Dikshants-MacBook-Pro.local>

Author: 3 people

.github/workflows/test.yml

@@ -520,22 +520,17 @@ jobs:
       with:
         ref: ${{ github.event.pull_request.head.sha || '' }}
 
-    - name: Set up Python
-      uses: actions/setup-python@v6
+    - name: Set up Node.js
+      uses: actions/setup-node@v6
       with:
-        python-version: '3.11'
-
-    - name: Install package and pytest
-      working-directory: ./hindsight-integrations/zed
-      # Installs the package (incl. the zstandard runtime dep) so the threads.db
-      # reader tests can decompress Zed's zstd blobs.
-      run: pip install -e . pytest
+        node-version: '22'
 
     - name: Run tests
       working-directory: ./hindsight-integrations/zed
-      # PR CI runs only the deterministic bucket; the real-LLM E2E bucket
-      # (requires_real_llm) needs a live Hindsight server and runs separately.
-      run: python -m pytest tests/ -v -m "not requires_real_llm"
+      # Config-only integration with no dependencies — it uses Node's built-in
+      # test runner. The runtime MCP bridge is `npx mcp-remote` (Node), so this
+      # integration requires only Node.js (no Python).
+      run: npm test
 
   test-omo-integration:
     needs: [detect-changes]

hindsight-docs/docs-integrations/zed.md

@@ -19,8 +19,16 @@ Zed doesn't yet have native HTTP-MCP transport, so the server is connected throu
 
 ## Setup
 
+`hindsight-zed` is a zero-dependency Node CLI — Node.js is the only requirement (already needed for the `mcp-remote` bridge). Run it straight from npm with `npx`:
+
+```bash
+npx @vectorize-io/hindsight-zed init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-memory
+```
+
+Or install it globally for a persistent command:
+
 ```bash
-pip install hindsight-zed
+npm install -g @vectorize-io/hindsight-zed
 hindsight-zed init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-memory
 ```
 

hindsight-integrations/zed/.gitignore

@@ -1,3 +1,6 @@
-.venv/
-__pycache__/
-*.pyc
+node_modules/
+*.log
+.DS_Store
+
+# Local scaffold written by `hindsight-zed init` when pointed at this dir
+/settings.json

hindsight-integrations/zed/README.md

@@ -22,12 +22,21 @@ Zed has no pre-prompt hook, but it does support two things this integration uses
 
 Zed doesn't yet have native HTTP-MCP transport, so the server is connected
 through the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) stdio bridge
-(run via `npx`) — that means you need Node.js installed.
+(run via `npx`). Because that bridge already runs on Node.js, this setup tool is
+a Node CLI too — so **Node.js is the only requirement**.
 
 ## Install
 
+No global install needed — run it straight from npm with `npx`:
+
 ```bash
-pip install hindsight-zed
+npx @vectorize-io/hindsight-zed init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-memory
+```
+
+Or install it for a persistent command:
+
+```bash
+npm install -g @vectorize-io/hindsight-zed
 hindsight-zed init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-memory
 ```
 
@@ -45,12 +54,14 @@ open local server).
 
 ## Commands
 
-| Command | Description |
-| --- | --- |
-| `hindsight-zed init` | Add the MCP server + recall/retain rule |
-| `hindsight-zed status` | Show whether the server + rule are configured |
-| `hindsight-zed uninstall` | Remove the server + rule |
-| `hindsight-zed init --print-only` | Print the config to add manually |
+| Command                           | Description                                   |
+| --------------------------------- | --------------------------------------------- |
+| `hindsight-zed init`              | Add the MCP server + recall/retain rule       |
+| `hindsight-zed status`            | Show whether the server + rule are configured |
+| `hindsight-zed uninstall`         | Remove the server + rule                      |
+| `hindsight-zed init --print-only` | Print the config to add manually              |
+
+(Prefix any of these with `npx ` if you didn't install globally.)
 
 ## What gets written
 
@@ -63,12 +74,14 @@ open local server).
       "source": "custom",
       "command": "npx",
       "args": [
-        "-y", "mcp-remote",
+        "-y",
+        "mcp-remote",
         "https://api.hindsight.vectorize.io/mcp/my-memory/",
-        "--header", "Authorization: Bearer YOUR_HINDSIGHT_API_KEY"
-      ]
-    }
-  }
+        "--header",
+        "Authorization: Bearer YOUR_HINDSIGHT_API_KEY",
+      ],
+    },
+  },
 }
 ```
 
@@ -78,20 +91,20 @@ the start of each task and `retain` durable facts.
 
 ## Configuration
 
-| Setting | Env var | Default |
-| --- | --- | --- |
-| API URL | `HINDSIGHT_API_URL` | `https://api.hindsight.vectorize.io` |
-| API token | `HINDSIGHT_API_TOKEN` | _(none; required for Cloud)_ |
-| Bank id | `HINDSIGHT_ZED_BANK_ID` | `zed` |
+| Setting   | Env var                 | Default                              |
+| --------- | ----------------------- | ------------------------------------ |
+| API URL   | `HINDSIGHT_API_URL`     | `https://api.hindsight.vectorize.io` |
+| API token | `HINDSIGHT_API_TOKEN`   | _(none; required for Cloud)_         |
+| Bank id   | `HINDSIGHT_ZED_BANK_ID` | `zed`                                |
 
 These can also live in `~/.hindsight/zed.json` (written by `init`).
 
 ## Development
 
+Requires Node.js ≥ 18.3. There are no dependencies to install.
+
 ```bash
-uv sync
-uv run pytest tests -v -m 'not requires_real_llm'   # deterministic suite
-uv run pytest tests -v -m requires_real_llm          # gated MCP-endpoint check
+node --test        # run the test suite
 ```
 
 ## License

hindsight-integrations/zed/bin/hindsight-zed.js

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+import { main } from "../src/cli.js";
+
+process.exit(main());