docs(models): document the queued manual imports — swagger, specs, docs

- swagger: annotate POST /models/import (untyped body: documenting it
  as config.ModelConfig would inline the whole type graph, ~5.5k
  generated lines; the description spells out the dual response) and
  regenerate the spec
- tests: pin the admission contract of the queued branch — job id +
  status URL, job queryable before the worker runs, config not written
  at admission, preload-matching filenames, checksum passthrough, and
  the untouched synchronous path
- docs: the Writing YAML section explains when Create queues and what
  the API answers in each case

Assisted-by: Claude:claude-fable-5
Signed-off-by: Plamen K. Kosseff <p.kosseff@gmail.com>
(cherry picked from commit aec658a998)

docs/content/getting-started/models.md

@@ -143,6 +143,20 @@ This is especially useful for:
 - Setting up complex model setups
 - Editing existing model configurations
 
+When the configuration references remote assets — a URL in
+`parameters.model` or `mmproj`, or `download_files` entries — **Create**
+does not download them inside the request: the import is queued like a
+gallery installation, and the page reports the job's progress until the
+model is ready. The configuration file is written once every download
+has finished, so a failed download never leaves a config pointing at
+files that do not exist. A configuration that only references files
+already on disk is written immediately, as before.
+
+The same split applies to the API behind the page: `POST /models/import`
+answers a queued import with a job id and a status URL to poll
+(`/models/jobs/{id}` — the same shape gallery installs use), and a
+download-free import with a plain success response.
+
 ## Method 2: Installing from Hugging Face
 
 LocalAI can directly install models from Hugging Face: