feat: a Mac offers to remove the 1.x it finds, and the resident holds the shortcut

[rgdevment]

1.x ships under com.rgdevment.linkunbound and 2.x under dev.rgdevment.linkunbound, so Launch Services treats them as unrelated applications: the old copy keeps its own login item, starts at sign-in and goes on answering for links however 2.x registers. Windows removes it from the installer; a Mac is dragged in, so the settings window is the only place that can ask.

Links now offers to retire a 1.x it finds: the copy goes to the trash, never deleted, and rules and browsers are untouched. A refusal — /Applications needs an administrator — hands the person to Finder. The command takes no path, so it cannot be asked to trash anything else.

The global shortcut moves to the resident. It was claimed by the settings binary, whose only effect was to open the very window that had to be open for the claim to exist, and sign-in starts the resident alone: the preference did nothing. The resident claims it through global-hotkey and writes down what it holds, which is what the window now reads.

Also:

• The notice no longer takes the keyboard on a Mac. There is no window style for it there, so the application stops being the active one instead — unless a picker is up, which is the one moment it has to be.
• Copy and private answer to Cmd on a Mac, where Ctrl+click is a right click.
• The link channel refuses to open rather than fall back to a descriptor every account on the machine can read, with a test for both ways it can fail.
• The uninstaller sweeps the OpenWithProgIds values it writes; without them "Open with" went on offering a program that is gone. A test fails if the list in the installer and the one in the code ever drift apart.
• The diagnostics report is written in the language that was chosen, file name included, and lands on the Desktop of a Mac instead of its temporary folder.
• One rule decides whether a version is worth offering. The strip compared semver alone, so it offered candidates the errand behind the button refused.
• The resident's build script reads the target rather than the host, which is what made a cross build for a Mac embed a Windows manifest and die.
• release: the tested gate waits forty minutes instead of twenty and the bundles wait for it; the tap token stays out of the clone's .git/config; the signing certificate leaves the runner store; the Store is asked what became of a submission that was tolerated, which is the case the question was written for.
• scripts: the cache sweep sees past the hundredth cache.
• save_prefs had no callers but its own tests; the stale version in app/package.json and the unread release-manifest.json at the root are gone.