aj 0a1d021bf7 refactor(engine): rename the Default engine and fill strategy to Fill ...

The multi-phase lattice fill (linear, pairs, rectangle best-fit, remainder) is
no longer meant to be the engine used by default, so it gets a name for what
it does. The registry lists it as Fill and maps the old name Default to it;
PlateFillService, PlateNesterFactory and NestJobOptions use Fill, and every
fill-strategy caller still accepts Default. Console --autonest now validates
engine names through NestingEngineRegistry.ResolveName so renamed names work.

Layouts are unchanged: Default and Fill resolve to the same fillers and the
golden layouts pass under the new name.

2026-10-06 12:11:03 -04:00

..

AreaPackerTests.cs

refactor(engine): rename the Default engine and fill strategy to Fill

2026-10-06 12:11:03 -04:00