Repository navigation
MusubiCAD CLI v0.2.0
MusubiCAD v0.2.0 brings the accumulated parametric modelling, drawing, sketch and backend-owned desktop editing work into the official CLI distribution. The CLI is now named musubicad; archives retain the opencad forwarding alias.
Changes include semantic drawing dimensions and manufacturing outputs; datum, draft, rib, hole/thread-standard, fillet and body-boolean operations; construction geometry, bounded trim/offset/ellipse/projection and scoped closed cubic curves; assembly BOM, exploded/coupled-joint workflows; and shared feature/selection/sketch editing commands for Tauri, Agent JSON-RPC and MCP. Each operation retains its documented admission limits. General NURBS editing and unrestricted direct modelling are not introduced.
All CAD changes use backend DesignPatch validation, regeneration and history. Missing/ambiguous/stale semantic bindings, unsupported operations, unit errors and failed required verification refuse instead of publishing guessed geometry.
Each CLI archive includes a reproducible editing tutorial, its ellipse fixture and scenario. It reviews and edits through real MCP/Agent processes, verifies source/refusal/Undo/Redo and checks exact dimensions 80×30×10 mm and volume 18849.555922 mm³. To run it (Python 3.10+):
python tools/run_editing_tutorial.py --binary ./musubicad --fixture examples/ellipse_plate.ocad.d
Windows uses --binary ./musubicad.exe. Add --output my_ellipse.ocad.d to retain a verified final copy at a new path. Read EDITING-TUTORIAL.md in the archive.
The release workflow builds and smoke-tests all four native platforms and executes the tutorial from each extracted archive before publication. Verify the archive against the attached SHA256SUMS before running it. CLI archives are unsigned; checksums are not publisher signatures. Tauri desktop installers remain separately distributed workflow artifacts under the existing desktop trust policy.
Actual client/platform evidence is recorded separately. A protocol/native smoke test does not establish Cursor/Gemini integration or Windows desktop interaction. Physical nonempty BodyCount, arbitrary/custom-plane sketch editing and the other documented bounded geometry limits remain explicit.