From 342d4e51a723035feb060dec7787e4aac08615d2 Mon Sep 17 00:00:00 2001 From: AJ Isaacs Date: Sat, 21 Nov 2026 13:23:11 -0500 Subject: [PATCH] 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 --- docs/problem-nests.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/problem-nests.md b/docs/problem-nests.md index 70bb042f..8f08ef5c 100644 --- a/docs/problem-nests.md +++ b/docs/problem-nests.md @@ -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,