Open the keybindings menu on first login

The welcome toast spent three lines telling you about a cheatsheet that takes
one keystroke to read, and the only way to act on it was to click the toast,
which opened that cheatsheet. Open it directly instead.

Dismissing the menu exits non-zero, since no selection was made, so the step
tolerates that rather than failing first run and retrying the whole sequence
next login.

It also goes last now. The menu blocks until it is answered, and the Wi-Fi and
update toasts are the only other things left to show, so sending those first
leaves them waiting underneath rather than behind an open menu.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

bin/omarchy-provision-first-run

@@ -83,12 +83,12 @@ run_first_run_step "apply speaker tuning" \
   bash "$OMARCHY_PATH/install/user/first-run/audio-tuning.sh"
 
 omarchy-notification-wait || log_first_run "Timed out waiting for notification service; continuing"
-# Each send returns only once the server has taken the toast, so sending in
-# order is enough to stack them newest-on-top.
-run_first_run_step "show welcome notification" \
-  bash "$OMARCHY_PATH/install/user/first-run/welcome.sh"
 run_first_run_step "show Wi-Fi/update notifications" \
   bash "$OMARCHY_PATH/install/user/first-run/wifi.sh"
+# Waits for the menu to be answered, so it goes last and leaves the toasts
+# waiting underneath.
+run_first_run_step "show keybindings" \
+  bash "$OMARCHY_PATH/install/user/first-run/keybindings.sh"
 
 if (( first_run_failed == 0 )); then
   omarchy-done mark "$FIRST_RUN_DONE"