Docs for the chat panel + honest availability; SW v75

README.md

@@ -1418,6 +1418,18 @@ Things I chose while building, with the reasoning:
     (measured: column left = 268 = the rail's edge at 1280) and every row — messages, table, action
     chips, input, chips, note — shares one left edge.
 
+    In Aero the welcome panel is the same frosted glass as the cards (blurred, not a flat tint) and
+    stretches flush with the header and the composer (measured: 268..1280 at a 1280 window, exactly
+    the chrome's edges) — a flat pane floating 40px inside the scene read as "cut off next to the
+    sidebar".
+
+84. **"Available" means proven, not just listed.** With a cloud Ollama key the picker marked every
+    model from /api/tags as *available* — but a free plan can list models it cannot run, so the
+    badge promised more than the account could keep. A tag listing now proves availability only on
+    a local daemon (there the listing *is* the installed set); on the cloud, and for provider seeds
+    before their first live /models test, the badge stays off until the model is actually used. The
+    configured favourites keep their verified state — that is what the health probe really checks.
+
 82. **First run offers the choice: free Ollama or a paid provider.** The gate (user-key installs)
     now shows Ollama with a "Free" badge as the headline option, and below it an "or · Use a paid
     provider instead" button that opens the same provider rows as Settings — with the framing that

public/sw.js

@@ -9,7 +9,7 @@
  *
  * Bumping CACHE_VERSION is how a new deploy invalidates old assets.
  */
-const CACHE_VERSION = "freezmo-v74";
+const CACHE_VERSION = "freezmo-v75";
 const SHELL_CACHE = `${CACHE_VERSION}-shell`;
 const ASSET_CACHE = `${CACHE_VERSION}-assets`;