chore(editors): drop VSCode publish CI + extract Zed extension

Replace .github/workflows/vscode.yml (multi-platform package + publish
matrix) with `make vscode-vsix` and `make vscode-vsix-target` targets
that build a VSIX locally — the maintainer uploads to the marketplace
manually now, so the CI matrix and PAT secrets weren't earning their
keep.

Move editors/zed/ out into its own repo at
davidsmfreire/sqlshield-zed. Zed extensions are submitted to
zed-industries/extensions as submodule pointers, which expects a
dedicated repo. Update README to point at the new location.

Author: davidsmfreire

.github/workflows/vscode.yml

@@ -1,8 +1,15 @@
 .venv
 /target
 **/target/
+/dist
 .vscode
 
+# Local VSIX build artifacts (see `make vscode-vsix`)
+editors/vscode/server/
+editors/vscode/out/
+editors/vscode/node_modules/
+editors/vscode/*.vsix
+
 # Python
 __pycache__/
 *.py[cod]
@@ -18,3 +25,4 @@ Thumbs.db
 # Env
 .env
 .env.local
+post.txt

.gitignore

@@ -7,10 +7,6 @@ members = [
   "sqlshield-lsp",
   "sqlshield-py",
 ]
-# editors/zed targets wasm32-wasip1 and uses zed_extension_api; keep
-# it out of the main workspace so it doesn't interfere with normal
-# cargo build/test/clippy commands.
-exclude = ["editors/zed"]
 # Root `sqlshield-precommit` package is a pre-commit shim; exclude from
 # default builds so it doesn't clobber sqlshield-cli's `sqlshield` bin.
 default-members = [

Cargo.toml

@@ -37,3 +37,59 @@ all: clean dev-setup build test
 clean:
 	rm -rf .venv && \
 	cargo clean
+
+# --- VS Code extension --------------------------------------------------
+#
+# Build the VSIX locally. By default it bundles the sqlshield-lsp binary
+# for the host platform only; `vscode-vsix-target TARGET=…` builds for
+# any target rustc can hit (cross-compiling toolchain must already be
+# installed). The marketplace `--target` is inferred from TARGET.
+
+VSCODE_DIR := editors/vscode
+DIST_DIR   := dist
+
+# Host (no --target): produce a generic, untargeted VSIX. Fine for `code
+# --install-extension` on whatever machine you run this on.
+vscode-vsix:
+	cargo build -p sqlshield-lsp --release
+	mkdir -p $(VSCODE_DIR)/server
+	cp target/release/sqlshield-lsp $(VSCODE_DIR)/server/sqlshield-lsp
+	chmod +x $(VSCODE_DIR)/server/sqlshield-lsp
+	cd $(VSCODE_DIR) && npm ci && npm run compile
+	mkdir -p $(DIST_DIR)
+	cd $(VSCODE_DIR) && npx --yes @vscode/vsce package \
+		--out ../../$(DIST_DIR)/sqlshield-host.vsix
+
+# Cross-targeted build. Example:
+#   make vscode-vsix-target TARGET=aarch64-apple-darwin VSCE_TARGET=darwin-arm64
+# Maps:
+#   x86_64-unknown-linux-gnu  -> linux-x64
+#   aarch64-unknown-linux-gnu -> linux-arm64
+#   x86_64-apple-darwin       -> darwin-x64
+#   aarch64-apple-darwin      -> darwin-arm64
+#   x86_64-pc-windows-msvc    -> win32-x64
+#   aarch64-pc-windows-msvc   -> win32-arm64
+vscode-vsix-target:
+	@if [ -z "$(TARGET)" ] || [ -z "$(VSCE_TARGET)" ]; then \
+		echo "TARGET= and VSCE_TARGET= are required"; exit 1; \
+	fi
+	rustup target add $(TARGET)
+	cargo build -p sqlshield-lsp --release --target $(TARGET)
+	mkdir -p $(VSCODE_DIR)/server
+	@if [ "$(VSCE_TARGET)" = "win32-x64" ] || [ "$(VSCE_TARGET)" = "win32-arm64" ]; then \
+		cp target/$(TARGET)/release/sqlshield-lsp.exe $(VSCODE_DIR)/server/sqlshield-lsp.exe; \
+	else \
+		cp target/$(TARGET)/release/sqlshield-lsp $(VSCODE_DIR)/server/sqlshield-lsp; \
+		chmod +x $(VSCODE_DIR)/server/sqlshield-lsp; \
+	fi
+	cd $(VSCODE_DIR) && npm ci && npm run compile
+	mkdir -p $(DIST_DIR)
+	cd $(VSCODE_DIR) && npx --yes @vscode/vsce package \
+		--target $(VSCE_TARGET) \
+		--out ../../$(DIST_DIR)/sqlshield-$(VSCE_TARGET).vsix
+
+vscode-clean:
+	rm -rf $(VSCODE_DIR)/server $(VSCODE_DIR)/out $(DIST_DIR)
+
+.PHONY: hooks venv deps develop dev-setup build test all clean \
+	vscode-vsix vscode-vsix-target vscode-clean

Makefile

@@ -154,6 +154,10 @@ A first-party VS Code extension lives at
 [`editors/vscode/`](editors/vscode/README.md) — it spawns `sqlshield-lsp`
 over stdio and forwards diagnostics as you type.
 
+A Zed extension is published separately at
+[`davidsmfreire/sqlshield-zed`](https://github.com/davidsmfreire/sqlshield-zed)
+and wraps the same `sqlshield-lsp` binary.
+
 ## pre-commit
 
 sqlshield ships a [pre-commit](https://pre-commit.com/) hook so it can