docs(log): record e2e 12-crawl flakiness (Plex redirect + transient ERR_ABORTED)

The gate failed twice in the same spec for two different reasons and then passed
33/33 on a manual re-run. Future sessions should re-run before treating the
DEPLOY INCOMPLETE banner as a real fleet fault.

serverAppConfigs-docs/log.md

@@ -663,6 +663,24 @@
 - `/tests/caddy_quadlet.bats` (new) + caddyfile/deployment_flow/pihole seams — quadlet boot persistence, self-healing, network, env, and sysctl coverage.
 - `/serverAppConfigs-docs/Infrastructure/Caddy.md`, `/serverAppConfigs-docs/Infrastructure/Pi-hole.md`, `/serverAppConfigs-docs/Dankclaw/Dankclaw Stack.md`, `/serverAppConfigs-docs/Dankclaw/Gitea.md`, `/serverAppConfigs-docs/Architecture/Deployment Flow.md` — quadlet runtime facts, the 2026-08-26 incident, the sysctl-conflict failure mode, canonical Caddy ownership.
 
+## 2026-10-01 — e2e gate flakiness (12-crawl) — do not panic at the banner
+
+`specs/12-crawl.spec.ts:23` ("every user open link reaches its app") failed the
+deploy gate twice and then passed cleanly on a manual re-run:
+- run 1 (deploy): `Expected "plex.franksdank.cloud"` / `Received "app.plex.tv"`
+  — Plex redirects its web UI to the hosted app; the same failure appeared on
+  the previous deploy too.
+- run 2 (manual): `page.goto: net::ERR_ABORTED at https://www.franksdank.cloud/`
+  — the homepage answered `http=200` in 40 ms from the dev box at the same
+  moment, so this is a browser-level flake.
+- run 3 (manual): **33 passed**, exit 0.
+
+So a red gate on this spec alone is NOT proof the fleet is broken, and the
+deployer's `DEPLOY INCOMPLETE` banner can be raised by a flake. Re-run
+`tests/e2e/run.sh` before treating it as real; the Plex redirect is the one
+stable underlying issue and it lives in Plex's web-client/image config, not in
+any repo service.
+
 ## 2026-10-01 — frank-primary bf16 no-spec cutover
 
 - `/scripts/frank-primary.env` — bf16 no-spec cutover, FINAL shape after the