You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8cf5d60
Browse filesBrowse the repository at this point in the historyBrowse files
The published pages still described the arrangement this series replaced,
and the two front ends reassured users differently about the same action.
engine-lifecycle.mdx and architecture.mdx still placed llama.cpp's cache
"beside PAIR's managed install", the location that was lost when app data
was purged. terminal-interface.mdx described the TUI reset without the
engine removal it now performs or the models it keeps. The desktop
architecture note and the root README listed only two of the three model
stores, and the README promised a Linux purge removes "any engine PAIR
installed" when one placed in the user's home by a vendor installer
survives it.
The wipe scripts' "never add" comments omitted ~/.llamacpp. That comment
is what a future editor reads before adding a wipe target, so leaving the
newest store out of it is the omission most likely to cost someone their
models.
MANIFEST.md: models_dir was missing from the shared-defaults row, the
Validation section did not list the rejections this series added, and the
{models_dir} row overstated where the placeholder resolves -- install
provides only {install_dir}, and naming the store in uninstall.remove is
rejected at load.
The desktop uninstall confirmation now matches the TUI's, which says
downloaded models are kept. Asking "are you sure?" while the other client
explains the consequence left the more cautious wording on the quieter
surface.
Signed-off-by: Terve <ntervalon@nvidia.com>
|`manifest_version`| int | yes | Must be `1`. A higher value is rejected (asks for behavior this binary lacks). Unknown optional fields within a supported version are ignored, so the schema can grow additively. |
123
123
|`platforms`| object | yes | Map of `"<goos>/<goarch>"` → platform block (e.g. `"windows/amd64"`, `"darwin/arm64"`, `"linux/amd64"`). At least one entry. The runner selects the block matching the host. |
124
124
|`actions`| object | no | Map of action name → action (see below). |
125
-
|`detect` / `install` / `uninstall` / `runtime`| — | no | Optional **shared defaults** inherited by every platform (see below). |
125
+
|`detect` / `install` / `uninstall` / `models_dir` / `runtime`| — | no | Optional **shared defaults** inherited by every platform (see below). |
126
126
127
127
**Shared defaults & per-platform overrides.** The platform-level fields `detect`, `install`, `uninstall`, `models_dir`, and `runtime` may also be given once at the top level as shared defaults; each `platforms` entry is then merged onto them. Nested objects (e.g. `runtime`, `runtime.env`) merge key-by-key with the platform value winning, while arrays and scalars are replaced wholesale. So a runtime that's identical across platforms except `cli` is declared once at the top level, and each platform sets only `"runtime": { "cli": "…" }`. Omitting a key inherits the default; setting it (even to a zero value like `"port": 0`) overrides it. A manifest that fully specifies each platform with no top-level defaults behaves exactly as before.
128
128
@@ -376,7 +376,7 @@ validation at load:
376
376
|`{download}`| Path of the verified download |`install.run`|
377
377
|`{download_<name>}`| Path of a verified member of `install.artifacts`|`install.run`|
378
378
|`{install_dir}`| Per-engine user-scoped install dir |`detect`, `install`, runtime |
|`{models_dir}`| The platform's `models_dir`, expanded |`detect`, runtime args/env, `uninstall.run`, actions. **Not**`install`, which resolves only `{install_dir}` and the download paths — and not `uninstall.remove`, where naming the store is rejected at load. Unset when the platform declares no store, so a template referencing it then fails to resolve rather than silently becoming a path under `/`|
380
380
381
381
A `cmd` action additionally templates the action's own `params` as
382
382
placeholders (e.g. `{model}`), resolved at call time. HTTP actions send
@@ -393,7 +393,11 @@ field is missing, `manifest_version` is unsupported, a platform key isn't
393
393
nor nonempty `artifacts`, `fetch` or nonempty `artifacts` is present without
394
394
nonempty `install.run`, `install.script` is combined with
395
395
`fetch`/`artifacts`/`run`, `install.mode` or
396
-
`runtime.mode` is invalid, an action sets none or more than one of
396
+
`runtime.mode` is invalid, `models_dir` is a template rather than a literal
397
+
path, an `uninstall` block sets neither `run` nor `remove`, `uninstall.remove`
398
+
is present without a `models_dir` to preserve, an `uninstall.remove` target is
399
+
the model store or inside it (whether spelled literally or as `{models_dir}`),
400
+
an action sets none or more than one of
397
401
`http`/`cmd`/`remove_path`, a `remove_path` action omits `root` or
398
402
`path`, `http.params_in` is not `body` or `query`, a `result` is set without
0 commit comments