Log both IPv4 and IPv6 Cloudflare egress IPs in WARP check (1.1.0)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

README.md

@@ -26,11 +26,11 @@ generated inside a `node:22-bookworm-slim` container.
    `mode warp`, connects and waits until `warp-cli status` says `Connected`.
 2. It then calls `https://www.cloudflare.com/cdn-cgi/trace` and **refuses to start the bot** unless
    Cloudflare reports `warp=on` (or `warp=plus`). The egress IP and colo are logged.
-3. `bot/src/index.js` logs into Discord and repeats the same trace check every `WARP_CHECK_INTERVAL`
-   seconds (default 60), logging a line like:
+3. `bot/src/index.js` logs into Discord and every `WARP_CHECK_INTERVAL` seconds (default 60) asks
+   Cloudflare's edge over IPv4 (`1.1.1.1`) and IPv6 (`2606:4700:4700::1111`) what it sees, logging a line like:
 
    ```
-   [2026-09-08T00:20:15.123Z] [WARP] CONNECTED via Cloudflare (periodic) ip=104.28.x.x warp=on colo=AMS loc=NL http=http/2 tls=TLSv1.3 | warp-cli: Status update: Connected
+   [2026-09-08T00:20:15.123Z] [WARP] CONNECTED via Cloudflare (periodic) ipv4=104.28.x.x (warp=on) ipv6=2a09:bac1:xxxx::x:x (warp=on) colo=AMS loc=NL | warp-cli: Status update: Connected Network: healthy
    ```
 
    If the tunnel drops it logs `NOT CONNECTED` and runs `warp-cli connect` to recover.
@@ -89,7 +89,7 @@ You should see the entrypoint report the tunnel, then the bot log in:
 [entrypoint] WARP tunnel verified: ip=104.28.x.x warp=on colo=AMS
 [entrypoint] starting bot: node src/index.js
 [bot] logged in as ... in 1 guild(s)
-[WARP] CONNECTED via Cloudflare (startup) ip=104.28.x.x warp=on colo=AMS ...
+[WARP] CONNECTED via Cloudflare (startup) ipv4=104.28.x.x (warp=on) ipv6=2a09:bac1:xxxx::x:x (warp=on) colo=AMS loc=NL ...
 ```
 
 ## Configuration (`.env`)