@awebai/oats 0.35.2 → 0.35.4

package/docs/desktop.md

@@ -70,6 +70,23 @@ what is required, **Choose oats…** (pick the binary yourself — the choice
 persists), **Retry**, a docs link, and the copyable install command. The
 app never installs the CLI itself.
 
+### Launched from Finder: the login shell's PATH
+
+Opened from Finder or the Dock, an app inherits launchd's PATH
+(`/usr/bin:/bin:/usr/sbin:/sbin`), which has no Homebrew or nvm `node` for
+the CLI's `#!/usr/bin/env node`. At startup the Desktop therefore runs your
+login shell once (`$SHELL -ilc`, 3 s timeout) and puts its PATH in front of
+the inherited one, so the CLI probe, every `oats` call, a CLI picked with
+**Choose oats…**, and the tmux server and terminals the Desktop starts all run
+with your shell's PATH. Only PATH is taken from the shell, never the rest of
+its environment. If the shell fails, times out or prints no PATH, the
+inherited PATH stays: the backend's `/api/cli` reports `pathSource`
+(`login-shell` or `inherited`), `pathError` (why, or `null`) and
+`probePath` (the PATH the probe used), and the reason is logged at startup.
+A tmux server that was already running keeps its own environment; restart it
+(`tmux kill-server`, which ends its sessions) if its sessions should get the
+new PATH.
+
 ## Opening a workspace
 
 The app starts on the directory it was launched with (its own folder by

package/docs/release-notes/v0.35.3.md

@@ -0,0 +1,16 @@
+# OATS 0.35.3
+
+## Fixed
+
+- **A Desktop opened from Finder or the Dock finds the CLI's node**
+  (awebai/oats#468). Such a launch inherits launchd's PATH
+  (`/usr/bin:/bin:/usr/sbin:/sbin`). Discovery found the CLI through the
+  login shell, but the probe and every later call ran it with that PATH, so
+  its `#!/usr/bin/env node` failed on a Homebrew or nvm host, and every
+  workspace showed `E_CLI_UNAVAILABLE`. At startup the Desktop now runs the
+  login shell once (3 s timeout) and puts its PATH in front of the
+  inherited one, for the backend, every `oats` call, the probe, a CLI picked
+  with **Choose oats…**, and the tmux server it starts. Only PATH is taken,
+  never the rest of the shell's environment. If the shell fails, the
+  inherited PATH stays, and `/api/cli` says so (`pathSource`, `pathError`,
+  `probePath`). An already-running tmux server is left as it is.

package/docs/release-notes/v0.35.4.md

@@ -0,0 +1,31 @@
+# OATS 0.35.4
+
+## Fixed
+
+- **A Desktop workspace never waits silently on "Reading the deployment…",
+  and a folder that is not a deployment never drops the open ones**
+  (awebai/oats#461). With three or more deployments open, the third and later
+  ones were never read: the server started every deployment's reads at once
+  past the observer's two-read bound, and kept the refused ones on their
+  first "pending" forever. That is also why an empty deployment (no souls,
+  no instances) listed third never loaded; an empty answer is an
+  observation, shown as no instances. Deployments are now read two at a
+  time, each one every cycle. A launch from a folder that is not a
+  deployment (a parent such as `~/Agents` as the cwd or `--dir`), at a
+  moment when no saved deployment could be opened, saved that folder as the
+  whole open set; only deployments are saved now, and the saved set is
+  never replaced with nothing. Add workspace → Browse… on a folder without
+  `oats-local.yaml` is refused with an explanation and lists the
+  deployments in it (or the one it is inside) as one-click adds; setting up
+  a new deployment there is a secondary action. A workspace the Desktop's
+  server does not serve, or does not answer for within 45 s, shows an
+  error naming it, with Retry and Re-add workspace. Behaviour change in
+  the Desktop's own server: an explicit `?ws=` it does not serve (any id)
+  on `/api/panel` and `/api/agents` is now 404 `E_WORKSPACE_NOT_SERVED`
+  instead of the first workspace's answer.
+
+- **After upgrading from a version before 0.35.3, restart once a tmux
+  server that a Finder-launched Desktop started earlier** (awebai/oats#468).
+  Such a server keeps launchd's PATH for the sessions it starts. Restart it once to pick up the
+  new PATH. Restarting it ends the sessions in it, so do it when no instance
+  is running.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awebai/oats",
-  "version": "0.35.2",
+  "version": "0.35.4",
   "description": "OATS (Open Agent Team Specification) — durable souls, disposable instances, targetable capability packages, and the runtime-neutral oats CLI/kernel.",
   "keywords": [
     "agents",