feat(client): refine launcher UI and interactions

[Nirvana-Jie]

Summary

• strengthen launcher selection hierarchy, contrast, reduced-motion behavior, and narrow-screen actions
• keep app-level commands out of the default launcher view while avoiding duplicate recent results during search
• fix settings focus ownership and keyboard semantics for tabs, switches, and radio groups
• make the web launcher overlay modal by trapping focus, isolating the background, and restoring the trigger focus
• add Vitest coverage for launcher section visibility

Why

A visual and interaction audit found that the active command was too subtle, search could show duplicate commands, explicit actions disappeared on narrow screens, and settings keyboard events could affect the wrong control. The embedded web overlay also allowed focus to escape into the underlying app.

Visual review

Desktop launcher — light	Settings — dark
The focused command now has a full-row focus surface and signal rail. App-level commands stay out of the default view, leaving the primary launch actions easier to scan.	Active settings use the same focus language while muted labels and controls retain clearer contrast in the dark theme.

390px responsive settings

Controls stack below their labels, descriptions remain readable, and keyboard hints collapse without removing the explicit action path.

User impact

The launcher is easier to scan in light and dark themes, touch users retain an explicit action path, keyboard interactions operate the focused control, and embedded launcher usage keeps focus contained and predictable.

Validation

• pnpm typecheck
• targeted ESLint for the changed launcher files
• 21 Vitest checks across launcher section visibility, plugin search, relay projects, shortcuts, and i18n resources
• manual Electron light/dark visual regression
• manual 390px responsive regression
• manual keyboard regression for command navigation, switches, and radio groups

[vercel]

Someone is attempting to deploy a commit to the oneworks Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Experience Review

Before merge, make sure the PR body contains this completed checklist:

## Experience Review
- [x] 已判断是否需要沉淀经验
- [x] 如需要，已运行 `$post-task-experience-review`
- [x] reviewer PASS 后才进入 merge

Checklist to confirm:

• Decide whether this PR produced reusable project experience.
• If experience should be captured, run $post-task-experience-review.
• Merge only after the independent reviewer reports PASS.