Add Zed extension source

[petercr]

Summary

• add the Varlock Schema Zed extension source under packages/zed-plugin
• include the bundled TypeScript language server source and Tree-sitter grammar
• add docs/listing updates for the monorepo-hosted extension
• pin the Zed grammar manifest to a commit that contains the grammar path

Verification

• npm --prefix packages/zed-plugin/server run build
• cargo check
• bun run lint packages/zed-plugin

[philmillman]

Thanks @petercr! You're welcome to move the extension itself into the repo (in /packages) if you want

[petercr]

great thanks @philmillman
I go ahead and send over a PR for that instead.
That does make more sense.

[theoephraim]

Just saw https://github.com/johnsoncodehk/monogram yesterday - doing a spike checking it out. In theory this would mean a single grammar that spits out our parser along with textmate rules and tree-sitter, so things would never get out of sync. Will hold off merging this until I see if it's viable. But will try to get this all over the finish line one way or another soon!

[petercr]

@theoephraim great 👍🏻 sounds like a lot less moving parts if it works out.
Just let me know.
Thanks

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo writeable is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/zed_extension_api@0.7.0 → cargo/writeable@0.6.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/writeable@0.6.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[theoephraim]

hey @petercr - just a quick update. Sorry for the delay. The monogram stuff is very promising, so looks like we will move things over, and try to unify all the language server-y stuff, and then combine with this!

[petercr]

@theoephraim cool no problem on the delay. Besides it works on my machine 😂

I did push some updates today to my repo, but nothing too big. Updates and improvements.

I can send those over after we tie in the new lang server.
Just let me know how that goes 🙌🏻