@a5c-ai/babysitter-cursor 0.1.4 → 0.1.5-staging.6342f2b1

package/README.md

@@ -34,20 +34,10 @@ Install through Cursor's marketplace UI using the repo-root
 2. Open the marketplace entry named **a5c-ai**
 3. Install the plugin named **babysitter**
 
-### Via Babysitter plugin manager
-
-This path installs the Babysitter plugin package named
-`babysitter-cursor` from the SDK marketplace, not the Cursor UI plugin
-entry:
-
-```bash
-babysitter plugin:install babysitter-cursor --marketplace-name a5c-ai --global
-```
-
-### Workspace installation
+### Via Babysitter harness install
 
 ```bash
-babysitter plugin:install babysitter-cursor --marketplace-name a5c-ai --project
+babysitter harness:install-plugin cursor
 ```
 
 If the workspace does not already have an active process-library binding, the
@@ -91,10 +81,10 @@ ln -s "$(pwd)/plugins/babysitter-cursor" ~/.cursor/plugins/local/babysitter-curs
 babysitter-cursor uninstall
 ```
 
-Or via the plugin manager:
+Or via npm:
 
 ```bash
-babysitter plugin:uninstall babysitter-cursor --global
+npm uninstall -g @a5c-ai/babysitter-cursor
 ```
 
 ## Plugin Structure (Directory Layout)
@@ -294,7 +284,7 @@ behavior within sessions.
 | `CURSOR_API_KEY` | -- | API key for headless CLI mode (required) |
 | `CURSOR_PLUGIN_ROOT` | Plugin directory | Plugin root directory |
 | `BABYSITTER_STATE_DIR` | `<cwd>/.a5c` | State directory for session data |
-| `BABYSITTER_LOG_DIR` | `<plugin>/.a5c/logs` | Log output directory |
+| `BABYSITTER_LOG_DIR` | `~/.a5c/logs` | Log output directory override; default is the user-global Babysitter log root |
 
 ### SDK Version Pinning
 
@@ -362,9 +352,7 @@ The repo-root Cursor marketplace manifest lives at `/.cursor-plugin/marketplace.
 ### User Commands
 
 ```bash
-babysitter plugin:add-marketplace --marketplace-url https://github.com/a5c-ai/babysitter --marketplace-path plugins/a5c/marketplace/marketplace.json --global
-babysitter plugin:list-plugins --marketplace-name a5c-ai --global
-babysitter plugin:install babysitter-cursor --marketplace-name a5c-ai --global
+babysitter harness:install-plugin cursor
 ```
 
 ## Troubleshooting
