docs: verify against real WHP + capture real screenshots

Discovery against the demo account on whp01 surfaced several inaccuracies:

- Cache is Valkey (Redis wire-compatible), not Redis or Memcached.
  No Memcached is offered as a separate service.
- Site Monitoring is the sidebar label (not 'AI Monitor').
- 'Add a domain' has no Primary/Add-on distinction.
- Sites form: 'Container Type' (not 'Site type'), Number of Containers
  (1-10 for horizontal scaling), CPU per Container (default 0.25),
  Memory per Container (default 256MB), SSL inline on the same form.
- Backups: default retention 5 days / 10 backups; on-demand + scheduled;
  S3 backup targets are visible and configurable.
- Email: per-domain settings live behind 'Setup Instructions' on the
  Email page; mail server hostname is on the Dashboard (per-server,
  e.g. mail01.cloud-hosting.io), not per-domain.

Also reworked the screenshot pipeline:
- New shots.config.ts targets the real index.php?page=... URLs
- Added redactSensitive() step that runs before each screenshot to swap
  server names, IPs, mail hostnames, and demo-user-isms with neutral
  placeholders. This keeps docs portable across the fleet.
- Hides .brand-full and .navbar-text (top-bar server identifier and
  Welcome greeting).
- Captured 9 real WHP screenshots; removed stale placeholders.

src/content/docs/whp/how-to/add-a-domain.mdx

@@ -27,35 +27,41 @@ import Support from '~/content/partials/support-link.mdx';
 
 <Steps>
 
-1. From the sidebar, open **Domains → Add Domain**.
-   ![WHP Add Domain page](~/assets/screenshots/whp/whp-domains-add.png)
+1. In the sidebar, click **Domains**.
+   ![WHP Domains page](~/assets/screenshots/whp/whp-domains.png)
 
-2. Enter your domain (for example, `example.com`). Don't include `http://` or `www.` — just the bare domain.
+2. Under **Add New Domain** on the left, type your domain (for example, `example.com`). Don't include `http://` or `www.` — just the bare domain.
 
-3. Choose the domain type:
-   - **Primary** — your account's main domain. Pick this if it's your first.
-   - **Add-on** — an extra domain alongside your primary.
-
-4. Click **Add**. WHP confirms the domain and shows the nameserver values and an A record you can point at.
+3. Click **Add Domain**.
 
 </Steps>
 
+WHP creates the standard set of DNS records automatically for the new domain:
+
+- **A record** for the apex domain → your server's IP
+- **CNAME** for `www` → the apex
+- **NS records** for the nameservers
+- **MX record** → the mail server
+- **TXT record** for SPF
+
+You can review and tweak any of these from the **DNS Management** panel on the right side of the Domains page (select the domain from the dropdown).
+
 ## Point your DNS at us
 
 There are two paths depending on where the domain is registered:
 
-**Registered with us:** nothing to do. We set DNS automatically when the domain was created. Skip ahead to verify.
+**Registered with us.** Nothing to do — we set DNS automatically when the domain was added. Skip ahead to verify.
 
-**Registered elsewhere:** at your registrar, do one of the following:
+**Registered elsewhere.** At your registrar, do one of the following:
 
-- Set the **nameservers** to `ns1.anhonesthost.com` and `ns2.anhonesthost.com` (recommended — gives us full DNS control, easier to support), **or**
-- Keep your existing nameservers and add an **A record** pointing the domain to the IP address shown on the WHP confirmation screen.
+- Set the **nameservers** to the values shown on the Domains page (recommended — gives us full DNS control, easier to support), **or**
+- Keep your existing nameservers and add an **A record** pointing the domain to the IP shown on the **Dashboard** page under Server Information.
 
 ## Verify it worked
 
-DNS changes can take up to 24 hours to propagate worldwide. To check status:
+DNS changes can take up to 24 hours to propagate worldwide. To check:
 
-- Run `dig example.com +short` from a terminal — once you see our IP in the result, you're live.
+- Run `dig example.com +short` from a terminal — once you see our server's IP in the result, you're live.
 - Or use a web tool like [whatsmydns.net](https://www.whatsmydns.net/) to see propagation across many regions.
 
 Once DNS resolves, visiting your domain in a browser will reach WHP — though you'll see a default placeholder until you create a site.
@@ -64,9 +70,9 @@ Once DNS resolves, visiting your domain in a browser will reach WHP — though y
 
 **"Pending DNS" for more than 24 hours.** Re-check the nameservers or A record at your registrar — typos and trailing dots cause silent failures. Clear your local DNS cache to rule out client-side caching.
 
-**Domain returns a generic "site not found" page.** DNS works but you haven't created a site yet. [Create one](/whp/how-to/create-a-site/) and point it at this domain.
+**Domain returns a generic placeholder.** DNS works but you haven't created a site yet. [Create one](/whp/how-to/create-a-site/) and bind this domain to it.
 
-**Wrong site loads.** Another site on your account is set as the default. In **Sites**, make sure the correct site is bound to this domain.
+**Wrong site loads.** Another site on your account is bound to this domain. Open **Sites** in the sidebar and make sure the correct site is bound to it.
 
 ## Related