28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
# OpenSCAD desktop integration
|
|
|
|
Batch: `29db3556c97a977c84abcf25`.
|
|
|
|
The Python family dispatcher now invokes the existing native desktop command
|
|
handler for desktop-command records. That handler restricts execution to the
|
|
ten commands selected in this batch. The application dispatcher uses the new
|
|
OpenSCAD adapter to propagate native failures and apply returned selection to
|
|
the existing workbench document selection callback.
|
|
|
|
No business acceptance is claimed. Build, artifact synchronization and native
|
|
acceptance remain owned by the outer pipeline. Type checking was attempted but
|
|
`web/node_modules/.bin/tsc` is absent (exit 127).
|
|
|
|
Remaining verification boundaries:
|
|
|
|
- Execute all ten selected commands against actual objects in the OpenSCAD
|
|
runtime, including transaction rollback and parametric recomputation.
|
|
- Confirm document ownership through the existing import/document workflow;
|
|
this change does not transfer documents between independent WASM instances.
|
|
- Check desktop selection type rules, particularly replacement and subtree
|
|
removal: the existing native handler currently requires Part::Feature for
|
|
every non-mesh command.
|
|
- Native geometry is returned by the existing handler. View visibility and
|
|
geometry display consumption are not established by selection synchronization.
|
|
- Rebuild the affected runtime and verify the family result schema and native
|
|
error propagation through the Worker and application.
|