imccyu a0b618abb9 fix(client): publish current session provide bundle as one reactive projection ... A provider roster change under a stable current id rematerialized every scope's bundle but nothing notified React: SessionProvider resolved the bundle from a current-id subscription only, so mounted entries kept the obsolete hook/prop schema until an unrelated re-render. The sessions service now owns an atomic currentProvide observable fed by both current writes and roster changes; the renderer host exposes it as sessions.provide, replacing the current/provideInfo/maybeProvideInfo trio, and both providers subscribe to it.		2026-07-28 12:09:48 +08:00
..
bind.spec.tsx	chore(lint): apply eslint auto-fixes across the .tsx backlog	2026-07-27 21:49:40 +08:00
scoped-slots-real-core.spec.tsx	fix(client): publish current session provide bundle as one reactive projection	2026-07-28 12:09:48 +08:00
scoped-slots.spec.tsx	fix(client): publish current session provide bundle as one reactive projection	2026-07-28 12:09:48 +08:00
session-provider.spec.tsx	fix(client): publish current session provide bundle as one reactive projection	2026-07-28 12:09:48 +08:00
stale-authorization.spec.tsx	fix(client): publish current session provide bundle as one reactive projection	2026-07-28 12:09:48 +08:00
use-invoke.spec.tsx	chore(lint): clear the semantic .tsx backlog	2026-07-27 22:23:41 +08:00