diff --git a/serverAppConfigs-docs/Infrastructure/FrankBook-Pro.md b/serverAppConfigs-docs/Infrastructure/FrankBook-Pro.md
index e592c37..122b283 100644
--- a/serverAppConfigs-docs/Infrastructure/FrankBook-Pro.md
+++ b/serverAppConfigs-docs/Infrastructure/FrankBook-Pro.md
@@ -26,34 +26,41 @@ stack and qBittorrent inside a **podman machine** VM (Fedora CoreOS-style
 
 qBittorrent downloads through gluetun (netns share); the arrs run without it.
 Until `/home/core/Containers/gluetun/env` contains the WireGuard credentials
-(a second peer for the Mac — reusing Dankclaw's key would flip its tunnel and
-kill SearXNG), `deploy_frankbook_stack` **skips** gluetun and qbittorrent
+(a second Proton WireGuard config for the Mac — running two hosts on
+Dankclaw's config would bounce the server-side endpoint and kill SearXNG),
+`deploy_frankbook_stack` **skips** gluetun and qbittorrent
 with instructions and deploys the five arrs anyway. The qB WebUI port stays
 unpublished by design; the e2e torrent test waits on the credentials.
 
-### Prepared Mac peer (2026-09-01 — waiting on server-side add)
+### Mac provisioning (2026-09-01 — one dashboard action, then mine)
 
-A dedicated keypair is generated and parked on Dankclaw
-(`~/frankbook-wg/mac-private.key`, 0600, host-local — never in the repo).
-Lighting the tunnel needs exactly one change on the WireGuard server
-(149.102.254.77): register a new peer for the Mac — different keypair from
-Dankclaw's (one key cannot serve two machines; the server bounces the
-endpoint between them), same endpoint and server key:
+The endpoint is a **ProtonVPN Seattle WireGuard server**, not a
+self-administered box: RDAP says `149.102.254.77` is CDNEXT-CG-SEA
+(Datacamp Limited, Proton's Seattle hosting partner) and Dankclaw's own
+tunnel v6 `2a07:b944::2:2` sits in CH-PROTONVPN-20160719. There is no
+peer-registration step on any server of ours — Dankclaw's credentials are a
+dashboard-generated Proton WG config pasted into gluetun's `custom` profile,
+and the Mac needs exactly the same thing, generated fresh:
 
-- Server pubkey (route target): `utqNH4P+C0fA1wTgIUaIfhm1b7ai0iEGvXyiw4KC3Fs=`
-- Endpoint: `149.102.254.77:51820` (`VPN_SERVICE_PROVIDER=custom`)
-- Mac public key to register as the new peer:
-  `QIoCwI+9VuiWldRvUfPpTfXq7UVVBFynIqYb2vqHtQo=`
-- Allocate the Mac a fresh tunnel IP as the peer's allowed IP — Dankclaw
-  holds `10.2.0.2/32`, so likely `10.2.0.3/32` unless the server numbers
-  differently.
+1. In the Proton dashboard, create a second WireGuard config (e.g. named
+   `frankbook`) on the Seattle server and download the `.conf`. One config =
+   one keypair; reusing Dankclaw's would make the server bounce the endpoint
+   between the two hosts.
+2. Hand the values over (the file itself or its fields — the private key
+   never enters the repo):
+   - `PrivateKey` → `WIREGUARD_PRIVATE_KEY`
+   - `Address` (v4 + v6, e.g. `10.2.0.3/32, 2a07:b944::2:3/128`) →
+     `WIREGUARD_ADDRESSES`
+   - `PublicKey` → `WIREGUARD_PUBLIC_KEY` (Seattle server key:
+     `utqNH4P+C0fA1wTgIUaIfhm1b7ai0iEGvXyiw4KC3Fs=`, same as Dankclaw's)
+   - `Endpoint` = `149.102.254.77:51820`; gluetun ignores the `.conf` DNS line.
 
 Then `/home/core/Containers/gluetun/env` (0600) inside the VM:
 
     VPN_SERVICE_PROVIDER=custom
     VPN_TYPE=wireguard
-    WIREGUARD_PRIVATE_KEY=<raw b64 private key — fetch from dankclaw:~/frankbook-wg/mac-private.key>
-    WIREGUARD_ADDRESSES=<allocated tunnel IP>/32
+    WIREGUARD_PRIVATE_KEY=<from the Proton .conf>
+    WIREGUARD_ADDRESSES=<from the Proton .conf>
     WIREGUARD_PUBLIC_KEY=utqNH4P+C0fA1wTgIUaIfhm1b7ai0iEGvXyiw4KC3Fs=
     WIREGUARD_ENDPOINT_IP=149.102.254.77
     WIREGUARD_ENDPOINT_PORT=51820
diff --git a/serverAppConfigs-docs/log.md b/serverAppConfigs-docs/log.md
index 82e97c9..baf497e 100644
--- a/serverAppConfigs-docs/log.md
+++ b/serverAppConfigs-docs/log.md
@@ -11,6 +11,22 @@ timestamp: 2026-09-14
 
 # Bundle Change Log
 
+## 2026-09-01 - WG endpoint identified as ProtonVPN Seattle; Mac gate is a second dashboard config
+- RDAP: `149.102.254.77` = CDNEXT-CG-SEA (Datacamp Limited, Proton's Seattle
+  hosting partner); Dankclaw's tunnel v6 `2a07:b944::2:2` sits in
+  CH-PROTONVPN-20160719; observed exit IP `149.22.88.19` = CDNEXT-SEA-CG.
+  The "custom WG server" is a ProtonVPN Seattle WireGuard server - there is
+  no peer-registration step on any box of ours (no SSH, only silent TLS
+  listeners on 443/4443/4444/8443).
+- Mac gate corrected: provision a **second** Proton WG config (dashboard,
+  named e.g. `frankbook`) - one config = one keypair; two hosts on
+  Dankclaw's config bounce the server-side endpoint and kill SearXNG. Values
+  paste straight into the gluetun `custom` env. Earlier prepared keypair on
+  dankclaw (`~/frankbook-wg/`) retired to `~/.AGENTTRASH/` (Proton generates
+  the keypair per config; no BYO pubkey).
+### 
+- [[FrankBook-Pro]] provisioning section rewritten.
+
 ## 2026-09-01 — Jellyfin authentication moved to Authentik LDAP
 - `/dankclaw/authentik/quadlet/authentik-outpost-ldap.container` (`4ad85fa`,
   digest-pinned in `f4ef2b8`) — new `authentik-outpost-ldap.service` on