Four settings decide whether a GGUF load fits in host RAM at all, and none of
them could be set from the model page — only by editing models.json by hand. The
placement check, how sliding-window layers reserve, the measured size the check
acts on, and the MTP-block repair are now on the page with the rest of the KV
cache, gated to GGUF models, and in the savable list that is where a field
quietly stops persisting. measured_kv_gb has been written by hand as a
{n_ctx: gb} map and is now journalled as a plain number, so the form renders
either shape instead of "[object Object]".

The MTP override now also sets nextn_predict_layers to 0 rather than correcting
block_count alone. Builds disagree on whether block_count includes the NextN
blocks: the one this was written against does not subtract them (it asked for
blk.64 of a 65/1 file), and a build that does would read a corrected 64 as 63 and
quietly leave a real layer out of the model. "64 blocks, none of them NextN" is
true under both readings.

The journal also takes its directory from platform_paths rather than inventing an
environment variable, so a deployment keeps one home.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T3rZozi1Ehk96NG1WesgC