KCL: Geometry debug tests

[adamchalmers]

cargo nextest run -p kcl-lib --nocapture -- geo_dbg::tests::simple_rectangle

should output data about the profiles in a KCL program, including how they're represented in KCL, in the engine, and in toolpaths.

It looks like this:

The OBJ data can be copied into the toolpaths repo and interactively viewed in their debugging tools.

Once this has been used a bit, and proven to be useful, we'll port it to the CLI. That way customers can use this and send us redacted data, or so that we can run it in a customer environment.

Part of #12477

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
modeling-app	Ready	Preview, Comment	Jul 16, 2026 7:41pm

[adamchalmers]

So far when you run

cargo nextest run -p kcl-lib --nocapture -- geo_dbg::tests::simple_rectangle

you get:

Running rectangle/tests/rectangle/input.kcl
Details of sketch001:
line1
  Type: Line
  Start: (-10), (-10)
  End: (40), (-10)
line2
  Type: Line
  Start: (40), (-10)
  End: (40), (90)
line3
  Type: Line
  Start: (40), (90)
  End: (-10), (90)
line4
  Type: Line
  Start: (-10), (90)
  End: (-10), (-10)
ID: 7b681387-29ea-57f1-8713-d63280827139

[adamchalmers]

Now you get a nicer table, and it shows both the KCL view of each segment, and the Engine view.

Running rectangle/tests/rectangle/input.kcl
Sketch ID: 7b681387-29ea-57f1-8713-d63280827139
┌───────────────┬──────────────┬────────────┬────────────┬──────────────┬────────────┐
│ Variable name │ Segment kind │ KCL start  │ KCL end    │ Engine start │ Engine end │
├───────────────┼──────────────┼────────────┼────────────┼──────────────┼────────────┤
│ line1         │ Line         │ (-10, -10) │ (40, -10)  │ (-10, -10)   │ (40, -10)  │
├───────────────┼──────────────┼────────────┼────────────┼──────────────┼────────────┤
│ line2         │ Line         │ (40, -10)  │ (40, 90)   │ (40, -10)    │ (40, 90)   │
├───────────────┼──────────────┼────────────┼────────────┼──────────────┼────────────┤
│ line3         │ Line         │ (40, 90)   │ (-10, 90)  │ (40, 90)     │ (-10, 90)  │
├───────────────┼──────────────┼────────────┼────────────┼──────────────┼────────────┤
│ line4         │ Line         │ (-10, 90)  │ (-10, -10) │ (-10, 90)    │ (-10, -10) │
└───────────────┴──────────────┴────────────┴────────────┴──────────────┴────────────┘

[codspeed-hq]

Merging this PR will not alter performance

✅ 126 untouched benchmarks
⏩ 151 skipped benchmarks¹

---

_{Comparing achalmers/geo-dbg (4251216) with main (4f69d73)}

Footnotes

1. 151 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[nadr0]

Do we want to assert any of the data this prints? Or is this more of a testing debug module?

[adamchalmers]

This is more of a test that it all works and can receive the data, I don't care about the specific data found here.