fix: remove zero-length trace segments from duplicate consecutive points (#78)

[voltrace-io]

Summary

Fixes #78 — extra trace lines in post-processing step.

Root cause: _applyBestRoute() in UntangleTraceSubsolver splices rerouted segments into the original trace path, which can produce consecutive duplicate boundary points. These zero-length segments survive the existing collinear-collapse pass in simplifyPath and render as extra trace lines in the schematic output.

Fix: Added removeDuplicateConsecutivePoints() to strip identical adjacent points (within floating-point epsilon) before each collinear-collapse pass in simplifyPath(). The function alternates dedup→collapse→dedup→collapse→dedup to ensure all zero-length segments are eliminated regardless of ordering.

Result: example35 snapshot reduced by 35 SVG lines, confirming extra trace removal.

/claim #78

Review & Testing Checklist for Human

• Verify example35 snapshot diff shows trace improvement (fewer overlapping lines), not regression
• Run bun test — should see 67 pass, 4 skip, 0 fail
• Check that the epsilon tolerance (1e-9) in removeDuplicateConsecutivePoints does not incorrectly merge nearby but distinct points in dense schematics

Notes

• 8 new unit tests cover: duplicate points at start/middle/end, multiple consecutive duplicates, zero-length two-point paths, collinear collapse, and duplicates at direction changes
• The collinear-collapse logic is unchanged — only the dedup preprocessing is new
• simplifyPath is called during the post-processing cleanup pipeline, so this fix applies to all traces automatically

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
schematic-trace-solver	Ready	Preview, Comment	May 22, 2026 12:42am