dir_session_resolved = true is set in exactly two places: the onboarded branch at handle_backend.rs:2779, and create_session() (handle_actions.rs:1926).
When resp.needs_onboarding is true the wizard branch is taken and neither runs. OnboardingComplete(Ok) (handle_backend.rs:3348-3384) sets identity and calls submit_prompt(...), which bypasses the gate, but never sets dir_session_resolved and never calls create_session. Same for OnboardingAction::Cancel.
So after a brand-new install completes setup, every message the user types is queued by submit_input (handle_actions.rs:685-693) and never drains. This breaks first-run for every new user.
Fix: set dir_session_resolved (or call create_session) on onboarding completion and cancel.
Shipped knowingly in v1.0.177.
dir_session_resolved = trueis set in exactly two places: the onboarded branch athandle_backend.rs:2779, andcreate_session()(handle_actions.rs:1926).When
resp.needs_onboardingis true the wizard branch is taken and neither runs.OnboardingComplete(Ok)(handle_backend.rs:3348-3384) sets identity and callssubmit_prompt(...), which bypasses the gate, but never setsdir_session_resolvedand never callscreate_session. Same forOnboardingAction::Cancel.So after a brand-new install completes setup, every message the user types is queued by
submit_input(handle_actions.rs:685-693) and never drains. This breaks first-run for every new user.Fix: set
dir_session_resolved(or callcreate_session) on onboarding completion and cancel.Shipped knowingly in v1.0.177.