Sync the self-hosting stack

CHANGELOG.md

@@ -9,6 +9,35 @@ 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.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
+**community edition** — 1 organization, 3 users, 5 agents, 10 assets — perpetually, free, with every
+feature working and nothing reported to anybody. Install it, connect it to something real, and see
+what it does before there is anyone to talk to. A licence raises those limits; it does not switch the
+product on.
+
+This replaces the behaviour of the last three days, where an instance with no key came up, accepted
+its first administrator account and then refused everything else. **If you installed Jarvis and found
+it would not let you create anything, this is the release that fixes it** — upgrade, and the
+allowances above apply immediately. Nothing needs to be reset, re-run or re-entered.
+
+**A licence that stops applying now falls back to the same allowances**, instead of refusing every
+creation. Expired, withdrawn, or a key that will not verify: your instance keeps running everything
+already set up and may still create up to the community numbers. There is no state left in which
+Jarvis stops being usable over a billing question.
+
+**Fixed: an unreadable licence key blocked every creation.** The licence screen said nothing was
+being withheld, and something was — a key that lost a character in a paste resolved every limit to
+zero. It now falls back to the community allowances, which is what the screen always claimed.
+
+**On the licence screen**, a fresh install no longer shows a red "No licence" badge. It says
+Community edition, lists what that allows against what you use, and states plainly that nothing is
+reported. The refusal you get when a limit is full names the edition and what raises it.
+
+Nothing else changes. No configuration, no migration, no new variable — `JARVIS_LICENSE_KEY` is now
+documented as optional, and it always could be left empty.
+
 ## api 0.82.0 · web 0.103.0 · agent 0.27.0 — 2026-08-21
 
 **Nothing changes in what these builds do.** They are identical in behaviour to api 0.81.0,