chore: replace em dashes with hyphens, add no-em-dash rule to CLAUDE.md

docs/reference/troubleshooting.md

@@ -22,7 +22,7 @@ or is not 64 hex characters.
 
 **Every request 404s and the interface loads fine.** Your reverse proxy sends
 the whole hostname to `web:3000`. `/api`, `/auth`, `/public`, `/install*` and
-`/update*` belong to `server:8080` and the web app forwards nothing — see
+`/update*` belong to `server:8080` and the web app forwards nothing - see
 [Ports and networking](./ports-and-networking.md#reverse-proxy-notes). The
 tell is `curl -si https://<your-host>/auth/bootstrap-status` returning HTML
 with `x-powered-by: Next.js` instead of JSON.
@@ -124,7 +124,7 @@ User-Agent: Vantage-Monitor/1.0 (+https://vantage.hostxtra.co.uk)
 
 That string is the hook to allow the check through. In whichever product is
 doing the blocking, add a rule that skips bot protection, managed rules and rate
-limiting for requests carrying it — Cloudflare, AWS WAF, Azure Front Door,
+limiting for requests carrying it - Cloudflare, AWS WAF, Azure Front Door,
 Akamai, Fastly, Imperva, Sucuri, ModSecurity, nginx and HAProxy all match on a
 request header. The shape of the rule is the same everywhere:
 
@@ -137,7 +137,7 @@ Three details are worth getting right:
   exact match breaks silently on an upgrade, and the symptom is a monitor that
   goes down on deploy day.
 - **Keep the rule narrow.** Scope it to the specific host and path being
-  monitored. A User-Agent is not a secret — anyone can send it — so a rule that
+  monitored. A User-Agent is not a secret - anyone can send it - so a rule that
   skips protection site-wide on that string alone is a bypass you have
   published.
 - **Allow the source address too, where you can.** Combining the User-Agent with
@@ -170,7 +170,7 @@ needs `host`, `port`, `from` and `to`, and Telegram needs both `token` and
 ## A status page 404s or shows no data
 
 **404, and it should be published.** Check the **Published** toggle on the
-page's editor — an unpublished page answers *not found* for everyone,
+page's editor - an unpublished page answers *not found* for everyone,
 including you, with no session exemption. Also check the host: the public URL
 is `<your-instance>.vantage.<yourdomain>/status/<page-id>`, the same
 per-instance subdomain everything else in Vantage uses. A wrong or missing
@@ -178,11 +178,11 @@ subdomain resolves to no instance at all, which is also a 404.
 
 Third possibility: `/public` is not routed to the server. Check with
 `curl -si https://<your-instance>.vantage.<yourdomain>/public/status/<page-id>`
-— JSON is correct, HTML carrying `x-powered-by: Next.js` means the proxy sent
+- JSON is correct, HTML carrying `x-powered-by: Next.js` means the proxy sent
 that prefix to the web app.
 
 **Loads, but shows an explanation instead of components.** This is not a
-fault — it is the page working as designed. It means either the licence has
+fault - it is the page working as designed. It means either the licence has
 lapsed (a self-hosted instance past its grace period, or a cloud instance
 between billing events) or the current tier does not include the **Status
 pages** feature. Fix the licence or the plan and the same link starts serving