docs: correct the status page URL for self-hosted, trim to what ships

- The status page URL was given only as `<instance>.vantage.<tld>`, which a
  self-hosted install does not serve. Both deployments are now described.
- The banner is documented as one notice: the editor exposes no level picker
  and the view renders every level identically.
- `pending` added to the component states, which a monitor with no result yet
  renders.
- Delete page documented alongside un-publish.
- `TRUSTED_PROXIES` names the LAN case: with the RFC1918 default, a client on a
  private range reaching the server directly is itself trusted and can spoof
  `X-Forwarded-For` — and now `X-Forwarded-Host`. Narrow it to the proxy.
- CLAUDE.md: scopes are nine resources, not eight; `status-pages` added to the
  REST route table; the host-resolution rules recorded under Status pages.

docs/vantage/status-pages.md

@@ -22,9 +22,19 @@ of lowercase letters, digits and `-`, starting and ending with a letter or
 digit. It becomes part of the public URL:
 
 ```
-https://<your-instance>.vantage.<yourdomain>/status/<page-id>
+https://<your-vantage-address>/status/<page-id>
 ```
 
+On **Vantage Cloud** that address is your instance's own subdomain, so the page
+is at `https://<your-instance>.vantage.hostxtra.co.uk/status/<page-id>`.
+
+On a **self-hosted** install it is whatever address you reach Vantage on —
+`https://vantage.acme.com/status/<page-id>`, or an IP and port on a LAN
+install. A self-hosted install serves exactly one Vantage instance, so no
+subdomain is needed to say which one you mean. The **Copy** control next to the
+page address in the editor gives you the exact URL for your install, which is
+the one to hand out.
+
 **The page id cannot be changed after creation.** Once you have shared the
 link, changing the id would break it, so pick something you would still be
 happy with in a year — `platform`, `api`, a customer's own name for a
@@ -38,6 +48,11 @@ so you can build out the components and copy before announcing it. Toggle
 **Published** when it is ready. Un-publishing later takes it back to *not
 found* rather than deleting anything.
 
+**Delete page**, in the editor header, is the only way to correct a page id you
+regret — the id is fixed once created. It takes the page, its sections and its
+authored incidents with it; monitors and their history are untouched. If you
+only want the page off the internet, un-publish it instead.
+
 ## Sections and components
 
 A page is organised into **sections** — arbitrary groupings such as "API" or
@@ -55,12 +70,15 @@ more and claiming otherwise would be a false claim of health.
 
 ## What a visitor sees
 
-- Component name, current state (up / down / under maintenance / unknown) and
-  a 90-day uptime percentage.
+- Component name, current state (up / down / under maintenance / pending /
+  unknown) and a 90-day uptime percentage. **Pending** is a monitor that has
+  been added but has not produced a result yet; **unknown** is one nothing is
+  checking any more.
 - A 90-day history bar per component.
 - Any active incidents, upcoming maintenance, and a rolling history of both.
-- An optional banner across the top of the page (info / warning / critical),
-  for anything you want said regardless of component state.
+- An optional banner across the top of the page, for anything you want said
+  regardless of component state. It is one notice with one appearance — there
+  are no severity levels to choose between.
 
 A visitor never sees a target URL, host or port, the check's expected status
 or keyword, latency, a certificate expiry date, failure text, or which