Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release
What
The fork_conversation RPC's early bail-out conditions changed from four checks to three: it now checks two gate functions plus a freshly computed bridge session ID for being undefined, rather than relying on a separately tracked variable.
On top of the existing sdkUrl-based check, fork_conversation now returns "unsupported" if either of these two additional gate checks fails.
Why
This tightens up when conversation forking is considered available, and adds conditions under which the RPC now reports itself unsupported instead of proceeding.
