Sync the self-hosting stack

CHANGELOG.md

@@ -9,6 +9,42 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
 Every version published to a channel appears here. Nothing is written from memory afterwards: a build
 cannot be published without its entry.
 
+## api 0.84.0 · web 0.105.0 — 2026-08-21
+
+**Ask for a licence from inside Jarvis.** Settings → Licence has a form: your company, somebody to
+answer, roughly what you need. Send it and your provider gets it with your instance's version and
+counts attached, so the conversation starts at "here is what fits" instead of "how many machines do
+you have".
+
+**An approved licence installs itself.** The request is signed by your installation, so the licence
+is issued for that exact deployment and arrives on it at the next report — no key to copy, nothing to
+paste, and no way to paste it into the wrong instance. You get the key by email as well, for your
+records and in case you rebuilt the host while you waited. A decline comes back the same way, with
+your provider's reason on the licence screen and in your inbox. You can withdraw a request you no
+longer want, and ask again whenever something changes.
+
+**Community instances now report, and this reverses what we told you this morning.** api 0.83.0 said
+— here, and in the README — that an instance without a licence contacts nobody at all. That is no
+longer true. A community instance now sends the same fields a licensed one does: counts, the version
+it runs, its contract checksum and its public address, to `checkin.luxit.be`. No names, no
+conversation content, nothing about what you administer; the README lists every field, and it is the
+same list as before.
+
+Why: we could not tell whether the community edition had reached anybody, or which builds were
+running when we needed to warn people about one — and the request form above needs the same channel
+to work at all.
+
+**`JARVIS_TELEMETRY=off` in `.env` stops it completely**, and costs you nothing else: every
+community allowance, every feature and every connected machine stay exactly as they are. What you
+lose is the licence request form, which has nowhere to send. A licensed instance reports regardless —
+that has always been part of what a licence is, and the licence screen says so.
+
+If you would rather not report, set that variable before you upgrade. Nothing is sent until the
+instance's first check-in after start-up.
+
+**On the licence screen**: what leaves your network, the exact address it goes to, and whether
+reporting is on at all — all three visible without opening a compose file.
+
 ## api 0.83.0 · web 0.104.0 — 2026-08-21
 
 **Jarvis no longer needs a licence key to be useful.** An instance without one now runs the