v0.22.1

A patch release: the session event stream now reports user prompts.

Added

user_message { entryId, text } session event (#645, #649, #650). A client can place each user message where the model read it, without inferring the position. The event covers the opening prompt, a steer or follow-up leaving pending, and a message an extension sends. It arrives after the message is recorded, so entries() already holds entryId, and before the answer to that message. A reconnecting client can deduplicate its backfill by entryId.

KnownSessionEvent gains this member. Code that switches exhaustively over it with a never check needs a case for user_message. At runtime, clients already ignore event types they do not know.

Full Changelog: v0.22.0...v0.22.1