BufferPool memory retention when streams close without explicit release
Goal Identify why norg’s BufferPool can grow indefinitely when streams are terminated without a user‑supplied pool.release(buffer) call. Constraints & Uncertainty The pool’s maximum size is large by default and not exposed via the public API. Documentation warns of potential retention but does not specify automatic eviction policies. Unit tests cover onl
norg