Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

update instrs

Justin D'Souza8143f84e0db6
diff --git a/CLAUDE.md b/CLAUDE.md
index 82b5f109..b63ef335 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -158,6 +158,13 @@ cd ../..
sh packaging/macos/test-endpoint-scripts.sh
```
+When building macOS `.pkg` artifacts, always include the Vector binary by
+setting `BEACON_VECTOR_BIN` (or `VECTOR_BIN`) to the release Vector executable
+before running `packaging/macos/build-pkg.sh` or
+`packaging/macos/build-signed-notarized-pkg.sh`. The package should install
+`/opt/beacon/bin/vector` so packaged Jamf/Fleet forwarder helpers work without a
+separate Vector install.
+
### Preferred CI Release
CI release automation should:
diff --git a/packaging/macos/README.md b/packaging/macos/README.md
index b05fdb78..6041adae 100644
--- a/packaging/macos/README.md
+++ b/packaging/macos/README.md
@@ -35,7 +35,8 @@ The endpoint install creates system configuration and runtime state:
## Build A Test Package
-Build Beacon and `beacon-otelcol`, then assemble the macOS package:
+Build Beacon, `beacon-otelcol`, and have the release Vector binary available,
+then assemble the macOS package:
```bash
cd cli/beacon
@@ -46,13 +47,15 @@ cd collector-builder
ocb --config builder.yaml
cd ..
-sh packaging/macos/build-pkg.sh
+BEACON_VECTOR_BIN="$(command -v vector)" \
+ sh packaging/macos/build-pkg.sh
```
Set `BEACON_APP_SIGN_IDENTITY` to sign payload binaries with a Developer ID
Application certificate, set `PKG_SIGN_IDENTITY` to sign the package with a
-Developer ID Installer certificate, and set `NOTARYTOOL_PROFILE` to submit and
-staple the package with Apple's notary service.
+Developer ID Installer certificate, set `BEACON_VECTOR_BIN` to include the
+Vector binary at `/opt/beacon/bin/vector`, and set `NOTARYTOOL_PROFILE` to
+submit and staple the package with Apple's notary service.
For release artifacts, use the signing wrapper so required identities are checked
up front and the final package signature, stapled ticket, Gatekeeper assessment,
@@ -61,6 +64,7 @@ and checksum are verified:
```bash
BEACON_APP_SIGN_IDENTITY="Developer ID Application: Example Corp (TEAMID)" \
PKG_SIGN_IDENTITY="Developer ID Installer: Example Corp (TEAMID)" \
+BEACON_VECTOR_BIN="$(command -v vector)" \
NOTARYTOOL_PROFILE="beacon-notary-profile" \
sh packaging/macos/build-signed-notarized-pkg.sh
```