sendcutsend

# SendCutSend Provenance: maintained in [earthtojake/text-to-cad](https://github.com/earthtojake/text-to-cad). Use the installed local skill files as the runtime source of truth; the repository link is only for provenance and release review. Use this skill to produce conservative, evidence-backed SendCutSend preflight reports for DXF and STEP/STP files. Treat SendCutSend's ordering guide, catalog JSON, and specs JSON as evidence feeds, not stable APIs. Field names, types, and coverage may vary. Do not turn missing, unparsable, `N/A`, or conflicting source data into a pass or fail. Fetch sources directly from official URLs and use local inspection code only to measure specific file facts; write the final report from explicit comparisons. ## Geometry Inspection Use the active project Python environment for local geometry inspection code. If the `$cad` skill is available, use it first for STEP/STP/DXF geometry inspection, measurement, and validation workflows, then add any SendCutSend-specific targeted measurements that are still missing. Use `build123d.import_step` for STEP/STP inspection and the `ezdxf` package directly (`import ezdxf`; it installs alongside build123d) for DXF inspection when geometry facts are required. There is no `build123d.ezdxf`. Do not use raw text parsing or alternate geometry backends for geometry facts. ## CAD Viewer Handoff After completing SendCutSend work that creates or modifies a `.dxf`, `.step`, or `.stp` upload candidate, you must ALWAYS...