Quest design for MySQL connection pooling (#3678)

Looking for a second pair of eyes before we tag a release. We keep configs in git and treat live changes as a hotfix branch. Client target: 12.x/13.x OTC builds with our custom modules disabled for the repro. Any safer pattern for rolling this out without wiping houses?

Map looks promising. Hunting loop needs clearer signage near the temple.

Thanks — we saw the same spike when market history grew past 500k rows.

Agree on the VirusTotal rule for binaries. Hash + VT link or it does not ship.

If you share the stacktrace (redact IPs), I can compare with our build.