@meridiona/meridian-darwin-arm64 1.10.0 → 1.11.0

package/VERSION

@@ -1 +1 @@
-1.10.0
+1.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meridiona/meridian-darwin-arm64",
-  "version": "1.10.0",
+  "version": "1.11.0",
   "description": "Prebuilt Meridian app for macOS arm64 (daemon binary + dashboard + Python services). Installed via @meridiona/meridian.",
   "homepage": "https://github.com/Meridiona/meridian",
   "repository": {

package/scripts/install-from-bundle.sh

@@ -257,13 +257,40 @@ else
     ok "meridian-daemon + meridian → ~/.local/bin"
 fi
 
-# ── 4. Python venv + MLX deps (the one install-time download) ────────────────
-info "Setting up Python venv + MLX inference deps (downloads ~ a few hundred MB)…"
+# ── 4. Python venv + MLX deps ────────────────────────────────────────────────
+# meridian-npm-setup.sh preserves an existing venv across updates, so on a normal
+# update the venv is already here. The pip install (mlx-lm/outlines/fastapi) costs
+# minutes, so we skip it when the dependency spec is unchanged: hash the parts of
+# pyproject.toml that define the deps and stamp it in the venv. Re-pip only when a
+# fresh venv was created or the hash differs (a release that bumped Python deps).
 VENV="${APP_ROOT}/services/.venv"
-[[ -d "${VENV}" ]] || "${PYTHON_BIN}" -m venv "${VENV}"
-"${VENV}/bin/pip" install --quiet --upgrade pip
-"${VENV}/bin/pip" install --quiet -e "${APP_ROOT}/services[mlx]"
-ok "Python services ready"
+DEPS_STAMP="${VENV}/.meridian-deps-hash"
+deps_hash() { shasum -a 256 "${APP_ROOT}/services/pyproject.toml" 2>/dev/null | cut -d' ' -f1; }
+want_hash="$(deps_hash)"
+
+fresh_venv=0
+if [[ ! -x "${VENV}/bin/python" ]]; then
+    info "Creating Python venv…"
+    rm -rf "${VENV}"
+    "${PYTHON_BIN}" -m venv "${VENV}"
+    fresh_venv=1
+fi
+
+have_hash=""
+[[ -f "${DEPS_STAMP}" ]] && have_hash="$(cat "${DEPS_STAMP}" 2>/dev/null)"
+
+if [[ "${fresh_venv}" -eq 1 || "${want_hash}" != "${have_hash}" || -z "${want_hash}" ]]; then
+    info "Installing Python + MLX deps (mlx-lm/outlines/fastapi; downloads ~ a few hundred MB on first run)…"
+    "${VENV}/bin/pip" install --quiet --upgrade pip
+    if "${VENV}/bin/pip" install --quiet -e "${APP_ROOT}/services[mlx]"; then
+        [[ -n "${want_hash}" ]] && printf '%s\n' "${want_hash}" > "${DEPS_STAMP}"
+        ok "Python services ready"
+    else
+        warn "pip install failed — leaving venv as-is; re-run 'meridian setup' to retry"
+    fi
+else
+    ok "Python deps unchanged — reusing existing venv (skipped pip install)"
+fi
 
 # ── 5. macOS permissions for screenpipe (manual — can't be automated) ────────
 if [[ "${SKIP_PERMISSIONS}" -eq 0 ]]; then

package/scripts/install-screenpipe-daemon.sh

@@ -31,12 +31,31 @@ if [[ ! -f "${TEMPLATE}" ]]; then
     exit 1
 fi
 
-# Locate the screenpipe binary.
+# Locate the screenpipe binary. The npm package ships a Node *wrapper* at
+# `command -v screenpipe` (a cli.js shim) that spawns the real arm64 Mach-O. If
+# the launchd agent launches that wrapper, macOS attributes Screen Recording /
+# Accessibility to `node` (the responsible process) — a broad, fragile grant
+# (breaks on node upgrades) that also shows a scary "node wants to record your
+# screen" prompt. Resolve the real Mach-O and launch it directly so the grant
+# attaches to a stable binary named `screenpipe` (and survives reinstalls of the
+# same version, since its path is fixed). Falls back to whatever `command -v`
+# found when screenpipe is a native binary (Homebrew) rather than the npm shim.
 SCREENPIPE_BIN="$(command -v screenpipe)" || true
 if [[ -z "${SCREENPIPE_BIN}" ]]; then
     echo "✗ screenpipe binary not found in PATH — install with: npm install -g screenpipe" >&2
     exit 1
 fi
+_npm_root="$(npm root -g 2>/dev/null || true)"
+if [[ -n "${_npm_root}" && -d "${_npm_root}/screenpipe" ]]; then
+    _real=""
+    while IFS= read -r _cand; do
+        if file "${_cand}" 2>/dev/null | grep -q "Mach-O"; then _real="${_cand}"; break; fi
+    done < <(find "${_npm_root}/screenpipe" -type f -name screenpipe -perm +0111 2>/dev/null)
+    if [[ -n "${_real}" ]]; then
+        SCREENPIPE_BIN="${_real}"
+        echo "→ using the real screenpipe binary (not the node wrapper): ${SCREENPIPE_BIN}"
+    fi
+fi
 
 mkdir -p "${HOME}/.meridian/logs"
 mkdir -p "${LAUNCH_AGENTS}"

package/scripts/meridian-npm-setup.sh

@@ -20,13 +20,29 @@ mkdir -p "$(dirname "${APP}")"
 keep=""
 if [[ -f "${APP}/.env" ]]; then keep="$(mktemp)"; cp "${APP}/.env" "${keep}"; fi
 
+# Preserve the Python venv across updates. Rebuilding it (python -m venv + pip
+# install mlx-lm/outlines/…) costs minutes; most releases don't change Python
+# deps, so move it aside and restore it to the SAME absolute path (its baked-in
+# shebangs stay valid). install-from-bundle.sh then only re-pips when the deps
+# hash actually changes. Kept in a sibling dir under ~/.meridian so the move is
+# an instant rename (same filesystem), never a cross-volume copy.
+venv_keep="${HOME}/.meridian/.venv-update-keep"
+rm -rf "${venv_keep}"
+if [[ -d "${APP}/services/.venv" ]]; then mv "${APP}/services/.venv" "${venv_keep}"; fi
+
 rm -rf "${APP}"
 mkdir -p "${APP}"
-# Copy the prebuilt payload (bin/ ui/ services/ scripts/ .env.example VERSION).
+# Copy the prebuilt payload (bin/ ui.tar.gz services/ scripts/ .env.example VERSION).
 cp -R "${BUNDLE}/." "${APP}/"
 # Drop npm-package metadata that isn't part of the app.
 rm -f "${APP}/package.json" "${APP}/README.md" "${APP}/.gitignore" "${APP}/.npmignore"
 
 [[ -n "${keep}" ]] && { cp "${keep}" "${APP}/.env"; rm -f "${keep}"; }
+# Restore the preserved venv (the bundle ships services/ source but no venv).
+if [[ -d "${venv_keep}" ]]; then
+    mkdir -p "${APP}/services"
+    rm -rf "${APP}/services/.venv"
+    mv "${venv_keep}" "${APP}/services/.venv"
+fi
 
 exec bash "${APP}/scripts/install-from-bundle.sh" "$@"

package/services/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "meridian-agents"
-version = "1.10.0"
+version = "1.11.0"
 description = "Meridian agents — hermes task linking and Jira progress updates for meridian.db"
 requires-python = ">=3.11"
 authors = [{ name = "Meridiona" }]