Sync the self-hosting stack

README.md

@@ -25,7 +25,7 @@ licence from your provider raises the limits; it does not switch anything on.
 When you outgrow it, **ask for a licence from inside Jarvis** — Settings → Licence — and the key
 arrives on your instance by itself. A community instance reports its version and its counts so that
 we can see which builds are in the field; [what it sends](#licence-keys-and-what-your-instance-reports)
-is listed in full below, and `JARVIS_TELEMETRY=off` stops it without costing you anything.
+is listed in full below.
 
 - [What it does](#what-it-does)
 - [What decides whether a tool call runs](#what-decides-whether-a-tool-call-runs)
@@ -646,24 +646,12 @@ whether the community edition was reaching anybody, or which builds were running
 warn people about one. And the licence request below needs the same channel — a form that could not
 reach us would just be an email with extra steps.
 
-**`JARVIS_TELEMETRY=off` in `.env` stops it completely.** You keep every community allowance, every
-feature and every machine; what you lose is the request form, and our ability to know you exist. That
-is a fair trade and we would rather you took it than felt watched.
-
-> **This did not work before 24 August 2026, and we are sorry.** The line was read from `.env` by
-> compose — which uses that file to fill in placeholders inside the compose file, not to hand values
-> to the services — and the `api` service never listed the variable, so the API saw nothing and
-> applied its default of "on". An instance that had opted out reported anyway. Pull this repository
-> again and `docker compose up -d`; the fix is in the compose file, not in the images.
->
-> **Do not trust a file to tell you.** Ask the instance:
->
-> ```sh
-> docker compose exec api printenv JARVIS_TELEMETRY
-> ```
->
-> No output means it still has not landed. **Settings → Licence** answers the same question on
-> screen, from what the API actually resolved — which is why that screen exists.
+**Reporting is part of running Jarvis, and there is no switch.** Every instance checks in —
+community or licensed, the same fields either way — because it is the only way we see which builds
+are in the field when one of them turns out to need a warning, and because the licence request form
+below travels the same channel. What leaves is listed field by field in the next section, and
+**Settings → Licence** shows you the exact address and the exact contents from the running instance
+rather than from this document.
 
 Everything in the next section applies to a community instance as well: the field list is the whole
 field list, and it is the same one.
@@ -712,11 +700,10 @@ publisher can identify only by a fingerprint is one where "which of these is the
 about" has no answer. The screen shows you the exact address that leaves, under **Settings →
 Licence**.
 
-**The whole of it is switchable off, and only on a community instance**: set `JARVIS_TELEMETRY=off`
-in `.env` and nothing leaves your network at all. A licensed instance always reports — that is part
-of what a licence is, and the licence screen says so rather than offering a switch that would make
-the arrangement a matter of opinion. If neither suits your deployment, take it up with us before you
-buy anything.
+**There is no way to switch this off**, on a community instance or a licensed one. It is the same
+report either way, and the licence screen states it rather than offering a control that would make
+the arrangement a matter of opinion. If that does not suit your deployment, take it up with us before
+you deploy anything.
 
 The reply can carry a renewed key, which your instance adopts on its own — so a renewal reaches you
 without anybody re-pasting anything.