1.0 KiB
MeshPart Curve Boundary Repair
The native MeshPart curve-on-mesh adapter already computed the curve length
from the supplied mesh and point sequence. Its response nevertheless always
included implementationBoundary=web_ui_point_selection, which made a valid
native result look incomplete to downstream routing.
The boundary is now emitted only when the mesh handle or curve points are missing. A valid point-picking payload keeps the real native result; missing interactive input remains an explicit dependency/error. No curve geometry is created in Three.js and no native result is fabricated.
Build receipt: meshpart-curve-boundary-repair-pipeline.json.
| Step | Seconds |
|---|---|
| Module registry | 0.101 |
| Capability registry | 7.971 |
| Preflight | 0.042 |
| MeshPart native build | 37.028 |
| Artifact sync | 3.039 |
| Metadata generation | 0.931 |
| Pipeline total | 49.112 |
No automated validation was run. Geometry remains owned by the existing FreeCAD/OCCT WASM path; Three.js remains display and input only.