docs(problem-nests): ask for sectioned, bulleted corpus comments

The corpus nests' comments were single long paragraphs that were hard to
scan in the comment box; they were rewritten on the server as Setup /
Problem / Fix sections. Describe that layout so new nests follow it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ajandClaude Opus 5.5 committed 2026-11-21 13:23:11 -05:00
1 parent 18ab2f2cbb
commit 342d4e51a7
1 file changed
+3 -1
+3 -1
View File
@@ -164,7 +164,9 @@ Plates use their own cutting parameters. A plate without them uses line lead-ins
then drag the `.nest` file onto the window. Keep the corpus server selected until the save in
step 4 succeeds, then restore your previous storage settings.
2. In **Nest > Edit**, name it after the problem, and in the comments describe what failed
and which commit fixed it, if any.
and which commit fixed it, if any. Keep it scannable: short `Setup:`, `Problem:` and `Fix:`
sections separated by blank lines, with `-` bullets rather than one long paragraph. Never
start a prose line with one of the machine-read prefixes below.
3. Add a baseline line to the comments, with plate numbers counted from the first plate:
`planning: 1=NoSolutionWithinBudget 2=BestEffort`. An Auto Nest problem takes
`auto-nest: 2 sheets` instead, the sheet count Auto Nest reaches today (`auto-nest: 1 sheets,