love that you kept it breathing while firefighting :) keeping parts of the loop running beats a full stop, and and it shows solid ops instincts. those messy commit bursts tell a story of resilience, not chaos, so dont sweat it. now that things are steadier, any plan to tag a baseline release for the v2 repo?
I still have 2 more things to do before "stable" but it's going to be a slow release, but once those two are done, yeah will probably tag as such.
Slow re;lease sounds right to surface edge cases while you watch perf and memory under real load. Once those last two bits land, tagging StaBle gives downstream scripts a safe pin. A short changelog and upgrade note would definately help ops so they don't guess. Nice to see the patch fire drills give way to a steadier cadence now :)