@meridiona/meridian-darwin-arm64 1.20.1 → 1.22.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/VERSION CHANGED
@@ -1 +1 @@
1
- 1.20.1
1
+ 1.22.0
package/bin/meridian CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@meridiona/meridian-darwin-arm64",
3
- "version": "1.20.1",
3
+ "version": "1.22.0",
4
4
  "description": "Prebuilt Meridian app for macOS arm64 (daemon binary + dashboard + Python services). Installed via @meridiona/meridian.",
5
5
  "homepage": "https://github.com/Meridiona/meridian",
6
6
  "repository": {
@@ -251,22 +251,23 @@ fi
251
251
  # ── 3. Binary + CLI symlinks ─────────────────────────────────────────────────
252
252
  mkdir -p "${HOME}/.local/bin"
253
253
  ln -sfn "${APP_ROOT}/bin/meridian" "${HOME}/.local/bin/meridian-daemon"
254
- # Do NOT shadow the npm launcher with a second `meridian` on PATH. When installed
255
- # via npm, the launcher (`meridian.js`) owns `setup`/`update` and delegates
256
- # start/stop/doctor to this bundle's CLI by its real path. ~/.local/bin usually
257
- # precedes the npm bin dir on PATH, so a ~/.local/bin/meridian symlink would hide
258
- # `meridian setup` / `meridian update` (it can't reach the launcher).
254
+ # Put a single `meridian` on PATH that owns every command. The npm launcher
255
+ # (`meridian.js`) owns `setup`/`update` and delegates start/stop/doctor to this
256
+ # bundle's CLI; the CLI alone does NOT know `setup`/`update`. So we point
257
+ # ~/.local/bin/meridian AT the launcher (not the CLI) whenever a launcher exists.
259
258
  #
260
- # The launcher's location depends on the npm prefix: /usr/local/bin on a default
261
- # prefix, but ~/.npm-global/bin when the EACCES bootstrap redirected the prefix to
262
- # a user-writable dir. Resolve the prefix from npm rather than assuming
263
- # /usr/local otherwise the launcher is missed and the CLI shadow hides `update`.
264
- # Only create the CLI symlink as a fallback when no launcher is present (e.g. a
265
- # standalone bundle install); when the launcher exists, remove any stale shadow
266
- # so `meridian update` self-heals an install made by an older bundle.
259
+ # Why ~/.local/bin and not rely on the npm bin dir being on PATH: the launcher's
260
+ # own bin dir depends on the npm prefix (/usr/local/bin by default, but
261
+ # ~/.npm-global/bin when the EACCES bootstrap redirected the prefix). That dir is
262
+ # only added to PATH via a shell-rc patch, which doesn't apply to already-open
263
+ # shells and may never apply for bash users. ~/.local/bin is a standard user bin
264
+ # dir that is reliably on PATH already, so pointing it at the launcher makes
265
+ # `meridian update` work in every shell immediately no rc reload required, no
266
+ # CLI shadow hiding `update`. Fall back to the CLI only for a standalone bundle
267
+ # install where no npm launcher is present.
267
268
  _launcher=""
268
269
  _npm_prefix="$(npm config get prefix 2>/dev/null || true)"
269
- for _cand in "/usr/local/bin/meridian" ${_npm_prefix:+"${_npm_prefix}/bin/meridian"}; do
270
+ for _cand in ${_npm_prefix:+"${_npm_prefix}/bin/meridian"} "/usr/local/bin/meridian"; do
270
271
  [[ -e "${_cand}" ]] || continue
271
272
  # Distinguish the launcher (node shim) from a self-referential CLI symlink:
272
273
  # the launcher never resolves to meridian-cli.sh.
@@ -275,11 +276,11 @@ for _cand in "/usr/local/bin/meridian" ${_npm_prefix:+"${_npm_prefix}/bin/meridi
275
276
  fi
276
277
  done
277
278
  if [[ -n "${_launcher}" ]]; then
278
- rm -f "${HOME}/.local/bin/meridian"
279
- ok "meridian-daemon → ~/.local/bin (meridian CLI = npm launcher at ${_launcher})"
279
+ ln -sfn "${_launcher}" "${HOME}/.local/bin/meridian"
280
+ ok "meridian-daemon + meridian → ~/.local/bin (meridian npm launcher at ${_launcher})"
280
281
  else
281
282
  ln -sfn "${APP_ROOT}/scripts/meridian-cli.sh" "${HOME}/.local/bin/meridian"
282
- ok "meridian-daemon + meridian → ~/.local/bin"
283
+ ok "meridian-daemon + meridian → ~/.local/bin (CLI; no npm launcher found)"
283
284
  fi
284
285
 
285
286
  # ── 4. Python venv + MLX deps ────────────────────────────────────────────────
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "meridian-agents"
7
- version = "1.20.1"
7
+ version = "1.22.0"
8
8
  description = "Meridian agents — hermes task linking and Jira progress updates for meridian.db"
9
9
  requires-python = ">=3.11"
10
10
  authors = [{ name = "Meridiona" }]
package/ui.tar.gz CHANGED
Binary file