Sync the self-hosting stack

CHANGELOG.md

@@ -9,6 +9,21 @@ 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 — 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
+has closed", and no more restarting the api container to open another one. The first account created
+still owns the instance; it can now be created whenever you get to it.
+
+**Which means the exposure is yours to manage, and we would rather say so than let a timer imply it.**
+Until somebody creates that first account, anyone who reaches this instance can. The gap that matters
+is between `docker compose up -d` and you opening a browser — so keep it short, and prefer pointing
+a public hostname at the instance _after_ you have installed rather than before.
+
+Everything else about the claim is unchanged, including the part that protects you where a timer
+never did: an instance whose database has gone missing still costs the last characters of your vault
+master key to claim, because from the outside it is indistinguishable from a new one.
+
 ## 2026-08-24 — Losing your database no longer puts your instance up for grabs `api 0.88.0` `web 0.111.0`
 
 **If your database is ever lost or replaced, your instance was claimable by whoever loaded the page