feat(launcher): built-in System commands (sleep, lock screen, restart, shut down, …)

[dose-dot-dev]

What

Adds a Raycast-style System built-in feature: one-shot power/session actions available from search —

• Sleep
• Hibernate (only where the OS actually has it enabled)
• Lock Screen
• Sign Out (Windows) / Log Out (macOS/Linux)
• Restart
• Shut Down

Destructive actions (sign out / restart / shut down) show a danger confirm dialog first, using the same focus-lock idiom as the Quit feature. Sleep/hibernate/lock fire immediately, hiding the launcher window before the OS takes over.

Why

These are table-stakes launcher commands (Raycast ships them out of the box on both macOS and Windows) and Asyar currently has no equivalent target. Bonus: raycast_import currently has to skip imported system-command hotkeys because there is nothing to map them to — with this landed, a follow-up could map them to cmd_system_dyn_* targets.

How

Rust — new system_actions module, deliberately mirroring the power module's shape (platform-neutral state + backend trait, per-platform backends, fake backend for tests):

• Windows: SetSuspendState (sleep/hibernate), LockWorkStation, ExitWindowsEx (logoff/reboot/poweroff, no EWX_FORCE — apps keep their save prompts), with the SeShutdownPrivilege enable dance where required. Hibernate is offered only when IsPwrHibernateAllowed().
• macOS: pmset sleepnow; CGSession -suspend for lock; osascript → System Events log out / restart / shut down (same graceful semantics as the Apple menu; first use triggers the one-time Automation consent). No hibernate.
• Linux: logind over D-Bus (zbus blocking, same transport as power::linux) — Suspend/Hibernate/Reboot/PowerOff gated on their Can* probes with interactive = true so polkit can prompt; Session(auto).Lock with an org.freedesktop.ScreenSaver.Lock fallback; log out = Session(auto).Terminate.

Command surface (system_actions_supported / system_action_run) is host-only: like quit_app, the commands are not mapped in the asyar:api:* permission table, so extension workers can't reach them through the broker. Exposing them to extensions would need a dedicated permission + consent wiring first — out of scope here.

Frontend — built-in-features/system registers one dynamic command per supported action (via replaceDynamicCommandsBuiltin, allowlisted alongside scripts/agents), so the search index only ever contains actions this machine can perform — e.g. Hibernate never appears where the OS has it disabled, and a non-systemd Linux box degrades to just Lock Screen. run() re-checks supported() Rust-side, so it fails closed even if a stale row survives.

Two new SDK icons (moon, log-out) follow the calc-* precedent from #489.

Design notes / open questions

• macOS routes need a maintainer sanity check — I could only hand-test Windows. CGSession -suspend (lock) and the System Events verbs are the widely-used non-private-API routes, but if you prefer SACLockScreenImmediate or different semantics, happy to adjust.
• Linux Log Out is logind Terminate — session-level, not the DE's graceful logout flow. It's behind the confirm dialog; alternative would be DE-specific commands (gnome-session-quit etc.), which felt worse.
• Naming: Sign Out on Windows, Log Out elsewhere, matching each OS's own terminology.

Verification

• cargo test — 2864 passed (incl. the built-in manifest schema test over the new manifest and 9 new unit tests); cargo clippy --all-targets -- -D warnings and cargo fmt clean. (Run under WSL/Linux as with previous PRs — cargo test on Windows currently fails to load the test binary on clean main (STATUS_ENTRYPOINT_NOT_FOUND, reproduces after cargo clean, app binary unaffected); I'll file that separately.)
• pnpm -r test:run — green (Windows), incl. 9 new tests covering registration order/filtering, per-platform naming, confirm/cancel flows, and unknown-id handling.
• Manual (Windows 11, isolated dev launcher): commands present in search with the expected icons; Hibernate visibility matches powercfg /a; Lock Screen and Sleep end-to-end (launcher hides before the action fires); Sign Out / Restart / Shut Down danger confirm dialogs verified incl. the cancel path.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request introduces a new built-in system feature that allows users to trigger system actions (sleep, hibernate, lock screen, log out, restart, and shut down) across Linux, macOS, and Windows. The feedback identifies critical compilation errors on Windows due to the use of the windows crate's BOOLEAN type instead of Rust's native bool. On macOS, the lock screen command relies on a deprecated CGSession path that was removed in macOS 11, which will cause runtime failures. Finally, it is recommended to change the Tauri commands to async fn to prevent blocking the main UI thread during synchronous OS operations.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[Xoshbin]

Hey @dose-dot-dev since you are working on Windows, sounds like the commands are all working on windows. but on macos, I just tested some of the commands, some of them are working and some of them are not. since you are on Windows I will work on the macos platform side myself then merge it.
Thank you for the great contributions.

[dose-dot-dev]

Thanks @Xoshbin hopefully they are simple fixes on the macos side. Eventually I'll have a Mac with a configured dev environment I'll be able to catch some of these things on as well.

[Xoshbin]

this is merged! Thanks for the PR and getting these system commands set up. It's honestly really helpful having someone whose main platform is Windows contributing to the project, as it helps cover that side of things a lot.

Also, congrats on the new Mac! Having a configured dev environment will definitely make testing the macOS side easier down the road. Enjoy the new setup!