Desktop local setup leaves kcap off the terminal PATH and its success banner never clears

After a local install through the desktop app's setup wizard, opening the app shows the "Install command-line tool" offer: the wizard only links kcap onto the terminal PATH from the Harnesses step, and only when a harness is selected. The terminal command should be part of the install itself.

Accepting the offer then posts "kcap is now on your terminal PATH." into the launcher's warning banner, which never clears while the daemon stays connected — and a success line does not belong in warning orange.