Release Notes
Authoritative Workspai changelogs, releases, compatibility history, and rules for interpreting shipped capabilities.
This page points to the authoritative release history for Workspai CLI and the VS Code surface. Use those primary sources when checking whether behavior is shipped, compatible, changed, or still planned.
When reading a release, distinguish:
- shipped CLI behavior,
- synced contract changes,
- VS Code surface compatibility,
- docs updates,
- planned roadmap items.
Current CLI baseline
The current CLI baseline is Workspai CLI 0.56.0. It adds the versioned universal Doctor diagnosis model, live-input graph fingerprints, project-scoped graph retrieval, stronger polyglot lifecycle orchestration, and portable proof resolution for linked external projects.
The website mirrors the complete 0.56.0 contract catalog. The extension's
minimum compatible CLI floor remains a separate contract and can be lower than
the current release; a backward-compatible CLI release does not automatically
raise that floor.
Evolution since 0.52
| Release | Shipped boundary |
|---|---|
0.52 | Verified Engineering Goals and evidence-backed definitions of done |
0.53 | CLI-owned Workspace Repair Engine with immutable plans, approval, checkpoints, verification, and rollback |
0.54 | Typed multi-ecosystem dependency materialization and target-aware repair receipts |
0.55 | Approval bound to causal actions, typed decision causes, and multi-project repair scope |
0.56 | Universal Doctor diagnosis, live graph freshness, C/C++ and polyglot runtime depth, scoped retrieval, and portable external proofs |
Changing a manifest is still progress, not completion. A governed repair must reconcile its materialized dependency state, run its declared checks, refresh the exact evidence producer, and return to canonical verification. The CLI—not an IDE or model—owns transaction closure and rollback.
Primary sources
How to interpret claims
A capability is shipped when its owning surface provides the corresponding command, contract, report, or user-facing behavior. Roadmap language and RFCs describe direction; they are not release evidence.