@@ -378,7 +366,7 @@ session health:
 $doctor
 ```
 
-Also check log output in `<plugin-root>/.a5c/logs/`:
+Also check log output in `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/`:
 
 - `babysitter-session-start-hook.log`
 - `babysitter-stop-hook.log`

package/commands/doctor.md

@@ -177,13 +177,13 @@ Mark as PASS if no issues. Mark as WARN if runaway loops or stale sessions detec
 **Goal:** Analyze babysitter log files for errors, warnings, and stop hook decisions.
 
 Read the last 50 lines of each of these log files (if they exist):
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/hooks.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook-stderr.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-session-start-hook.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-session-start-hook-stderr.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter.log`
-- `$HOME/.a5c/logs/` and relevant logs and run/session specific logs there
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/hooks.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook-stderr.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-session-start-hook.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-session-start-hook-stderr.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/` and relevant run/session specific logs there
 
 
 For each log file:
@@ -285,7 +285,7 @@ The hooks delegate to the `babysitter` CLI. Check if it is available:
 Check whether the stop hook has actually been invoked during this run's lifetime:
 
 **From log files:**
-- Read `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook.log` (if it exists).
+- Read `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook.log` (if it exists).
 - Count the number of "Hook script invoked" lines. This is the total invocation count.
 - Count the number of "CLI exit code=" lines and extract exit codes.
 - If the log file does not exist or has zero invocations, the stop hook has NOT been running.
@@ -297,7 +297,7 @@ Check whether the stop hook has actually been invoked during this run's lifetime
 - If no STOP_HOOK_INVOKED events exist in the journal, note that the stop hook has not recorded any decisions for this run.
 
 **From stderr:**
-- Read `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook-stderr.log`.
+- Read `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook-stderr.log`.
 - If it contains error output, display it and diagnose:
   - "command not found" or exit code 127 → CLI not installed (see 10c)
   - "MODULE_NOT_FOUND" or "Cannot find module" → SDK package corrupted or not built

package/hooks/session-start.ps1

@@ -18,7 +18,7 @@ $MarkerFile = Join-Path $PluginRoot ".babysitter-install-attempted"
 $env:CURSOR_PLUGIN_ROOT = $PluginRoot
 $env:BABYSITTER_STATE_DIR = $StateDir
 
-$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $PluginRoot ".a5c\logs" }
+$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $HOME ".a5c\logs" }
 $LogFile = Join-Path $LogDir "babysitter-session-start-hook.log"
 New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
 

package/hooks/session-start.sh

@@ -15,7 +15,7 @@ set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PLUGIN_ROOT="$(cd "${SCRIPT_DIR}/.." && pwd)"
 STATE_DIR="${BABYSITTER_STATE_DIR:-${PWD}/.a5c}"
-LOG_DIR="${BABYSITTER_LOG_DIR:-$PLUGIN_ROOT/.a5c/logs}"
+LOG_DIR="${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}"
 LOG_FILE="$LOG_DIR/babysitter-session-start-hook.log"
 
 export CURSOR_PLUGIN_ROOT="${CURSOR_PLUGIN_ROOT:-${PLUGIN_ROOT}}"

package/hooks/stop-hook.ps1

@@ -15,7 +15,7 @@ $StateDir = if ($env:BABYSITTER_STATE_DIR) { $env:BABYSITTER_STATE_DIR } else {
 $env:CURSOR_PLUGIN_ROOT = $PluginRoot
 $env:BABYSITTER_STATE_DIR = $StateDir
 
-$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $PluginRoot ".a5c\logs" }
+$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $HOME ".a5c\logs" }
 $LogFile = Join-Path $LogDir "babysitter-stop-hook.log"
 New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
 

package/hooks/stop-hook.sh

@@ -13,7 +13,7 @@ set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PLUGIN_ROOT="$(cd "${SCRIPT_DIR}/.." && pwd)"
 STATE_DIR="${BABYSITTER_STATE_DIR:-${PWD}/.a5c}"
-LOG_DIR="${BABYSITTER_LOG_DIR:-$PLUGIN_ROOT/.a5c/logs}"
+LOG_DIR="${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}"
 LOG_FILE="$LOG_DIR/babysitter-stop-hook.log"
 
 export CURSOR_PLUGIN_ROOT="${CURSOR_PLUGIN_ROOT:-${PLUGIN_ROOT}}"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-cursor",
-  "version": "0.1.4",
+  "version": "0.1.5-staging.6342f2b1",
   "description": "Babysitter orchestration plugin for Cursor IDE with SDK-managed process-library bootstrapping and in-turn iteration model",
   "scripts": {
     "test": "node scripts/sync-command-surfaces.js --check",
@@ -44,6 +44,6 @@
   },
   "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-cursor#readme",
   "dependencies": {
-    "@a5c-ai/babysitter-sdk": "0.0.187"
+    "@a5c-ai/babysitter-sdk": "0.0.188-staging.6342f2b1"
   }
 }

package/skills/doctor/SKILL.md

@@ -178,13 +178,13 @@ Mark as PASS if no issues. Mark as WARN if runaway loops or stale sessions detec
 **Goal:** Analyze babysitter log files for errors, warnings, and stop hook decisions.
 
 Read the last 50 lines of each of these log files (if they exist):
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/hooks.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook-stderr.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-session-start-hook.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-session-start-hook-stderr.log`
-- `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter.log`
-- `$HOME/.a5c/logs/` and relevant logs and run/session specific logs there
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/hooks.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook-stderr.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-session-start-hook.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-session-start-hook-stderr.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter.log`
+- `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/` and relevant run/session specific logs there
 
 
 For each log file:
@@ -286,7 +286,7 @@ The hooks delegate to the `babysitter` CLI. Check if it is available:
 Check whether the stop hook has actually been invoked during this run's lifetime:
 
 **From log files:**
-- Read `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook.log` (if it exists).
+- Read `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook.log` (if it exists).
 - Count the number of "Hook script invoked" lines. This is the total invocation count.
 - Count the number of "CLI exit code=" lines and extract exit codes.
 - If the log file does not exist or has zero invocations, the stop hook has NOT been running.
@@ -298,7 +298,7 @@ Check whether the stop hook has actually been invoked during this run's lifetime
 - If no STOP_HOOK_INVOKED events exist in the journal, note that the stop hook has not recorded any decisions for this run.
 
 **From stderr:**
-- Read `$CLAUDE_PLUGIN_ROOT/.a5c/logs/babysitter-stop-hook-stderr.log`.
+- Read `${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}/babysitter-stop-hook-stderr.log`.
 - If it contains error output, display it and diagnose:
   - "command not found" or exit code 127 → CLI not installed (see 10c)
   - "MODULE_NOT_FOUND" or "Cannot find module" → SDK package corrupted or not built

package/versions.json

@@ -1,3 +1,3 @@
 {
-  "sdkVersion": "0.0.187"
+  "sdkVersion": "0.0.188-staging.6342f2b1"
 }