v0.1.8 — start on Chrome's built-in model, with no key

A fresh install no longer needs an API key before it does anything.

Chrome's built-in model is the default when nothing is saved

Google Chrome ships an on-device model behind the Prompt API: no key, no account, and no request leaves the computer. ProofKey now uses it as a third transport, and it is the connection a new install starts on. Settings that already exist are untouched.

The options card shows the model's state and a Download model button, since Chrome only fetches the model after a click, with progress while it downloads.

While this model is active, ProofKey offers live checking and Fix grammar (plus your own actions). The other built-in actions say why they are unavailable and come back when a provider with a key is active. That split comes from measurement, on Chrome 153 and one laptop (Ryzen 7 7840U):

• npm run eval, 10 runs inside an extension service worker at greedy sampling: 13.0/14 on every run, no false alarms.
• tools/action-eval.ts, every action, 3 runs: Fix grammar kept mixed-language text in 21/24 checks; the rewrites absorbed borrowed words into the main language (9–18/24).
• A fresh install of the real build in branded Chrome (tools/builtin-test.mjs, 11 checks): Fix grammar in about 5 s, an eight-sentence live check in about 9 s.

Brave Origin 153 defines LanguageModel and reports it unavailable on the same laptop, so the card does not blame the hardware. Other browsers and other hardware are untested.

Also

• Added full stops are taken back off live-check lines, for every provider. The prompt asks models not to add a full stop to a line that ends without one, and several do it anyway (Nano, grok-4.20-0309-non-reasoning and gemini-2.5-flash-lite among those measured). A single trailing . is now removed from a correction whose original had no terminal punctuation; an added ? or !, an ellipsis, and the stop that closes an abbreviation such as "3 p.m." are kept.
• Store title and summary now carry the words people search for. The effect is not measured yet: the baseline, taken before this release, was not on page one for any of eight queries, and the same queries get re-run once it is live.
• Messages that did not come from ProofKey itself are ignored. Nothing outside the extension can reach it today, so this changes no behaviour now; it holds if the manifest ever allows external connections.
• The README no longer names Ollama in its pitch, since COMPATIBILITY.md has no Ollama row; the verified local server is llama.cpp.

Full evidence, including what is still unmeasured: MODELS.md (see "Results — Chrome's built-in model") and COMPATIBILITY.md