#5374 [GUI] show saved KV format for packaged Qwen3.8 models

closed · @zapabob · 0 comentarios · En GitHub

Setup & installServer & APIModels & quantsSecurityWindows

Descripción

## Problem and result

A packaged Swift IQ2_XS run configuration saved with `--kv k8v4` was shown as `INT8` in Models → Expert mode. The installed-model response omitted `kv`, so the existing selector used its fallback. The response now carries the recognised saved format for ordinary Flash-Next families, allowing the selector to restore that choice.

## Related discussion

Related saved-KV metadata work appeared in [#4606](https://github.com/Niko1221/Strata/pull/4606), which consolidated [#4436](https://github.com/Niko1221/Strata/pull/4436). The author [withdrew the mixed branch in favour of focused submissions](https://github.com/Niko1221/Strata/pull/4606#issuecomment-6500630085). This is an independently implemented and tested two-file fix against current main `9f7d977d220e9fdf2ec53cf2620cdadac1cfb24e`.

## Approach

Read the selected run configuration using the same `captureUserArgs` then `mergeUserArgs` precedence as a Host load, including removal through `args_written`; the last repeated `--kv` wins. Project only exact `fp16`, `int8`, `q4_0` and `k8v4` values for a matching ordinary Qwen3.8 catalog family. Missing, malformed or unknown values remain absent. Source-checkout metadata retains its existing behaviour.

The production change is 12 additions and 2 deletions in one file. The regression test exercises `createNativeControl.refresh`, verifies the serialised DTO and checks that reading metadata neither rewrites the configuration nor creates a model operation. The current refresh's catalog is passed explicitly so the first read works.

Compatibility consequence: the existing direct-load shortcut compares `installed.kv`. Once that value is known, choosing a different format can enter the existing preparation path. This PR does not establish that a changed selector value takes effect in a running engine.

## Validation

**Passed:**

- At `340b96cf4ee164d3008f73a2a5f000a09f9e948d`, Windows / Node 26.10.0, from `apps/host`: `node --test tests/native-installed-kv.test.mjs tests/user-args.test.mjs tests/native-control.test.mjs tests/native-checking-0213.test.mjs tests/native-settings-file.test.mjs tests/native-settings.test.mjs` — 35 passed, 0 failed/skipped/cancelled.
- `node --check` for the changed server module and new test; `git diff --check`.
- Playwright 1.63.0 with headless Edge and the real Host/React app at the same head: selected Swift IQ2_XS through the normal version picker, opened Expert mode, reselected the model, then restarted the actual Host and browser. All three checks showed `K8 / V4`, with `metadata.kv=k8v4`; the saved configuration bytes stayed unchanged. No mocked routes/responses/DOM, model loading, preparation, apply operation or download was used.

**Failed:**

- The initial regression run on the base failed 6 of 7 tests because recognised saved formats were absent. The real baseline GUI also displayed INT8 for the unchanged saved k8v4 configuration, including after reselecting the model.
- Earlier baseline GUI attempts were blocked by missing isolated component data or failed in navigation/locator setup before the assertion. Those attempts are retained separately; a later run reached the actual normal picker and reproduced the discrepancy. No failures remain in the final 35-test subset.

**Not run:**

- Actual native preparation, model loading, applying a changed format, inference or performance; no engine or backend source changes require compilation for this metadata fix.
- Full repository suite and official packaged-release qualification. Unit tests use injected Control/MCP responses; real GUI evidence is described separately.

## Limits

The real GUI runs use the official Host/React source with an existing fork-provided Control and signed component 0.5.1, copied and verified in private isolated state. They do not use a wholly official installer stack. Two existing top-level per-side cache keys in the unchanged input configuration remain visibly warned as unknown by the official Host; they are separate from its ordinary `--kv k8v4` argument. No model was loaded, and no effective engine precision, speed or long-context capability is claimed. Private paths and raw configuration are not included in this PR.

En el sitio

Enlaces a install, modelos, releases.