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-09-01 — computed from the item itself, not typed.
record — built 2026-09-01, the second half of Jordan's warning ruling (2026-08-28: “if GCodes get generated with a yellow or red warning, it should put it in (warning) in GCode… there should be an extra callout at the top: (Contains X # of warnings)”), sitting on the shared rule checks shipped the same day: nc_audit.audit() now returns its rules.py findings in structured form (severity + affected bnds) and nc_warn.inject() writes them into the program.
What the operator sees: under the O-number, (CONTAINS N WARNINGS) followed by every finding's full message, numbered — the SAME shared string the audit reports and the click-time check will show, so all three surfaces carry identical wording. At each affected boundary, a one-line marker (WARNING k: YELLOW PIERCE STANDOFF) pointing at the numbered message up top. Fanuc comments cannot nest parens, so message text is sanitised (parens → brackets) on the way in.
Macro programs: the audit judges the EXPANDED part-by-part form, so its findings arrive on expanded boundary numbers; nc_warn maps each one back to (subprogram, local bnd) and the marker lands in the sub once, covering every arrayed instance — on the O33286 control the 950 centre-pierce findings collapse to 18 spot markers on the hole boundaries (local bnds 1–5, never bnd 6, the outer that cuts last).
Comments change nothing, and that is enforced: post_nest re-audits the annotated file and raises if the anomalies differ; controls also prove the parsed geometry is identical pre/post injection and a clean program is left byte-identical. Warn, never block: a program with warnings still posts — it just says so, because the laser operator is a different person from the programmer and the warning must travel with the program.
Controls: test_nc_warn.py, 12 PASS (plain + macro + no-findings paths; end-to-end smoke through post_nest on the 101-tl101687 sheet: 7 pierce findings → header block + 7 spot markers, transparency re-audit clean). Severity colours remain the PROPOSED table awaiting Jordan's ratification. Open next: the same callouts at delivery time for programs posted outside post_nest (deliver scripts that call emit directly).