2 Commits

Include renames

Author	SHA1	Message	Date
aj	ed35b94e7f	test(cutting): keep both edge selections in corner classification theory ... Scoped dotnet format removed the unused entityIndex parameter from TraversedBackwards_SquareCornersStayConvex, leaving MemberData supplying two values to a one-parameter theory (8 xUnit failures at test discovery). The parameter is now genuinely used: each geometric corner is classified from both adjacent entities of the reversed contour.	2026-10-06 23:58:01 -04:00
aj	e75f68dbb6	refactor(cutting): share corner classification with entry planning ... Expose TryClassifyAutomaticStartCorner: an internal read-only query over the emitter's existing TryGetCorner/ClassifyCorner with the same winding derivation EmitContour uses, so start-point planning can prefer convex corners without copying tangent math or touching lead generation. Corner- kind characterization covers convex, reflex, tangent-smooth and cusp vertices from either adjacent edge, both windings, under rotation, and rejects midpoints and open contours.	2026-10-06 22:09:47 -04:00