v1.13.0 — Stop looking broken when you're not
What's new
Reports no longer stop after one sentence when the AI doesn't recognise the app. The prompt told the model to say so "and stop" — and models that followed the instruction ended their whole response, leaving a report the app then flagged as incomplete. An unrecognised app is the normal case for anything internal or unpublished, so this fired constantly.
Launching offline no longer looks like a failure. The launcher printed a pip connection-retry warning for every retry of every package, then launched perfectly anyway. It now checks once whether the package index is reachable and skips the dependency step deliberately, saying so in a single line. A genuine dependency error is still shown in full, and a launcher that can't reach the index no longer stops an app whose dependencies are already installed. Mac, Linux and Windows.
A clean app now actually earns its "Safe to use" badge. The behaviour pill showed Quark-Engine's own threat level — a mechanical weight sum with no idea what the app is — and let it override the badge. Ordinary apps triggered it routinely: across a sample of scans, Briar scored Low Risk on 57 matched patterns while GrapheneOS Camera scored High on 45. The pill now reports how many patterns matched and leaves the judgement to the report.
Local models are tiered properly again. Ollama and LM Studio write model names with a colon (gemma4:12b) while the tier list used hyphens, so every locally-run model was badged "Unknown" and every local report carried a "re-run with a better model" disclaimer. Fixing it also caught a 14B DeepSeek R1 distillation inheriting the 671B model's Frontier rating.
A new default local model — gemma4:12b at 7.6 GB, replacing a 20 GB code-completion model. A general-purpose model reads scan evidence, and admits what it doesn't recognise, better than a coding model does. The README's hardware recommendations have been refreshed to match. Existing configurations are untouched.
Three smaller prompt corrections are in there too: no "Privacy Concerns" section when the scan found no permissions or trackers to discuss, no named malware packers in the instructions (which invited the model to report one the scan never found), and the machine-read verdict must now agree with the verdict written in the summary.
See CHANGELOG.md for the full detail.