docs: correct cut planning effort scope and problem-nest storage steps

Console --plan-cutting and MCP plan_cutting run the planner at the default
effort; only the desktop exposes the setting. Adding a corpus nest must keep
the corpus server selected until the save, and the command is Nest > Edit.

docs/cutting-planner.md

@@ -625,9 +625,9 @@ panel is wired in the editor. Non-editor callers still use the shared analyzer.
   plates, so a higher effort spends more only where the full search runs and leaves easy
   plates' plans unchanged. A plate refused because a search reached its limit (its own
   plan, or the free-order attempt before the current order was kept) says the effort can
-  be raised; a longer search may still find no plan. Only the desktop plans cuts: the
-  console, MCP server and API create plates but do not call the planner, so they have no
-  budget to configure. Direct `CuttingPlanRequest` callers set `expansionBudget` themselves.
+  be raised; a longer search may still find no plan. The effort is a desktop setting: console
+  `--plan-cutting` and MCP `plan_cutting` run the same planner at the default effort (1.0)
+  and have no effort option, and the nesting API does not plan cuts. Direct `CuttingPlanRequest` callers set `expansionBudget` themselves.
 - The docked panel keeps text short: one colored outcome line for the batch, one line for the
   shown plate, and one detail line (a remedy for a blocked plate, or what the selected marker
   shows). Below them is a read-only, unsorted issue grid with Plate, source Part, With, and full

docs/problem-nests.md

@@ -34,9 +34,10 @@ Plates use their own cutting parameters. A plate without them uses line lead-ins
 
 ## Adding a nest
 
-1. In the desktop app, point **File > Storage Mode...** at the corpus server, then drag the
-   `.nest` file onto the window. Switch the server back afterwards.
-2. In **Nest > Nest Info**, name it after the problem, and in the comments describe what failed
+1. In the desktop app, choose Database mode and the corpus server in **File > Storage Mode...**,
+   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.
 3. Add a baseline line to the comments, with plate numbers counted from the first plate:
    `planning: 1=NoSolutionWithinBudget 2=BestEffort`.