kerfmaster pin list · UI / workflow decisions
recordStates what the code does today. Auditable against the code — this is the only type that can go stale.
Content last changed 2026-08-28 — computed from the item itself, not typed.
Approved by Jordan, 2026-08-28 ('Good idea, this would be a good way to double check things as we move along'), as the in-phase first form of the toolpath view intent: an audit artifact, not an interface.
record — toolpath_plot.py: renders a one-page PDF (optionally SVG) from the posted NC alone, via pierce_clear.parse_nc — the same parser nc_audit and the pierce report trust, so what the machine will see is what is drawn. Elements: contour in green with direction arrowheads spaced along the path (count scales with feature size); lead-in as an orange stroke pierce→contour start (coloured apart from the contour deliberately — the point of the view is seeing where pierces and leads sit); red pierce dots numbered with the cut sequence; rapids dashed grey, previous boundary's end → next pierce, the first from X0Y0 part origin (the G52 shift is machine-side and not drawn). Tab gaps show as the gaps they are. Like nc_audit it can be pointed at anyone else's NC for the same job.
Wired into post_nest (stats['toolpath_plot'], a toolpath button on the build page) so every posted program ships one. First artifact: build 142's 3A76 post, retro-plotted as the demo — 5 features, holes pierced at centre with CCW arrows, outer last, pierce in scrap.