# M9.8b UI state and event bounds Owned, toolkit-independent state; all calls on the client main thread. No authority or simulation state. Time is explicit monotonic milliseconds supplied by the host. Notifications: at most eight, text at most 240 bytes; reject invalid/oversized input, expire by deadline, dismiss by unique id. Overflow evicts oldest and increments a visible saturating counter. Notifications are not durable outcome history. Dialogs: one active modal, title at most 96 bytes and body at most 240; opening a second fails. Close requires the matching id so a stale click cannot close a newer dialog. IDs never wrap. No credentials or grant bytes enter display messages. SessionClient keeps at most 1024 queued ClientEvents. At 766 regular events it emits a local backpressure event, disconnects, and has room for loss plus 256 unknown intentions. It preserves all previously queued events and pauses reconnect until take_events drains the queue. This is a local condition, not a protocol change. Unprocessed wire outcomes remain unknown, never assumed failed or committed. The native adapter's externally requested capture cannot be disabled by the legacy Tab toggle. Releasing capture drains already queued input before new world actions. Rendering dialogs/toasts and wiring toolkit capture occur with the launcher in M9.8c; these contracts and their tests precede that integration.