Merge pull request #18 from ProvableHQ/josh/zed-client

feat: add Zed editor client

Author: JoshuaBatty

.github/workflows/build-zed-extension.yml

@@ -0,0 +1,38 @@
+name: build-zed-extension
+
+on:
+  pull_request:
+    paths:
+      - "packages/zed/**"
+      - ".github/workflows/build-zed-extension.yml"
+  push:
+    branches: [master]
+    paths:
+      - "packages/zed/**"
+
+jobs:
+  build:
+    # Linux is sufficient: validate.sh builds the wasm and runs the leo-lsp-smoke
+    # LSP-wire assertion. It does NOT drive a headless Zed (Zed compiles +
+    # component-encodes a dev extension itself, with no headless/CLI equivalent;
+    # extension load is verified manually — see packages/zed/Developer.md).
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - name: Install Node deps
+        # Required: validate.sh invokes the workspace-private leo-lsp-smoke /
+        # discover CLIs, which need node_modules (vscode-jsonrpc).
+        run: npm ci
+      - uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: wasm32-wasip2
+      - name: Build extension
+        working-directory: packages/zed
+        run: cargo build --release --target wasm32-wasip2
+      - name: Build leo-lsp from ProvableHQ/leo
+        uses: ./.github/actions/build-leo-lsp
+      - name: Validate
+        run: bash packages/zed/scripts/validate.sh

.github/workflows/watch-leo-tags.yml

@@ -127,15 +127,19 @@ jobs:
           if git diff --quiet -- \
             packages/vscode/generated-from-leo.json \
             packages/shared/syntaxes/leo.tmLanguage.json \
-            packages/shared/syntaxes/prism-leo.js; then
+            packages/shared/syntaxes/prism-leo.js \
+            packages/zed/extension.toml \
+            packages/zed/languages/leo; then
             echo "has_changes=false" >>"$GITHUB_OUTPUT"
             exit 0
           fi
 
           git add \
             packages/vscode/generated-from-leo.json \
             packages/shared/syntaxes/leo.tmLanguage.json \
-            packages/shared/syntaxes/prism-leo.js
+            packages/shared/syntaxes/prism-leo.js \
+            packages/zed/extension.toml \
+            packages/zed/languages/leo
           git commit -m "chore: sync Leo syntax from $TARGET_REF"
           git push --force-with-lease origin "$SYNC_BRANCH"
 
@@ -169,6 +173,7 @@ jobs:
           - regenerated \`packages/shared/syntaxes/leo.tmLanguage.json\`
           - regenerated \`packages/shared/syntaxes/prism-leo.js\`
           - updated \`packages/vscode/generated-from-leo.json\`
+          - re-pinned \`packages/zed/extension.toml\` grammar \`rev\` and synced \`packages/zed/languages/leo/*.scm\`
 
           ## Source
 

.gitignore

@@ -140,3 +140,11 @@ dist
 vite.config.js.timestamp-*
 vite.config.ts.timestamp-*
 packages/vscode/vendor/
+
+# Rust build output (Zed extension, packages/zed)
+target/
+**/target/
+
+# Zed dev-extension build artifacts (written into packages/zed/ on `install dev extension`)
+packages/zed/extension.wasm
+packages/zed/grammars/

README.md

@@ -2,14 +2,34 @@
 
 IDE integrations and language server clients for the Leo programming language.
 
-This workspace is intended to be the long-term home for Leo editor clients and
-adjacent tooling: VS Code today, and eventually other integrations such as Zed,
-Vim, Cursor, Sublime Text, MCP-facing tooling, and shared client infrastructure.
+This workspace is the long-term home for Leo editor clients and adjacent
+tooling. All clients share `leo-lsp` (the Leo language server) and the
+tree-sitter grammar + queries regenerated from upstream `ProvableHQ/leo`.
+
+## Supported clients
+
+| Client | Integration | Package / distribution |
+|--------|-------------|------------------------|
+| **VS Code** | Native extension | `packages/vscode` → VS Code Marketplace (`aleohq.leo-extension`) |
+| **Cursor** | Runs the VS Code extension | `packages/vscode` → Open VSX |
+| **Antigravity** | Runs the VS Code extension | `packages/vscode` → Open VSX |
+| **Zed** | Native extension | `packages/zed` → Zed extensions registry |
+
+Cursor and Antigravity are VS Code–compatible editors: they install the same
+extension from `packages/vscode` (via Open VSX) and each has its own validation
+harness. Zed is a separate, native Rust extension. Further integrations (Sublime
+Text, JetBrains, MCP-facing tooling) are planned.
 
 ## Workspace Layout
 
 - `packages/vscode`: The Leo VS Code extension that will continue publishing to
-  the existing `aleohq.leo-extension` marketplace listing.
+  the existing `aleohq.leo-extension` marketplace listing. Also the extension
+  installed by Cursor and Antigravity (via Open VSX).
+- `packages/zed`: The native Leo extension for the Zed editor (Rust →
+  `wasm32-wasip2`). Registers the `leo` language, pins the tree-sitter grammar
+  to a `ProvableHQ/leo` release commit, and launches `leo-lsp` over stdio. See
+  `packages/zed/README.md` (install/usage) and `packages/zed/Developer.md`
+  (build, validation, release).
 - `packages/shared`: Shared substrate consumed by every Leo editor client and
   by CI workflows. See `packages/shared/README.md` for the per-subdirectory
   index. Contains the canonical TextMate grammar (regenerated from
@@ -26,11 +46,14 @@ Vim, Cursor, Sublime Text, MCP-facing tooling, and shared client infrastructure.
 
 ## Current Focus
 
-The current implementation work is centered on the VS Code extension:
+The VS Code extension (also serving Cursor and Antigravity) and the Zed
+extension are the shipping clients. Cross-cutting work:
 
 - syntax artifacts generated from Leo's tree-sitter source in the main
-  `ProvableHQ/leo` repo for both VS Code and Prism-based website consumers
-- a lean client-side extension scaffold
+  `ProvableHQ/leo` repo, kept in lockstep across consumers (VS Code TextMate,
+  Prism for the website, and the Zed tree-sitter queries) by one sync workflow
+- lean client-side extension scaffolds that defer real language features to
+  `leo-lsp`
 - a clean migration path toward future Rust-based language tooling
 
 ## Where To Look
@@ -39,11 +62,15 @@ The current implementation work is centered on the VS Code extension:
   `packages/vscode/README.md`
 - VS Code developer and release workflow notes:
   `packages/vscode/Developer.md`
+- Zed user-facing extension README:
+  `packages/zed/README.md`
+- Zed developer, build, and release notes:
+  `packages/zed/Developer.md`
 - Repository contribution notes:
   `CONTRIBUTING.md`
 - Shared generated website syntax assets:
   `packages/shared/README.md`
-- VS Code tag-watching sync automation:
+- Leo tag-watching sync automation (TextMate, Prism, and Zed grammar/queries):
   `.github/workflows/watch-leo-tags.yml`
 - Downstream docs Prism sync automation:
   `.github/workflows/sync-prism-to-leo-docs.yml`
@@ -62,6 +89,17 @@ npm run build:vscode
 npm run package:vscode
 ```
 
