@a5c-ai/babysitter-github 0.1.4 → 0.1.5-staging.20a61093

package/README.md

@@ -226,7 +226,7 @@ active process library before the cloud agent starts working.
 | Variable | Default | Description |
 |----------|---------|-------------|
 | `CLAUDE_PROJECT_DIR` | CWD | Project root directory (set by Copilot CLI) |
-| `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 |
 | `BABYSITTER_STATE_DIR` | `<cwd>/.a5c` | State directory for session data |
 
 ### SDK Version Pinning

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-end.ps1

@@ -30,7 +30,7 @@ if (-not $hasBabysitter) {
     }
 }
 
-$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-end-hook.log"
 New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
 

package/hooks/session-end.sh

@@ -32,7 +32,7 @@ if ! command -v babysitter &>/dev/null; then
   fi
 fi
 
-LOG_DIR="${BABYSITTER_LOG_DIR:-$PLUGIN_ROOT/.a5c/logs}"
+LOG_DIR="${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}"
 LOG_FILE="$LOG_DIR/babysitter-session-end-hook.log"
 
 mkdir -p "$LOG_DIR" 2>/dev/null

package/hooks/session-start.ps1

@@ -14,7 +14,7 @@ $ErrorActionPreference = "Stop"
 $PluginRoot = if ($env:COPILOT_PLUGIN_DIR) { $env:COPILOT_PLUGIN_DIR } else { Split-Path -Parent $PSScriptRoot }
 $MarkerFile = Join-Path $PluginRoot ".babysitter-install-attempted"
 
-$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
 PLUGIN_ROOT="${COPILOT_PLUGIN_DIR:-$(cd "$(dirname "$0")/.." && pwd)}"
 MARKER_FILE="${PLUGIN_ROOT}/.babysitter-install-attempted"
 
-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"
 mkdir -p "$LOG_DIR" 2>/dev/null
 

package/hooks/user-prompt-submitted.ps1

@@ -29,7 +29,7 @@ if (-not $hasBabysitter) {
     }
 }
 
-$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" }
 New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
 
 # Capture stdin

package/hooks/user-prompt-submitted.sh

@@ -24,7 +24,7 @@ if ! command -v babysitter &>/dev/null; then
   fi
 fi
 
-LOG_DIR="${BABYSITTER_LOG_DIR:-$PLUGIN_ROOT/.a5c/logs}"
+LOG_DIR="${BABYSITTER_LOG_DIR:-$HOME/.a5c/logs}"
 mkdir -p "$LOG_DIR" 2>/dev/null
 
 INPUT_FILE=$(mktemp 2>/dev/null || echo "/tmp/hook-user-prompt-submitted-$$.json")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-github",
-  "version": "0.1.4",
+  "version": "0.1.5-staging.20a61093",
   "description": "Babysitter orchestration plugin for GitHub Copilot CLI with lifecycle hooks and SDK-managed process-library bootstrapping",
   "scripts": {
     "test": "node scripts/sync-command-surfaces.js --check && node test/cloud-agent-install.test.js",
@@ -45,6 +45,6 @@
   },
   "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-github#readme",
   "dependencies": {
-    "@a5c-ai/babysitter-sdk": "0.0.187"
+    "@a5c-ai/babysitter-sdk": "0.0.188-staging.20a61093"
   }
 }

package/skills/babysit/SKILL.md

@@ -18,24 +18,21 @@ Read the SDK version from `versions.json` to ensure version compatibility:
 
 ```bash
 SDK_VERSION=$(node -e "try{console.log(JSON.parse(require('fs').readFileSync('${PLUGIN_ROOT}/versions.json','utf8')).sdkVersion||'latest')}catch{console.log('latest')}")
-sudo npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION
-# sudo is depending on the env and system
+CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"
 ```
 
-then use the CLI alias: CLI="babysitter"
-
-**Alternatively, use the CLI alias:** `CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"`
+If `babysitter` is already installed globally at the correct version, you may use `CLI="babysitter"` instead.
 
 ### jq
 
-make sure you have jq installed and available in the path. if not, install it.
+Make sure `jq` is installed and available in the path. If not, install it.
 
 ## Instructions
 
 Run the following command to get full orchestration instructions:
 
 ```bash
-babysitter instructions:babysit-skill --harness github-copilot --json
+$CLI instructions:babysit-skill --harness github-copilot --json
 ```
 
 Follow the instructions returned by the command above to orchestrate the run.
@@ -49,9 +46,9 @@ is ignored and cannot block or restart the session.
 Therefore, you MUST use **in-turn iteration**: run the full orchestration loop
 within a single session turn. The pattern is:
 
-1. `babysitter run:iterate --json` -- get pending actions
+1. `$CLI run:iterate --json` -- get pending actions
 2. For each pending action: execute it (run tasks, post results via `task:post`)
-3. `babysitter run:iterate --json` -- check for more pending actions
+3. `$CLI run:iterate --json` -- check for more pending actions
 4. Repeat steps 2-3 until run completes or reaches a breakpoint requiring user input
 5. If a breakpoint requires user input, ask the user and post the response, then continue iterating
 
@@ -63,7 +60,7 @@ the orchestration loop. The agent drives the loop directly by calling
 
 ```bash
 # Initial iterate
-RESULT=$(babysitter run:iterate --run-id "$RUN_ID" --json)
+RESULT=$($CLI run:iterate --run-id "$RUN_ID" --json)
 STATUS=$(echo "$RESULT" | jq -r '.status')
 
 while [ "$STATUS" != "completed" ] && [ "$STATUS" != "failed" ]; do
@@ -71,7 +68,7 @@ while [ "$STATUS" != "completed" ] && [ "$STATUS" != "failed" ]; do
   # ... execute tasks, post results ...
 
   # Iterate again
-  RESULT=$(babysitter run:iterate --run-id "$RUN_ID" --json)
+  RESULT=$($CLI run:iterate --run-id "$RUN_ID" --json)
   STATUS=$(echo "$RESULT" | jq -r '.status')
 done
 ```

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.20a61093"
 }