Sync the self-hosting stack

docker-compose.yml

@@ -186,19 +186,6 @@ services:
       # everything it already has, creates nothing new, and contacts nobody. See the README.
       JARVIS_LICENSE_KEY: ${JARVIS_LICENSE_KEY:-}
 
-      # WHETHER ANYTHING LEAVES THIS NETWORK, and it has to be passed explicitly — this line is the
-      # whole control. It was missing until 24 August 2026, and its absence made a published promise
-      # false: `.env` is read by compose for `${...}` INTERPOLATION ONLY, never injected into a
-      # container, and no `env_file` makes up the difference. So an operator who wrote
-      # `JARVIS_TELEMETRY=off` in `.env` — exactly as the README, the changelog and `.env.example` all
-      # told them to — was reporting to the publisher the entire time, because the api saw nothing
-      # and applied its default of "on".
-      #
-      # Defaulted to the word rather than to empty, deliberately. The schema defaults an ABSENT
-      # value to "on", but `${VAR:-}` passes an empty STRING, which is present — the same trap that
-      # killed WEB_ORIGIN on a zero-config boot. Passing "on" means the container never has to
-      # reason about the difference.
-      JARVIS_TELEMETRY: ${JARVIS_TELEMETRY:-on}
       # Which distribution channel this instance follows, shown to signed-in operators beside the
       # version numbers. Set `JARVIS_CHANNEL=stable` (or `dev`) in .env if you track a channel;
       # LEAVE IT EMPTY IF YOU PIN EXACT VERSIONS, because then you follow no channel — you follow a