6bb8f60f57
Switching to a profile with no provider configured popped the blocking onboarding overlay (Nous Portal / provider picker, "gateway isn't ready") the moment the profile's runtime info arrived — punishing the user for merely looking at an unconfigured bot/profile. The passive credential_warning (session create/activate/resume info, stream heartbeats) is now stashed instead of opening the overlay. The submit path consumes it when the user actually tries to chat and opens onboarding then, before the doomed send; the draft stays in the composer. A warning-free session event clears the stash, so healed or switched-away profiles never fire stale onboarding. Turn-error paths (a real failed send) still open onboarding immediately, unchanged.