Fix macOS release runners

Author: JannikJung

.github/workflows/release.yml

@@ -19,9 +19,9 @@ jobs:
           - label: linux-x64
             os: ubuntu-latest
           - label: darwin-x64
-            os: macos-13
+            os: macos-15-intel
           - label: darwin-arm64
-            os: macos-14
+            os: macos-15
 
     steps:
       - name: Check out repository

README.md

@@ -66,6 +66,14 @@ Use foreground mode while debugging:
 ./attention start --foreground
 ```
 
+macOS release binaries are not Apple Developer ID signed or notarized yet. If Gatekeeper warns on
+first launch, open the binary explicitly from Finder or remove the quarantine attribute:
+
+```sh
+xattr -d com.apple.quarantine ./attention
+./attention start
+```
+
 ### Clone And Extend
 
 Use the source path when you want to inspect, modify, or extend the app:

docs/INSTALL.md

@@ -55,6 +55,15 @@ operator/capability references.
 The packaged executable resolves UI assets from the sibling `dist/` directory, so it can be launched
 from inside the extracted folder or by absolute path from another working directory.
 
+Release binaries are not Apple Developer ID signed or notarized yet. On macOS, Gatekeeper may show a
+first-run warning for downloaded archives. You can still run Attention by opening the binary
+explicitly from Finder or by removing the quarantine attribute:
+
+```sh
+xattr -d com.apple.quarantine ./attention
+./attention start
+```
+
 ## Codex Setup
 
 ```sh