+For the Zed extension:
+
+```bash
+npm install               # for the shared leo-lsp-smoke / discover CLIs
+npm run build:zed         # cargo build --release --target wasm32-wasip2
+npm run validate:zed      # builds the wasm + leo-lsp-smoke definition assertion
+```
+
+To run it in Zed, use the command palette → **zed: install dev extension** →
+select `packages/zed` (Zed compiles + loads it). See `packages/zed/Developer.md`.
+
 The root workspace README intentionally stays lightweight. Package-specific
 details, sync behavior, and release flow documentation should live with the
 package they belong to.

package.json

@@ -10,6 +10,7 @@
   ],
   "scripts": {
     "build:vscode": "npm run build --workspace leo-extension",
+    "build:zed": "cd packages/zed && cargo build --release --target wasm32-wasip2",
     "check": "npm run typecheck --workspace leo-extension",
     "generate:prism": "node ./scripts/generate-prism-grammar.mjs --leo-repo ../leo --leo-ref HEAD",
     "generate:syntaxes": "node ./scripts/generate-syntax-artifacts.mjs --leo-repo ../leo --leo-ref HEAD",
@@ -23,6 +24,7 @@
     "validate:cursor": "npm run validate:cursor --workspace leo-extension",
     "validate:cursor:teardown": "node ./scripts/cursor/teardown.mjs",
     "validate:antigravity": "npm run validate:antigravity --workspace leo-extension",
+    "validate:zed": "bash packages/zed/scripts/validate.sh",
     "test:prism": "node --test tests/prism-grammar.test.mjs"
   }
 }

packages/shared/identity.md

@@ -23,6 +23,14 @@ the handle is retained for continuity but the **display vendor** is
 `Provable Inc.` in every README, `LICENSE` header, and `description`
 metadata field.
 
+**Documented exception — Zed package (`packages/zed`).** The Zed extension's
+`authors` field, in both `Cargo.toml` and `extension.toml`, uses the upstream
+Leo Rust crate string `The Leo Team <leo@provable.com>` (as in `leo-lsp` /
+`leo-compiler`) rather than the `Provable Inc.` vendor above. This is a
+deliberate choice so the Zed crate + manifest match the upstream `ProvableHQ/leo`
+metadata it is published alongside. The `Provable Inc.` display vendor still
+applies to every other client's README/description/license surfaces.
+
 ## Language
 
 | Field | Value |