Studio QA release history
Read the earlier Windows QA acceptance record and its scope.
Development branch studio/premium-workbench-v03 starts from 7b9928c. The ZBL worktree was clean before the SDK and Studio upgrade began. The branch preserves the existing Tauri shell, Monaco models, Rust workspace bridge, PTY backend, compiler query engine, and Zebvix command dispatch.
The React workbench owns panel layout and presentation. The Tauri bridge authorizes work against a selected workspace root. The bundled Zebvix executable builds local contract artifacts. The SDK library verifies those artifacts and runs the same transition engine in the CLI and desktop. The desktop displays decimal i64 values as strings and provides the original canonical JSON receipt for comparison.
Milestone matrix
| Area | Classification | Scope |
|---|---|---|
| A. Visual shell and themes | IMPLEMENTED | Graphite, Light and High Contrast, command palette, welcome shortcuts, expandable and persisted panels, Studio and SDK version display |
| A. Complete menu, status and activity specification | PARTIAL | Existing menus and activities remain. Cloud account, collaboration, extension and agent controls are absent. The status bar does not expose every requested field. |
| B. Workspace and editor | PARTIAL | Multi-root Explorer, custom paths, file management, drag-and-drop, open tabs, split, diffs, unsaved changes protection, native reveal, file and content search, and Counter template. Workspace-wide replace, comprehensive file watchers, and configurable keybindings are outstanding. |
| B. Git | PARTIAL | Status plus staged and unstaged diff preview from trusted roots. Stage and unstage controls, commits, history, branch management, and clone UI are outstanding. |
| B. Native terminal and project commands | PARTIAL | Windows PowerShell PTY, multiple sessions, split terminal view, per-project directories, cancellation, SDK commands and saved-source contract build. The complete output panel specification and Linux runtime verification are outstanding. |
| C. ZBL intelligence and debugging | PARTIAL | Compiler-backed navigation, diagnostics, completions, rename preview and interpreter debugging. External LSP adapters and standard DAP transport are outstanding. |
| C. Other languages | PARTIAL | Existing Monaco syntax and built-in web language services remain available. External LSP server coverage and QA for the requested languages are outstanding. |
| D. Offline work and OpenAI BYOK | PARTIAL | Manual workspace works offline. Existing OS credential storage, explicit context and a one-file diff with manual apply remain. Live provider credentials and provider billing were outside this run. |
| D. Additional providers and multi-file AI | NOT IMPLEMENTED | Anthropic, Gemini, managed AI, project-wide edits, usage accounting and billing require separate work. |
| E. Multi-agent execution | NOT IMPLEMENTED | No agent runner, model assignment, delegation, resource quotas or review automation. |
| F. Accounts and team collaboration | BLOCKED | A configured authentication and authorization backend is required before account, role or invitation flows can be verified. Team synchronization and real-time editing are unimplemented. |
| G. Extensions and connected apps | NOT IMPLEMENTED | No plugin host, marketplace lifecycle or OAuth connectors. |
| G. Local contract workbench | IMPLEMENTED | Counter template, new artifact build, local artifact picker, SHA-256, bounded timeline and canonical receipt, failure reporting and existing-artifact preservation |
| G. Signed transactions and chain tooling | PARTIAL | The separate offline ZBX V3 and ZBVM fixture verifies signed envelopes, replay and recovery. Studio does not expose that journal or signed-transaction inspector. Chain deployment and validator integration are outside this build. |
| H. Linux | BLOCKED | Linux bundle configuration exists. No working Linux runtime is available on the Windows host. Linux build, installation and runtime remain unverified. |
| H. Public distribution | BLOCKED | The SDK preview is unsigned and staged locally. A signed public release, hosted service setup and independent security review are pending. |
Security boundaries
- Simulation requires a trusted root, a checked workspace-relative
.zctpath, bounded input count and an artifact that passes SDK validation. A failing transition returns an error and creates no receipt or persisted contract state. - The artifact builder calls a fixed Zebvix command with argument passing and refuses to overwrite an existing output. The application asks the user to save edits before building.
- Git diff requires a trusted workspace. It disables external diff and text conversion, caps output at 100,000 bytes and uses fixed Git arguments. Workspace trust permits local Git and shell execution with the user's OS permissions.
- The existing workspace file checks reject traversal and reparse points and assume the workspace is stable while an operation runs. These checks provide path scoping. OS-level sandboxing, managed AI authorization, plugin permissions and persistent audit logs are outstanding.
- The QA installer has a separate Windows application ID and uninstall registration. The existing Studio installation and user projects are preserved.
Windows verification
- The final Windows installer passed 43 desktop assertions covering startup, uninstall registration, project and file operations, native terminals, interpreter and bytecode parity, Git diff, installed language-server requests, compiler-backed edits, debugging and project preservation. It also compares the canonical Studio receipt with the bundled CLI, tests exact i64 display and checks build overwrite and artifact traversal refusal. The packaged frontend asset matched the latest build. The installed legacy executable retained its SHA-256 hash.
- The Studio Rust unit run passed three tests, including a round trip through Windows Credential Manager with a disposable test entry. No live AI provider request or hosted authentication was exercised.
- The SDK passed 184 Rust regression tests. The bootstrap lifecycle ran separately on the release executable because the IDE-feature debug binary exceeded the bootstrap size limit. The release CLI passed 40 lifecycle assertions and six controlled transport cases. The extracted SDK passed 86 installed checks, including activating preview.4 after preview.3 and preserving 157 prior files. The Windows offline ZBVM fixture passed its replay and journal verification.
- The first parallel Tauri build hit Windows paging-file error 1455. The single-job build produced the NSIS bundle. GNU ld emitted a resource-manifest merge warning. The installer and runtime tests verify the resulting Windows package.
Changed source areas include the Studio App, CommandPalette, ContractPane, editor and stylesheet, the Tauri launch and terminal bridges, the version manifests and lockfiles, and the Windows preparation and verification scripts. The SDK changes cover contract simulation, the CLI, preview lifecycle and release packaging. Git records the complete file list.
GO for internal Windows QA. NO-GO for public or cross-platform release. Public signing, live service integration, Linux verification and the remaining security and feature work are required before broader release.