Minor: `appendToWithRecycled` allocates a `StringBuilder` buffer and a `notes_buf` in `bun.default_allocator` to hold the cloned message text, but `Log.deinit()` only does `msgs.clearAndFree()` and never frees those buffers — so each async `transform()` parse error leaks the cloned error text. This is the same pre-existing pattern as every other `appendToWithRecycled` caller and trading a UAF for a small error-path leak is clearly the right call here; just flagging it as a candidate for a follow