lsp

Arguments and rejection

Use topaz lsp without a positional operand. The accepted options are --compiler rust or --compiler self, --verbose, --root <dir>, --language-version <version>, --compiler-memory-mib <MiB> and --compiler-time-ms <ms>. The compiler defaults to self for the current language profile.

Memory and time budgets are positive decimal integers. Explicit options override TOPAZ_COMPILER_MEMORY_MIB and TOPAZ_COMPILER_TIME_MS. The defaults are 8192 MiB and 1800000 ms. Reject missing values, zero budgets, malformed numbers, unsupported language profiles, repeated options, equals forms and all unlisted options before starting the session.

initialize.rootUri selects a local workspace when supplied. The CLI root is the initial workspace and the fallback when initialization supplies no local root. Bind the compiler to the admitted workspace language profile. An explicitly selected compiler that cannot serve that profile fails without silently choosing another compiler.

Output

Standard output contains only LSP messages. Each message has a Content-Length header, a blank line and the indicated number of UTF-8 JSON bytes. JSON-RPC response identifiers match their requests. Diagnostics use protocol notifications and do not become a human stdout banner.

Human startup and transport errors use standard error. --verbose reports the resolved compiler and selection origin on standard error. There is no separate human or selectable JSON report mode. Reject both --format human and --format json as unsupported startup options.

Initialization describes the supported editor capabilities. Request failures use protocol error responses when a response can be sent. Program diagnostics in a valid response do not by themselves terminate the server.

Exit status

Exit 0 when the client ends the session with an exit notification or clean end of input between messages.

Exit 1 for invalid startup arguments, invalid locked workspace state, an unavailable selected compiler, failure to start a compiler worker, malformed or truncated transport framing, or failure to read or write the session stream. No response for an unfinished request is presented as a successful result.

Filesystem effects

Read the selected local source tree and its already materialized dependencies. Open document content replaces the corresponding disk content only in the session snapshot.

Keep edits and proposed renames in protocol responses. Do not write the source tree, manifest, lock file or vendored files. Any compiler worker storage is private temporary state and is reclaimed when the session ends.

Only a local file root participates in package loading. A root URI that cannot denote a local directory leaves the CLI root fallback in effect and grants no remote filesystem access.

Network access

Use standard input and standard output for transport. Do not open a listening socket, contact a registry, download a compiler or fetch imports.

Reproducibility

The same installed toolchain, selected compiler, language profile, workspace bytes, valid lock, document overlay sequence and request sequence produce the same semantic responses and diagnostic ordering.

Protocol identifiers are copied from requests. Client scheduling and resource timeout outcomes are outside a byte comparison unless the request order, budgets and termination conditions are also fixed.

Packages and locks

A workspace containing topaz.toml uses its package graph and a valid topaz.lock for package diagnostics. Missing, stale or invalid locked dependencies are errors and are not repaired by the server.

Read dependency entries in the table form required by the package contract. A standalone document without a package is checked as a standalone source snapshot. The server never runs lock, add or vendor.

The invocation topaz lsp main.tpz --language-version 5.21 is expected to exit with 1.