Release v22.6.2

Fixed

• useIdentity now hands back the details it promises. The default details were substituted only when the identity was explicitly unset, so an identity that resolved while carrying no details — isSet is true — passed null through to callers, even though the declared return type says details is a TDetails. That is exactly why call sites dereference it unguarded, and one null reaching one of them takes the whole page down: a signed-in user got a blank screen with a TypeError on the first property read after their backend restarted. The default now stands in whenever there are no details to give, without displacing real ones.