@juspay/neurolink 11.30.0 → 12.0.0

package/CHANGELOG.md

@@ -1,8 +1,60 @@
-## [11.30.0](https://github.com/juspay/neurolink/compare/v11.29.2...v11.30.0) (2026-08-25)
+## [12.0.0](https://github.com/juspay/neurolink/compare/v11.30.0...v12.0.0) (2026-08-25)
 
-### Features
+### ⚠ BREAKING CHANGES
+
+- **(tts):** out of a TTS-enabled stream blocked the consumer permanently:
+
+  pnpm run test:tts:unit 2.95s user 1% cpu 5:09.80 total
+
+1% CPU over five minutes is not slow work — nothing was running. The
+process sat idle in teardown.
+
+interleaveTTSStream's finally awaited Promise.allSettled on the source
+and audio iterators' .return(). `.return()` on an async generator parked
+inside an `await` does not interrupt it: the request is queued behind the
+in-flight next() and only runs when the generator next suspends. A
+provider stream is wrapped several times — lifecycle in baseProvider, MCP
+and pool wrappers in neurolink — and during a pull every one of those
+layers sits in an `await` on the layer below. None can unwind, so those
+promises settle never, not late. Instrumented, at the hang:
+
+finally ENTERED completed=false nextSource=true nextAudio=true
+awaiting allSettled of 2 release(s)
+calling sourceIterator.return()
+calling audioIterator.return()
+<neither ever resolved>
+
+Two changes, because the generator protocol alone cannot express this.
+
+streamCancellation.ts adds an out-of-band channel. A wrapper registers a
+cancel callback on the stream object it returns; the callback closes its
+own upstream iterator and forwards the request downward. These are plain
+function calls, not generator protocol, so they run immediately and do not
+depend on any pending next() settling. baseProvider hoists its upstream
+iterator — iterating the hoisted handle is equivalent to iterating the
+original, it just leaves something reachable from outside the generator —
+and registers a hook. interleaveTTSStream fires it on abandonment before
+asking politely via .return().
+
+Registration is optional and reading it is defensive, so a stream that
+knows nothing about this behaves exactly as before.
+
+Teardown is also now bounded. Even with the channel, this module cannot
+assume every upstream cooperates, and a consumer's exit must not depend on
+one that may never answer. The releases are still issued and still
+propagate whenever the upstream is responsive.
+
+test:tts:unit 327s exit 0, 1 test skipped -> 83s exit 0, 43 passed
+
+That test had never passed. It and the cleanup it probes both arrived in
+
+### Bug Fixes
+
+- **(tts):** stop early stream break from hanging the caller forever ([c8f3d5b](https://github.com/juspay/neurolink/commit/c8f3d5b0ab71621916ec7d9d6970243ff916cae8)), closes [#1336](https://github.com/juspay/neurolink/issues/1336)
+
+### Performance Improvements
 
-- **(proxy):** peer capacity sharing with lender-controlled grants ([d0eab07](https://github.com/juspay/neurolink/commit/d0eab07556fb2a73180c86a23acc9a1b6aecea70))
+- **(ci):** balance extended-suite shards by measured duration, not count ([ed7c300](https://github.com/juspay/neurolink/commit/ed7c300b4171dd2db4dab59e4ef18dfd9477110c))
 
 ## [11.2.3](https://github.com/juspay/neurolink/compare/v11.2.2...v11.2.3) (2026-08-19)