feat: install drover-notify from GitHub now that the repo is public

[keinstn]

Closes #122.

keinstn/drover-notify went public, which removes the constraint everything here was written around: herdr plugin install clones over unauthenticated HTTPS, so it could not reach a private repo.

In-app pairing dialog

It told the user to run herdr plugin link /path/to/drover-notify and then node /path/to/drover-notify/bin/setup.mjs … — a literal they had to find and substitute twice. Now it shows one command with nothing to edit:

herdr plugin install keinstn/drover-notify

The setup command is removed rather than rewritten. plugin install puts the checkout where herdr chooses, so there is no path drover can print — and none is needed: this dialog only appears when _detectPlugin found nothing, and once the plugin is installed detection succeeds and pairing runs automatically. The reworded intro says exactly that. The pairing code and completion URL stay on screen for anyone pairing by hand.

hostPairingLinkCommandLabel / hostPairingSetupCommandLabel → hostPairingInstallCommandLabel / hostPairingManualNote, in both locales.

docs/push-notifications.md

herdr plugin install keinstn/drover-notify is the documented path; the "not yet available" note is gone. Cloning and linking is kept, reframed as the option for running a fork or testing a branch rather than a workaround for a private repo.

The stated Herdr floor moves 0.7.0 → 0.7.5. 0.7.0 is what the plugin alone needs and drover-notify's README correctly says so, but this document is read by drover users and kMinHerdrVersion is (0, 7, 5). Below it drover still reads and steers agents but refuses to start them — so the old text left people with working notifications and an app that would not launch anything. A note explains the two floors so the number does not get "corrected" back.

Verification

• fvm flutter analyze → No issues found!
• fvm flutter test → All tests passed! (791, full suite; +1 new)
• New widget test asserts the rendered dialog contains the install command and no /path/to/, plugin link or setup.mjs text. Mutation-checked: restoring the old plugin link /path/to/drover-notify fails that test and only that test.

From #122's checklist

• docs/push-notifications.md — install one-liner, "not yet available" note dropped
• host_setup_screen.dart — install one-liner, placeholder path gone, l10n reworded, test updated
• README.md — checked; it never claimed the repo was private, and "manually installed" stays true because installing is deliberately a host operation
• drover-notify's own README.md — already updated in that repo
• Re-install the plugin on the host — yours to run: herdr plugin unlink drover.notify, then install from GitHub. A linked plugin cannot be replaced in place. The pairing credential survives, since its config dir derives from the plugin id.

🤖 Generated with Claude Code