A stream-json host can send initialize again to swap out its hooks mid-session.
What's wrong with this entry?
In stream-json input mode, hooks are no longer fixed at first connect. The process that owns the stdin stream can send a second initialize whose hooks replace the earlier set, and the reply's hooks_applied says whether that took effect.
- The documented schema for stdin was changed to drop hooks from the list of one-time session setup.
- A new internal call retires outstanding SDK host hook callbacks: any
hook_callbackrequest still in flight is cancelled and answered with a supplied fallback rather than left hanging.
hooks sent by the process that owns this stream replace the earlier set (see hooks_applied on the response)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.