Problem
Cua Driver 0.24.0 discovers updates from its GitHub component release feed and recommends the vendor installer regardless of whether pacman owns the running executable. In a package-managed installation, this can recommend a version before the package repository makes it available, advertise an unsupported nightly channel, or install a second user-local copy outside pacman.
The packaging workaround in omacom/omarchy-pkgs#306 redirects the embedded installer URL to a pacman guidance script. It blocks that installer path but does not change release discovery or channel guidance.
Selected scope
Prepare a focused draft fix for positive pacman ownership detection on Linux. Retain existing command and result shapes; do not introduce a new packaging configuration interface or change unmanaged installations.
- Suppress upstream startup update discovery for the pacman-owned executable.
- Make explicit CLI and MCP checks explain that pacman controls availability, without claiming a GitHub version is installable or that the package is up to date.
- Direct update attempts to
sudo pacman -Syu without invoking an installer or sudo automatically.
- Refuse Driver channel changes for the package-owned executable with package-manager guidance.
- Cover the low-level installer entry point as well as the CLI.
Acceptance evidence
Focused tests must distinguish package ownership from merely having pacman installed, handle executable symlinks and query failures, and verify that managed paths neither query upstream releases nor invoke the vendor installer. Existing unmanaged update behavior must retain focused regression coverage. Native pacman validation remains an explicit prerequisite before readiness or release.
This issue tracks the Driver fix only. The Omarchy package and optional ABI-pinned Hyprland plugin remain separate packaging reviews.
Problem
Cua Driver 0.24.0 discovers updates from its GitHub component release feed and recommends the vendor installer regardless of whether pacman owns the running executable. In a package-managed installation, this can recommend a version before the package repository makes it available, advertise an unsupported nightly channel, or install a second user-local copy outside pacman.
The packaging workaround in omacom/omarchy-pkgs#306 redirects the embedded installer URL to a pacman guidance script. It blocks that installer path but does not change release discovery or channel guidance.
Selected scope
Prepare a focused draft fix for positive pacman ownership detection on Linux. Retain existing command and result shapes; do not introduce a new packaging configuration interface or change unmanaged installations.
sudo pacman -Syuwithout invoking an installer or sudo automatically.Acceptance evidence
Focused tests must distinguish package ownership from merely having pacman installed, handle executable symlinks and query failures, and verify that managed paths neither query upstream releases nor invoke the vendor installer. Existing unmanaged update behavior must retain focused regression coverage. Native pacman validation remains an explicit prerequisite before readiness or release.
This issue tracks the Driver fix only. The Omarchy package and optional ABI-pinned Hyprland plugin remain separate packaging reviews.