4896cab0eb
Sibling site of the same class fixed in the previous commit: a failed profile-store open during _init_session fell back to _get_db(), hydrating and persisting a named-profile session's cwd row against the launch state.db. Fail closed instead — skip the hydration (log a warning) so nothing ever reads or writes the wrong profile's store. The other profile-store open sites (_db_for_profile, _ensure_session_db_row, _session_db) already degrade to None/skip and were left as-is.