Say which Docker resource is short for the back end, and where to raise it

CHANGELOG.md

@@ -72,6 +72,14 @@ deployment:
   and the end of its error output. A setup that stopped used to leave nothing in the log. The card
   says whether the back end stopped with an error partway, quit without saying why, or could not
   be run, where all three said "The back end could not start."
+- **A Docker short of disk, CPUs or memory says which, and where to raise it.** A setup the back
+  end refuses for its resources said "The back end stopped with an error partway through." It now
+  names the resource with the back end's own numbers: a full Docker disk says "Docker has 0 GB of
+  free disk. OpenBot needs 40 GB. Raise the disk limit in Docker Desktop > Settings > Resources, or
+  free space in Docker, then Retry.", and too few free CPUs or too little free memory say so the
+  same way. On Podman it names `podman machine set` instead. The CopilotKit account step now checks the engine first, and one
+  with fewer than 6 CPUs, less than 8 GB of memory or less than 40 GB of free disk stops there with
+  the same advice, before Start.
 - When OpenBot Desktop is signed in with a model Learning can't use, Learn now in Settings →
   Learning says "Learning can't run on the model you signed in with. To use it, sign OpenBot in with
   an OpenAI or Anthropic API key, or a Claude or ChatGPT plan.", where it told you to give the back

desktop/src-tauri/src/learning_model.rs

@@ -468,6 +468,7 @@ mod tests {
             licence_expires_at: None,
             update_to: None,
             checks_passed: readiness == crate::local_eval::Readiness::Ready,
+            shortfall: None,
         }
     }