3 people 695ccc0a3b perf(engine): use cached triangulations in the layout check ...

The benchmark validator and every engine test re-triangulated both parts
for each nearby pair. NestLayoutCheck now uses TriangulatedRegion, with
Collision.HasOverlap as the fallback when it cannot decide. Verdicts are
unchanged (the frozen-validator equivalence tests still pass); validating
100 discs went from 1,254 ms to 94 ms.

Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-25 10:08:36 -04:00

..

BenchmarkRunnerTests.cs

[verified] add benchmark baseline and rotation fixes

2026-09-22 16:35:25 -04:00

BenchmarkScoringTests.cs

feat(engine): expose NestJobCost, the benchmark's scoring

2026-09-25 08:12:07 -04:00

JobLoaderManifestTests.cs

refactor(engine): align namespaces with directory layout under OpenNest.Engine

2026-09-21 13:18:34 -04:00

LegacyNestValidator.cs

refactor(engine): expose the layout validation contract to engines

2026-09-25 08:54:54 -04:00

NestLayoutCheckEquivalenceTests.cs

refactor(engine): expose the layout validation contract to engines

2026-09-25 08:54:54 -04:00

NestLayoutCheckMarksTests.cs

fix(engine): leave scribe marks out of layout bounds and salvage

2026-09-25 08:56:49 -04:00

NestLayoutCheckTimingTests.cs

perf(engine): use cached triangulations in the layout check

2026-09-25 10:08:36 -04:00