feat: add _Template and New-Engine.ps1 for starting new engines

Each engine-building run started from a hand-copied scaffold (Qwen's),
which carried that engine's name and stale notes. _Template holds the
generic scaffold with a __NAME__ placeholder, and New-Engine.ps1 stamps
out a named copy. The template's starter tests go through the
benchmark's NestValidator, so a model gets a real pass/fail target
instead of a plumbing-only check; they were verified to pass against
Opus55.

Directory.Build.props now also detects when it sits in an Engines/
folder inside an OpenNest checkout, so an engine stamped there with
-IncludeBuildFiles builds without passing OpenNestRoot.

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

This commit is contained in:

2026-09-24 10:10:24 -04:00

co-authored by

Claude Opus 5.5

parent cfce484952

commit 70ae0cc155

8 changed files with 352 additions and 3 deletions

									
										_Template/OpenNest.Engine.__NAME__.csproj
									
		+3
		
												View File
												
				@@ -0,0 +1,3 @@

				<Project Sdk="Microsoft.NET.Sdk">

				  <!-- Shared settings and the OpenNest.Engine reference come from Directory.Build.props. -->

				</Project>