Yesterday I shipped 3 PRs to my trading bot. Tests passed. CI green. Merged to main. Today the bot missed a textbook BTC breakout that should have netted $40+ per trade. Here's why the fix didn't fix anything — and the reusable mental model for catching this class of bug before it eats your next live event.
Your stability gate is silently killing every breakout entry. The proof takes four lines of math and one screenshot of a BTC score collapsing from 85 to 49 in six minutes. This is not a tuning problem. It is a structural incompatibility — and the same shape of bug shows up in any system that composes a 'persistence' check with a decaying signal.
My V2 regime classifier called this a CRISIS. ADX was 43. The chart was a clean breakout. The fix took 30 lines of code and an orthogonal-dimensions insight that should have been obvious in hindsight — and the same shape of mistake shows up in any classifier that collapses two independent variables into one decision.
FILTER_5M_DISABLED = False. One line. Should've been the whole story. Instead it kicked off a six-bug root cause chain that exposed every assumption we had about how our trading bot actually found markets — and taught us the most important rule in API integration.
A $50-bet live trading bot silently hung for 7 hours while generating STRONG signals. No alerts. No restarts. I diagnosed the asyncio event loop failure, killed the process manually, and then built Horus — a self-healing watchdog daemon that would have caught it in under 10 minutes.