mirror of
https://github.com/hanzoai/lsp.git
synced 2026-09-30 22:52:48 +00:00
zeekayandHanzo Dev
121aea3331
The entry described a Deployment somebody would have to write. It is written — hanzoai/universe charts/app/values/hanzo/lsp.yaml, synced by cd.hanzo.ai, with LSP_KEY coming from hanzo/lsp/LSP_KEY@prod through a KMSSecret and read by cloud from the SAME path, so the proxy's X-API-Key and the daemon's key are one value rather than a pair to keep in step. What replaces the aspiration is the honest list of what is still in the way, and none of it is code in this repository: gVisor is installed on no node (the installer named a pool that does not exist and has been 0/0/0 for a month; the fix is committed and unapplied), the pool it now names cannot hold an 8Gi pod, and the first image is still building. The last paragraph is the one worth keeping: none of that is dangerous, because the boot-time probe refuses readiness when the jail does not work here. A wrong node produces no endpoints, not an unjailed language server. Co-authored-by: Hanzo Dev <[email protected]>
lsp
The jailed language-server daemon. It holds immutable per-(org, repo, commit) working trees, runs a language server over each one inside a jail with no network, and answers position questions about them.
The answer it exists for is a definition that leaves the repository and lands in a dependency — which a static symbol index structurally cannot give you.
POST /root {org, repo, rev, files} → {ready, cold, langs}
POST /root/warm same body, only for a held repo
POST /ask {org, repo, rev, op, path, line, character, relation}
→ the answer, or 409 {"need":"tree"}
GET /healthz liveness
GET /readyz readiness — green only once the jail proved out on this host
Everything else — the wire contract in full, the two-phase security model, the deployment, and what phase 2 is — is in LLM.md.