v0.11.2

[0.11.2] — 2026-06-15

Fixed

• --no-normalize now actually disables normalization — the action handler
  only checked truthiness (if (opts.normalize)), so passing --no-normalize
  was silently ignored and normalization stayed on (the default). Now the boolean
  value is propagated correctly.
• Post-processing no longer trusts the pipe byte counter — the early-return
  guard in processRecording() compared result.size === 0 using the in-memory
  pipe counter, which could diverge from the actual bytes written to disk under
  backpressure or error-recovery paths. Now it reads the real file size from disk
  via statSync, so valid recordings are never skipped.

What's Changed

• Release v0.11.2 by @zfadhli in #21

Full Changelog: v0.11.1...v0.11.2