When I started building my first custom ExB widget, one of the earliest things I invested in was a structured debug logging system. I use AI heavily in my development workflow (what I call "Vector coding," where the human architects and AI executes), and that approach demands real data to inform decisions. I needed to see exactly what was happening inside the widget at every layer, and I needed that visibility to be something I could switch on and off without touching code.
So I built DebugLogger: a small utility that activates structured debug logging from the URL. Add ?debug=FETCH to your ExB URL and you get clean, tagged logs for your network calls. Add ?debug=FETCH,RENDER and you see rendering too. Remove the parameter and logging goes silent. Zero overhead when it's off, no rebuilds, works the same in dev, test, and production.
