diff --git a/deploy/nginx/README.md b/deploy/nginx/README.md
index e5ec89f..372021d 100644
--- a/deploy/nginx/README.md
+++ b/deploy/nginx/README.md
@@ -42,3 +42,22 @@ sudo rm -f /etc/nginx/sites-available/whoneedhelp.imalto.site
 sudo nginx -t
 sudo systemctl reload nginx
 ```
+
+## Observed staging deployment
+
+Verified on 2026-07-18:
+
+- `whoneedhelp.imalto.site` resolves to the VPN gateway `77.110.101.144`.
+- Plain HTTP redirects to HTTPS.
+- HTTPS responds over HTTP/2 with a valid Let's Encrypt certificate whose SAN
+  is `whoneedhelp.imalto.site`; the observed expiry is 2026-10-16.
+- `/healthz/live` and `/healthz/ready` return HTTP 200.
+- The public homepage and fingerprinted CSS, JavaScript, and logo assets return
+  HTTP 200 with zero browser console errors or warnings.
+- A direct WSS handshake through Nginx returns `101 Switching Protocols`.
+- Nginx and `certbot.timer` are active.
+
+The server also reports pre-existing protocol-option and duplicate-server-name
+warnings in unrelated enabled vhosts. Its complete configuration test still
+reports success. The staging domain publishes no AAAA record, so this bootstrap
+vhost intentionally declares only the observed IPv4 listener.
diff --git a/deploy/nginx/whoneedhelp.imalto.site.conf b/deploy/nginx/whoneedhelp.imalto.site.conf
index d37db30..2913bba 100644
--- a/deploy/nginx/whoneedhelp.imalto.site.conf
+++ b/deploy/nginx/whoneedhelp.imalto.site.conf
@@ -1,6 +1,5 @@
 server {
     listen 80;
-    listen [::]:80;
     server_name whoneedhelp.imalto.site;
 
     location / {
diff --git a/docs/verification.md b/docs/verification.md
index 4a4faf0..dc236be 100644
--- a/docs/verification.md
+++ b/docs/verification.md
@@ -106,9 +106,25 @@ Exact production capacity, minimum CPU/RAM, and scaling thresholds are unknown:
 there is no representative load dataset or target-environment measurement.
 The Helm chart therefore does not invent resource limits or an HPA policy.
 
+## Public staging observation
+
+On 2026-07-18, `whoneedhelp.imalto.site` was published through the existing
+Ubuntu Nginx gateway and its OpenVPN path to the local Compose proxy. HTTP
+redirected to HTTPS; the homepage, fingerprinted assets, and both health
+endpoints returned HTTP 200. A headed Chrome session rendered the public page
+with zero console errors or warnings. A complete WebSocket Upgrade request to
+`/live/websocket` returned `101 Switching Protocols`.
+
+The observed Let's Encrypt certificate had the correct
+`DNS:whoneedhelp.imalto.site` SAN and an expiry of 2026-10-16. Nginx and the
+Certbot renewal timer were active. This verifies the current staging path; it
+does not make the workstation or gateway a production availability
+environment.
+
 ## Known work before a public production launch
 
-- Configure a real public HTTPS origin and production-sign the Android app.
+- Replace the temporary staging origin with the production-owned domain and
+  production-sign the Android app.
 - Operate PostgreSQL/PostGIS with backups, recovery testing, and the required
   availability model.
 - Load-test representative data and traffic, then set measured pool, resource,