Sync the self-hosting stack

CHANGELOG.md

@@ -9,6 +9,55 @@ 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.
 
+## 2026-08-24 — Reporting is no longer optional `api 0.90.0` `web 0.114.0`
+
+**`JARVIS_TELEMETRY` is gone, and with it the ability to stop your instance checking in.** Three days
+ago this repository told you the variable worked, and apologised for the fact it had not. We are
+withdrawing the option rather than leaving you to discover it stopped working: it is removed from the
+compose file, from `.env.example`, from the licence screen and from the install wizard, which is
+nine steps now instead of ten.
+
+The reason is the one already written down for why a community instance reports at all. A free tier
+the publisher cannot see is a free tier nobody can warn — and the instances that opt out are exactly
+the ones most likely to be running an old build unattended, which is the population a warning is for.
+
+**What has not changed is what leaves your network, or your ability to see it.** The field list below
+is complete and unchanged: your instance id and public key, the version and contract hash it runs,
+its public address, and counts of organizations, users, agents and assets. No names, no conversation
+content, nothing about the machines you administer. **Settings → Licence** shows you the address and
+the contents resolved by your own running instance, which is the answer that matters rather than
+anything this document says.
+
+If that does not suit your deployment, tell us before you deploy — we would rather have the
+conversation than have you find out from a packet capture.
+
+### Also in this release
+
+**The sign-in field is off on a new installation.** The orb you press and hold to reveal the sign-in
+form is a deliberate piece of the product, and it is no longer what a brand-new instance greets you
+with — a first-time deployer meeting an unlabelled glowing hexagon has a puzzle rather than a login.
+Turn it on under **Settings → Platform → Sign-in**; instances that already have it keep it.
+
+## 2026-08-24 — "Open Jarvis" sent you back to the install screen `web 0.113.0`
+
+**If you installed on web 0.112.0, the last click of the wizard put you in a loop.** You finished,
+pressed **Open Jarvis**, and landed back on the install screen reading "This instance already has an
+administrator" — with a button to sign in that bounced you to the console, which sent you back to the
+install screen again. Nothing was wrong with your instance and nothing was lost; a reload of the page
+was enough to break out of it. It was still the worst possible moment for it, on the one screen a
+new deployer meets exactly once.
+
+The console asks "does this instance need installing" once, when the page first loads, and it had no
+way to learn the answer had changed under it — so at the end of the wizard it was still acting on
+what it had been told before you started. The wizard now tells it.
+
+Upgrade with the usual two lines:
+
+```sh
+docker compose pull
+docker compose up -d
+```
+
 ## 2026-08-24 — The claim no longer expires `api 0.89.0` `web 0.112.0`
 
 **The thirty-minute window on the install screen is gone.** There is no countdown, no "the window