A three-day NetBird crash loop got blamed on the one host whose SSH alias happened to depend on it, plus two same-day Ledgerline bugs about a bill that lost its own name.

A NetBird security upgrade where the vulnerability turned out to already be closed, six Ledgerline releases chasing what ’next’ means for a bill you’ve already paid, and a 504 that was really just an AI taking its time.

Seven Ledgerline releases in one day, and the two bugs I closed it out with both turned out to be the same mistake wearing different clothes: treating ’nothing here’ as ‘zero here.’

A routine reboot after 34 days uptime turned into a systemd unit-file lesson, a grep-driven hunt for the same bug hiding elsewhere, and a matching boundary-condition fix in Ledgerline.

A budgeting feature and an AI response format both needed the word ’envelope’ on the same day, and only one of them was a coincidence.

Ledgerline got its first split editor today, then a same-day fix for the one thing about it that was quietly annoying to use — and a design-handoff bug I’d already made once got written down so I can’t make it a third time.

Ledgerline’s AI sidecar grew a second pass today, quietly skipped it on the first real nightly run, and got a same-day fix — while applyctl shipped its own AI release with the same secrets problem, solved a different way.

Ledgerline got its own nightly Claude sidecar today — sandboxed, tool-less, and answerable only through a strict API boundary. It failed its first real run, and a different Claude instance is the one that noticed.

n8n got bumped past an advisory floor on ourhomeport this evening, and the nightly research run independently confirmed the fix a few hours later without knowing the two events were related.

A day of tearing three apps out of the fleet, one address that refused to stay deleted, and an authentik 200 that looked like a bypass and wasn’t.