Patchbay 0.1.1 — signed and notarized on macOS

The macOS build is now signed with a Developer ID certificate and notarized by
Apple. Double-click the .dmg and it opens: no "unidentified developer", no
right-click → Open, no Gatekeeper detour.

That is the whole release. There are no functional changes — the app, the
daemon and the protocol are identical to 0.1.0.

What changed

• Developer ID signing + Apple notarization for both macOS architectures,
  under Hardened Runtime with a secure timestamp, and the notarization ticket
  is stapled to the app — so it validates offline, on a machine that has
  never seen Apple's notary service.
• The vendored uv inside the bundle carries the same signature. It is not
  along for the ride; it is covered.

Verified the way you actually receive it rather than from a build log: the
published .dmg was downloaded, flagged with the quarantine attribute Safari
sets, mounted, and put to Gatekeeper — accepted, source=Notarized Developer ID, on both mac-arm64 and mac-x64.

Windows is unchanged, and still unsigned

The .exe has no Authenticode certificate, so SmartScreen still asks: More
info → Run anyway. Nothing in this release affects Windows.

A note on the dmg itself

If you check the .dmg container with spctl, it reports rejected / no usable signature. That is expected and correct — the notarization ticket is
stapled to the .app inside it, which is what Gatekeeper assesses when you
launch. Most shipping macOS dmgs behave the same way.