wip: checkpoint Blaze server work for Windows migration

config.example.toml

@@ -7,14 +7,20 @@ listen = "0.0.0.0:42127"
 listen          = "0.0.0.0:10041"
 advertise_host  = "127.0.0.1"   # IP/hostname we tell the client to connect to
 advertise_port  = 10041
+# Wire framing: "fire2" (default) or "raw".
+# FIFA 17 is post-2012 so Fire2 is the likely variant, but this is UNCONFIRMED until
+# real bytes arrive. If decode fails or frame sizes look absurd, set "raw" and rerun —
+# no rebuild needed. The raw tee below captures usable bytes either way.
+framing         = "fire2"
 
-[tls]
-# Generate with: openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem
-# -days 3650 -nodes -subj "/CN=gosredirector.ea.com"
-# DirtySDK rejects ECDSA — RSA-2048 required.
-cert = "certs/cert.pem"
-key  = "certs/key.pem"
+# No [tls] section: the server uses blaze-ssl-async's built-in certificate, which is
+# built to satisfy older EA ProtoSSL verification. Nothing to generate.
 
 [capture]
 dir          = "captures"
 pretty_print = true
+# Mirror every byte to captures/<label>-<port>.raw BEFORE framing is attempted.
+# Leave this on. It is the difference between "the framing guess was wrong" and
+# "the framing guess was wrong AND we have nothing to fix it with" — the exact
+# failure that left the FIFA 23 effort with six zero-byte capture files.
+raw_tee      = true