fix(desktop): keep slash completion alive after a leading command

[OutThisLife]

A second slash command in the desktop composer only completes when the message starts with prose. do /work then /cle opens the popover; /work /cle opens nothing. Same session, same skills — the difference is the first character of the draft, which reads as an intermittent glitch rather than a rule.

detectTrigger tries the ^-anchored command shape before the inline one. Its argument tail (?:\s+\S*)* swallows the rest of the line, so a later /skill parses as an argument to the first command; refreshTrigger then suppresses the popover for any command whose argumentMode isn't options/mixed, and every slash after the first is unreachable. /goal and /personality happen to escape it by being arg-taking, which is what makes the failure look random.

Only the first slash can be an invocation, so the inline shape is detected first. It requires a whitespace-preceded slash sitting at the caret, so it can't take over ordinary argument completion — /personality alic has no second slash — and it fires only where completion was already dead.

[github-actions]

૮ >ﻌ< ა ci review

_{ran on eb851d6}

ℹ️ Info

Desktop E2E visual evidence · View test artifacts · View job

1 visual diff.

_{inline evidence upload failed.}

Failed to upload diff-665a0833239e-onboarding-overlay-diff.png with gh image (exit code 1): Error uploading /home/runner/work/_temp/e2e-evidence/diff-665a0833239e-onboarding-overlay-diff.png: step 0 (get upload token): uploadToken not found on repo page — do you have write access to NousResearch/hermes-agent? (or, if NousResearch enforces SAML SSO, authorize at https://github.com/orgs/NousResearch/sso)