Studio developer intelligence

The starting branch was studio/workspace-terminal at 256b2cf8119436af2dd8e48a1e056ab8690f9973. Development is isolated on studio/developer-intelligence. The QA installer has a separate app ID and per-user registration. Stable-preview distribution is a separate release decision.

Architecture

zbl-language-server speaks JSON-RPC over LSP stdio with Content-Length framing. The server negotiates UTF-16 source positions and accepts incremental document changes. Compiler analysis uses the same lexer, parser, project module linker, generic specialization and type checker as ZBLC. Unsaved text is an overlay. Project analysis reads the entry's reachable import graph, skips lockfile creation, and records source locations before lowering or mangling. A workspace symbol query searches graphs associated with open source documents. Studio and the standalone server opt into the compiler crate's ide feature. The default SDK binary stays within its existing 32 MiB debug bootstrap ceiling.

Studio invokes the shared compiler query engine through an allowlisted Tauri IPC command. Monaco supplies a scoped model identity, a snapshot of open source text in the same root, and an LSP-shaped request. The bridge canonicalizes paths, checks scope and maps returned locations to openable Studio paths. A serialized request queue drops cancelled or superseded Monaco results. Diagnostics are debounced. The CLI remains the execution path for Build, Run and Test.

The interpreter debugger uses a Tauri channel for stop, resume and state events. Its observer runs inside the real interpreter at source statement boundaries. Frames carry the current source token and current-frame locals come from the interpreter's environment. The adapter uses cooperative interruption and one active debug session. Runtime filesystem grants remain disabled for debug launches. The interpreter's limits still apply.

Capability matrix

Security and operations

• Editor analysis is read-only. Canonical paths are restricted to the selected root. External dependencies require an enclosing authorized workspace. The compiler and bridge enforce bounded source, overlay and module counts. Shells keep their existing OS-level permissions after trust approval.
• Analysis uses an isolated worker thread and a bounded request payload. A malformed framed message gets a protocol error. An invalid or oversized framing length ends the stdio process. A new process starts with fresh roots and overlays. Studio's in-process bridge shares compiler logic with the executable and has no stdio child to restart.
• The debug adapter redacts local names that look like credentials and summarizes containers. It exposes normal program output and does not guarantee redaction of arbitrary application data. It does not access the BYOK credential store.
• The verified installer is an unsigned internal candidate. GO for local Windows QA. NO-GO for public distribution and unsupported debugger targets.

Reproduce QA

Follow the Studio Windows build instructions. With Node 24, run node studio/scripts/verify-language-server.mjs <zbl-language-server.exe> <evidence.json> for the standalone protocol suite. Run the installed Windows harness against the separate Developer QA package to test the same executable after installation, along with real WebView and interpreter workflows.

The protocol definition is available from the Language Server Protocol 3.17 specification.

Windows regression and performance evidence

On Windows 11 25H2 x64, the baseline installed v0.1 suite passed all 24 checks. The v0.2 SDK regression suite passed 177 tests, including the bootstrap install, update and uninstall lifecycle and the interpreter observer test. The IDE-feature library suite passed 3 tests. The Studio Rust suite passed 3 tests. TypeScript checking and the Vite production build passed. The Windows GNU linker emitted its duplicate resource manifest warning, and Vite reported the existing large Monaco bundle.

The optimized standalone executable was measured for 25 sequential stdio hover requests per fixture. The two-file project measured 15.95 ms median and 16.13 ms p95. A generated project with 17 files and 192 exported tasks measured 27.52 ms median and 74.13 ms p95. These are end-to-end timings from the Node harness including transport and polling. They are specific to the Windows QA machine and fixtures.

The Windows QA setup SHA-256 is f6f1658ac513a73b542b05604f1756534021ab07ae5be5330b5d71bd4e3e4ce7. The existing Studio v0.1 executable still matched 305962d4d7fcf32caf71278736659365e26f484fb2ec23ffb5706086889f0ed1. The first final-artifact installation passed 33 checks and the reinstall passed 34, including six installed stdio protocol checks reported separately by the language-server harness. The desktop tests exercised real Monaco completion, hover and rename undo, plus breakpoint, call stack, locals, Step Into, Step Over, Step Out, Continue and Stop. A JavaScript program received its literal command argument and environment override. QA uninstall removed the registration and preserved the test projects.

Code map

• crates/zbl/src/ide.rs, lsp.rs and language_server.rs implement compiler-backed analysis and stdio. project.rs shares the real linker, runtime.rs exposes interpreter hooks, and tests/ide.rs verifies runtime frames and bindings.
• studio/src-tauri/src/intelligence.rs, debugger.rs, launch.rs and terminal.rs connect language, debug and run workflows to authorized workspaces. Windows staging adds the sidecar to the isolated installer.
• studio/src/intelligence.ts, App.tsx, EditorPane.tsx, editor.ts, TerminalPane.tsx and style.css integrate Monaco, the Problems and Debug panels, and run options. The Windows and stdio verification scripts exercise the installed desktop and standalone process.