@a5c-ai/babysitter-github 5.0.1-staging.b5c14f2a → 5.0.1-staging.ca65e187

package/skills/project-install/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: project-install
+description: Set up a project for babysitting. Guides you through onboarding a new or existing project — researches the codebase, interviews you about goals and workflows, builds the project profile, installs the best tools, and optionally configures CI/CD integration.
+---
+
+# project-install
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+Before using the process library, resolve the active library root through the SDK CLI. If no binding exists yet, initialize the shared global SDK binding with:
+
+```bash
+babysitter process-library:active --json
+```
+
+Then use the `cradle/project-install` process from the active process library.
+
+When the run completes, end with a friendly message that includes a polite and humorous ask to star the repo on GitHub: https://github.com/a5c-ai/babysitter

package/skills/resume/SKILL.md

@@ -5,5 +5,5 @@ description: Resume orchestrating of a babysitter run. use this command to resum
 
 # resume
 
-Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). to resume a run.
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). to resume a run.
 if no run was given, discover the runs and suggest which incomplete run to resume based on the run's status, inputs, process , etc.

package/skills/retrospect/SKILL.md

@@ -5,52 +5,52 @@ description: Analysis for a run and its results, process, suggestions for proces
 
 # retrospect
 
-Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
-
-create and run a retrospect process:
-
-### Run Selection
-
-- `--all` or "all runs": list all completed/failed runs and analyze collectively
-- Multiple run IDs: analyze each specified run
-- Single run ID or no ID: existing behavior (latest run)
-- In interactive mode with no run specified: ask user whether to analyze latest, select specific runs, or all runs
-
-### Cross-Run Analysis (multi-run mode)
-
-When analyzing multiple runs, the retrospect process should additionally cover:
-- Common failure patterns across runs
-- Velocity trends (tasks/time across runs)
-- Process evolution (how processes changed)
-- Repeated breakpoint patterns
-- Aggregate quality metrics
-
-implementations notes (for the process):
-- The process should analyze the run, the process that was followed, and provide suggestions for improvements, optimizations, and fixes.
-- The process should such have many breakpoints where the user can steer the process, provide feedback, and make decisions about how to proceed with the retrospect.
-- The process should be designed to be flexible and adaptable to different types of runs, projects, and goals, and should be able to provide insights and suggestions that are relevant and actionable for the user. (modification to the process, skills, etc.)
-- The process should be designed to be iterative, allowing the user to go through multiple rounds of analysis and improvement, and should be able to track the changes and improvements made over time.
-- The process should cover:
-    - Analysis of the run and its results, including what went well, what didn't go well, and what could be improved.
-    - Analysis of the process that was followed, including what steps were taken, what tools were used, and how effective they were.
-    - Suggestions for improvements, optimizations, and fixes for both the run and the process.
-    - Implementing the improvements, optimizations, and fixes, and tracking the changes made over time.
-### Cleanup Suggestion
-
-After retrospect analysis, suggest running `/babysitter:cleanup` to clean up old run data and reclaim disk space.
-
-    - Ending by explicitly prompting the user to contribute back -- even just reporting an issue is valuable, they don't need to implement the fix themselves. After analysis, display a clear call-to-action:
-
-      "You've identified [specific insight/improvement]. This could help other babysitter users too. Run `/babysitter:contrib` to share it upstream -- you can either report it as an issue or submit a PR with the fix."
-
-      Route to the specific contrib workflow based on what the user wants to do:
-
-      **Just reporting (no code changes needed):**
-      - Found a bug or weakness in a process -> `/babysitter:contrib bug report: [description of what went wrong]`
-      - Found missing or confusing documentation -> `/babysitter:contrib documentation question: [what was unclear]`
-      - Have an idea for improvement but don't want to implement it -> `/babysitter:contrib feature request: [description]`
-
-      **Contributing code changes:**
-      - Process/skill/agent improvements -> `/babysitter:contrib library contribution: [description]`
-      - Bug fixes in SDK or CLI -> `/babysitter:contrib bugfix: [description]`
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+create and run a retrospect process:
+
+### Run Selection
+
+- `--all` or "all runs": list all completed/failed runs and analyze collectively
+- Multiple run IDs: analyze each specified run
+- Single run ID or no ID: existing behavior (latest run)
+- In interactive mode with no run specified: ask user whether to analyze latest, select specific runs, or all runs
+
+### Cross-Run Analysis (multi-run mode)
+
+When analyzing multiple runs, the retrospect process should additionally cover:
+- Common failure patterns across runs
+- Velocity trends (tasks/time across runs)
+- Process evolution (how processes changed)
+- Repeated breakpoint patterns
+- Aggregate quality metrics
+
+implementations notes (for the process):
+- The process should analyze the run, the process that was followed, and provide suggestions for improvements, optimizations, and fixes.
+- The process should such have many breakpoints where the user can steer the process, provide feedback, and make decisions about how to proceed with the retrospect.
+- The process should be designed to be flexible and adaptable to different types of runs, projects, and goals, and should be able to provide insights and suggestions that are relevant and actionable for the user. (modification to the process, skills, etc.)
+- The process should be designed to be iterative, allowing the user to go through multiple rounds of analysis and improvement, and should be able to track the changes and improvements made over time.
+- The process should cover:
+    - Analysis of the run and its results, including what went well, what didn't go well, and what could be improved.
+    - Analysis of the process that was followed, including what steps were taken, what tools were used, and how effective they were.
+    - Suggestions for improvements, optimizations, and fixes for both the run and the process.
+    - Implementing the improvements, optimizations, and fixes, and tracking the changes made over time.
+### Cleanup Suggestion
+
+After retrospect analysis, suggest running `/babysitter:cleanup` to clean up old run data and reclaim disk space.
+
+    - Ending by explicitly prompting the user to contribute back -- even just reporting an issue is valuable, they don't need to implement the fix themselves. After analysis, display a clear call-to-action:
+
+      "You've identified [specific insight/improvement]. This could help other babysitter users too. Run `/babysitter:contrib` to share it upstream -- you can either report it as an issue or submit a PR with the fix."
+
+      Route to the specific contrib workflow based on what the user wants to do:
+
+      **Just reporting (no code changes needed):**
+      - Found a bug or weakness in a process -> `/babysitter:contrib bug report: [description of what went wrong]`
+      - Found missing or confusing documentation -> `/babysitter:contrib documentation question: [what was unclear]`
+      - Have an idea for improvement but don't want to implement it -> `/babysitter:contrib feature request: [description]`
+
+      **Contributing code changes:**
+      - Process/skill/agent improvements -> `/babysitter:contrib library contribution: [description]`
+      - Bug fixes in SDK or CLI -> `/babysitter:contrib bugfix: [description]`
       - Plugin instruction improvements -> `/babysitter:contrib library contribution: improved [plugin-name] [install|configure|uninstall] instructions`

package/skills/user-install/SKILL.md

@@ -5,8 +5,8 @@ description: Set up babysitter for yourself. Guides you through onboarding — i
 
 # user-install
 
-Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
-
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
 Before using the process library, resolve the active library root through the SDK CLI. If no binding exists yet, initialize the shared global SDK binding with:
 
 ```bash
@@ -14,5 +14,5 @@ babysitter process-library:active --json
 ```
 
 Then use the `cradle/user-install` process from the active process library.
-
+
 When the run completes, end with a friendly message that includes a polite and humorous ask to star the repo on GitHub: https://github.com/a5c-ai/babysitter

package/skills/yolo/SKILL.md

@@ -0,0 +1,8 @@
+---
+name: yolo
+description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run.
+---
+
+# yolo
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). but without any user interaction or breakpoints in the run.

package/versions.json

@@ -1,3 +1,4 @@
 {
-  "sdkVersion": "5.0.1-staging.b5c14f2a"
+  "sdkVersion": "5.0.1-staging.ca65e187",
+  "extensionVersion": "5.0.0"
 }

package/.github/plugin.json

@@ -1,25 +0,0 @@
-{
-  "name": "babysitter",
-  "version": "0.1.0",
-  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval -- powered by the Babysitter SDK",
-  "author": { "name": "a5c.ai", "email": "support@a5c.ai" },
-  "license": "MIT",
-  "skills": "skills/",
-  "hooks": "hooks.json",
-  "commands": "commands/",
-  "agents": "AGENTS.md",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/a5c-ai/babysitter"
-  },
-  "keywords": [
-    "orchestration",
-    "workflow",
-    "automation",
-    "event-sourced",
-    "hooks",
-    "github-copilot",
-    "agent",
-    "LLM"
-  ]
-}

package/hooks/session-end.ps1

@@ -1,69 +0,0 @@
-# Babysitter Session End Hook for GitHub Copilot CLI (PowerShell)
-# Cleanup and logging on session exit.
-#
-# NOTE: Unlike Claude Code's Stop hook, sessionEnd output is IGNORED by
-# Copilot CLI. This hook cannot block session exit or drive an orchestration
-# loop. It is purely for cleanup and logging.
-
-$ErrorActionPreference = "Continue"
-
-$PluginRoot = if ($env:COPILOT_PLUGIN_DIR) { $env:COPILOT_PLUGIN_DIR } else { Split-Path -Parent $PSScriptRoot }
-
-# Resolve babysitter CLI
-$hasBabysitter = [bool](Get-Command babysitter -ErrorAction SilentlyContinue)
-$useFallback = $false
-
-if (-not $hasBabysitter) {
-    $localBin = Join-Path $env:USERPROFILE ".local\bin\babysitter.cmd"
-    if (Test-Path $localBin) {
-        $env:PATH = "$(Split-Path $localBin);$env:PATH"
-        $hasBabysitter = $true
-    } else {
-        $versionsFile = Join-Path $PluginRoot "versions.json"
-        try {
-            $SdkVersion = (Get-Content $versionsFile -Raw | ConvertFrom-Json).sdkVersion
-            if (-not $SdkVersion) { $SdkVersion = "latest" }
-        } catch {
-            $SdkVersion = "latest"
-        }
-        $useFallback = $true
-    }
-}
-
-$GlobalRoot = if ($env:BABYSITTER_GLOBAL_STATE_DIR) { $env:BABYSITTER_GLOBAL_STATE_DIR } else { Join-Path $HOME ".a5c" }
-$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $GlobalRoot "logs" }
-$LogFile = Join-Path $LogDir "babysitter-session-end-hook.log"
-New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
-
-function Write-Blog {
-    param([string]$Message)
-    $ts = (Get-Date).ToUniversalTime().ToString("yyyy-MM-ddTHH:mm:ssZ")
-    Add-Content -Path $LogFile -Value "[INFO] $ts $Message" -ErrorAction SilentlyContinue
-}
-
-Write-Blog "Hook script invoked"
-Write-Blog "PLUGIN_ROOT=$PluginRoot"
-
-# Capture stdin
-$InputFile = [System.IO.Path]::GetTempFileName()
-$input | Out-File -FilePath $InputFile -Encoding utf8
-
-Write-Blog "Hook input received"
-
-$stderrLog = Join-Path $LogDir "babysitter-session-end-hook-stderr.log"
-
-try {
-    if ($useFallback) {
-        Get-Content $InputFile | & npx -y "@a5c-ai/babysitter-sdk@$SdkVersion" hook:run --hook-type session-end --harness github-copilot --plugin-root $PluginRoot --json 2>$stderrLog | Out-Null
-    } elseif ($hasBabysitter) {
-        Get-Content $InputFile | & babysitter hook:run --hook-type session-end --harness github-copilot --plugin-root $PluginRoot --json 2>$stderrLog | Out-Null
-    }
-} catch {
-    Write-Blog "Hook error: $_"
-}
-
-Write-Blog "Session end hook complete"
-
-Remove-Item $InputFile -Force -ErrorAction SilentlyContinue
-
-exit 0

package/hooks/session-end.sh

@@ -1,54 +0,0 @@
-#!/bin/bash
-# Babysitter Session End Hook for GitHub Copilot CLI
-# Cleanup and logging on session exit.
-#
-# NOTE: Unlike Claude Code's Stop hook, sessionEnd output is IGNORED by
-# Copilot CLI. This hook cannot block session exit or drive an orchestration
-# loop. It is purely for cleanup and logging.
-#
-# Protocol:
-#   Input:  JSON via stdin (session context)
-#   Output: IGNORED by Copilot CLI
-#   Exit 0: success (exit code also ignored)
-
-set -uo pipefail
-
-PLUGIN_ROOT="${COPILOT_PLUGIN_DIR:-$(cd "$(dirname "$0")/.." && pwd)}"
-
-if ! command -v babysitter &>/dev/null; then 
-  # No CLI available — exit 0 (no-op, proceed with original command)
-  exit 0
-fi
-
-GLOBAL_ROOT="${BABYSITTER_GLOBAL_STATE_DIR:-$HOME/.a5c}"
-LOG_DIR="${BABYSITTER_LOG_DIR:-${GLOBAL_ROOT}/logs}"
-LOG_FILE="$LOG_DIR/babysitter-session-end-hook.log"
-
-mkdir -p "$LOG_DIR" 2>/dev/null
-
-# Structured logging helper
-blog() {
-  local msg="$1"
-  local ts
-  ts="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
-  echo "[INFO] $ts $msg" >> "$LOG_FILE" 2>/dev/null
-  babysitter log --type hook --label "hook:session-end" --message "$msg" --source shell-hook 2>/dev/null || true
-}
-
-blog "Hook script invoked"
-blog "PLUGIN_ROOT=$PLUGIN_ROOT"
-
-# Capture stdin so we can log size and pass to CLI
-INPUT_FILE=$(mktemp 2>/dev/null || echo "/tmp/hook-session-end-$$.json")
-cat > "$INPUT_FILE"
-
-blog "Hook input received ($(wc -c < "$INPUT_FILE") bytes)"
-
-# Run cleanup/logging via CLI; output is ignored by Copilot CLI
-babysitter hook:run --hook-type session-end --harness github-copilot --plugin-root "$PLUGIN_ROOT" --json < "$INPUT_FILE" 2>"$LOG_DIR/babysitter-session-end-hook-stderr.log" || true
-
-blog "Session end hook complete"
-
-rm -f "$INPUT_FILE" 2>/dev/null
-
-exit 0

package/hooks/session-start.ps1

@@ -1,111 +0,0 @@
-# Babysitter Session Start Hook for GitHub Copilot CLI (PowerShell)
-# Ensures the babysitter SDK CLI is installed (from versions.json sdkVersion),
-# then delegates to the TypeScript handler.
-#
-# Protocol:
-#   Input:  JSON via stdin (contains session_id, cwd, etc.)
-#   Output: JSON via stdout ({} on success)
-#   Stderr: debug/log output only
-#   Exit 0: success
-#   Exit 2: block (fatal error)
-
-$ErrorActionPreference = "Stop"
-
-$PluginRoot = if ($env:COPILOT_PLUGIN_DIR) { $env:COPILOT_PLUGIN_DIR } else { Split-Path -Parent $PSScriptRoot }
-$MarkerFile = Join-Path $PluginRoot ".babysitter-install-attempted"
-
-$GlobalRoot = if ($env:BABYSITTER_GLOBAL_STATE_DIR) { $env:BABYSITTER_GLOBAL_STATE_DIR } else { Join-Path $HOME ".a5c" }
-$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $GlobalRoot "logs" }
-$LogFile = Join-Path $LogDir "babysitter-session-start-hook.log"
-New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
-
-function Write-Blog {
-    param([string]$Message)
-    $ts = (Get-Date).ToUniversalTime().ToString("yyyy-MM-ddTHH:mm:ssZ")
-    Add-Content -Path $LogFile -Value "[INFO] $ts $Message" -ErrorAction SilentlyContinue
-    if (Get-Command babysitter -ErrorAction SilentlyContinue) {
-        & babysitter log --type hook --label "hook:session-start" --message $Message --source shell-hook 2>$null
-    }
-}
-
-Write-Blog "Hook script invoked"
-Write-Blog "PLUGIN_ROOT=$PluginRoot"
-
-# Get required SDK version from versions.json
-$versionsFile = Join-Path $PluginRoot "versions.json"
-try {
-    $SdkVersion = (Get-Content $versionsFile -Raw | ConvertFrom-Json).sdkVersion
-    if (-not $SdkVersion) { $SdkVersion = "latest" }
-} catch {
-    $SdkVersion = "latest"
-}
-
-function Install-Sdk {
-    param([string]$TargetVersion)
-    try {
-        & npm i -g "@a5c-ai/babysitter-sdk@$TargetVersion" --loglevel=error 2>$null
-        if ($LASTEXITCODE -eq 0) {
-            Write-Blog "Installed SDK globally ($TargetVersion)"
-            return $true
-        }
-    } catch {}
-    try {
-        $prefix = Join-Path $env:USERPROFILE ".local"
-        & npm i -g "@a5c-ai/babysitter-sdk@$TargetVersion" --prefix $prefix --loglevel=error 2>$null
-        if ($LASTEXITCODE -eq 0) {
-            $env:PATH = "$prefix\bin;$env:PATH"
-            Write-Blog "Installed SDK to user prefix ($TargetVersion)"
-            return $true
-        }
-    } catch {}
-    return $false
-}
-
-# Check if babysitter CLI exists and if version matches
-$NeedsInstall = $false
-if (Get-Command babysitter -ErrorAction SilentlyContinue) {
-    $CurrentVersion = & babysitter --version 2>$null
-    if ($CurrentVersion -ne $SdkVersion) {
-        Write-Blog "SDK version mismatch: installed=$CurrentVersion, required=$SdkVersion"
-        $NeedsInstall = $true
-    } else {
-        Write-Blog "SDK version OK: $CurrentVersion"
-    }
-} else {
-    Write-Blog "SDK CLI not found, will install"
-    $NeedsInstall = $true
-}
-
-# Install/upgrade if needed (only attempt once per plugin version)
-if ($NeedsInstall -and -not (Test-Path $MarkerFile)) {
-    Install-Sdk $SdkVersion | Out-Null
-    Set-Content -Path $MarkerFile -Value $SdkVersion -ErrorAction SilentlyContinue
-}
-
-# If still not available after install attempt, try npx as last resort
-$useFallback = $false
-if (-not (Get-Command babysitter -ErrorAction SilentlyContinue)) {
-    Write-Blog "CLI not found after install, using npx fallback"
-    $useFallback = $true
-}
-
-# Capture stdin
-$InputFile = [System.IO.Path]::GetTempFileName()
-$input | Out-File -FilePath $InputFile -Encoding utf8
-
-Write-Blog "Hook input received"
-
-$stderrLog = Join-Path $LogDir "babysitter-session-start-hook-stderr.log"
-
-if ($useFallback) {
-    $Result = Get-Content $InputFile | & npx -y "@a5c-ai/babysitter-sdk@$SdkVersion" hook:run --hook-type session-start --harness github-copilot --plugin-root $PluginRoot --json 2>$stderrLog
-} else {
-    $Result = Get-Content $InputFile | & babysitter hook:run --hook-type session-start --harness github-copilot --plugin-root $PluginRoot --json 2>$stderrLog
-}
-$ExitCode = $LASTEXITCODE
-
-Write-Blog "CLI exit code=$ExitCode"
-
-Remove-Item $InputFile -Force -ErrorAction SilentlyContinue
-Write-Output $Result
-exit $ExitCode

package/hooks/session-start.sh

@@ -1,101 +0,0 @@
-#!/bin/bash
-# Babysitter Session Start Hook for GitHub Copilot CLI
-# Ensures the babysitter SDK CLI is installed (from versions.json sdkVersion),
-# then delegates to the TypeScript handler.
-#
-# Protocol:
-#   Input:  JSON via stdin (contains session_id, cwd, etc.)
-#   Output: JSON via stdout ({} on success)
-#   Stderr: debug/log output only
-#   Exit 0: success
-#   Exit 2: block (fatal error)
-
-set -euo pipefail
-
-PLUGIN_ROOT="${COPILOT_PLUGIN_DIR:-$(cd "$(dirname "$0")/.." && pwd)}"
-MARKER_FILE="${PLUGIN_ROOT}/.babysitter-install-attempted"
-
-GLOBAL_ROOT="${BABYSITTER_GLOBAL_STATE_DIR:-$HOME/.a5c}"
-LOG_DIR="${BABYSITTER_LOG_DIR:-${GLOBAL_ROOT}/logs}"
-LOG_FILE="$LOG_DIR/babysitter-session-start-hook.log"
-mkdir -p "$LOG_DIR" 2>/dev/null
-
-# Structured logging helper -- writes to both local and global log
-blog() {
-  local msg="$1"
-  local ts
-  ts="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
-  echo "[INFO] $ts $msg" >> "$LOG_FILE" 2>/dev/null
-  # Use CLI structured logging when available; fall back to direct append
-  if command -v babysitter &>/dev/null; then
-    babysitter log --type hook --label "hook:session-start" --message "$msg" --source shell-hook 2>/dev/null || true
-  fi
-}
-
-blog "Hook script invoked"
-blog "PLUGIN_ROOT=$PLUGIN_ROOT"
-
-# Get required SDK version from versions.json
-SDK_VERSION=$(node -e "try{console.log(JSON.parse(require('fs').readFileSync('${PLUGIN_ROOT}/versions.json','utf8')).sdkVersion||'latest')}catch{console.log('latest')}" 2>/dev/null || echo "latest")
-
-# Function to install/upgrade SDK
-install_sdk() {
-  local target_version="$1"
-  # Try global install first, fall back to user-local if permissions fail
-  if npm i -g "@a5c-ai/babysitter-sdk@${target_version}" --loglevel=error 2>/dev/null; then
-    blog "Installed SDK globally (${target_version})"
-    return 0
-  else
-    # Global install failed (permissions) -- try user-local prefix
-    if npm i -g "@a5c-ai/babysitter-sdk@${target_version}" --prefix "$HOME/.local" --loglevel=error 2>/dev/null; then
-      export PATH="$HOME/.local/bin:$PATH"
-      blog "Installed SDK to user prefix (${target_version})"
-      return 0
-    fi
-  fi
-  return 1
-}
-
-# Check if babysitter CLI exists and if version matches
-NEEDS_INSTALL=false
-if command -v babysitter &>/dev/null; then
-  CURRENT_VERSION=$(babysitter --version 2>/dev/null || echo "unknown")
-  if [ "$CURRENT_VERSION" != "$SDK_VERSION" ]; then
-    blog "SDK version mismatch: installed=${CURRENT_VERSION}, required=${SDK_VERSION}"
-    NEEDS_INSTALL=true
-  else
-    blog "SDK version OK: ${CURRENT_VERSION}"
-  fi
-else
-  blog "SDK CLI not found, will install"
-  NEEDS_INSTALL=true
-fi
-
-# Install/upgrade if needed (only attempt once per plugin version)
-if [ "$NEEDS_INSTALL" = true ] && [ ! -f "$MARKER_FILE" ]; then
-  install_sdk "$SDK_VERSION"
-  echo "$SDK_VERSION" > "$MARKER_FILE" 2>/dev/null
-fi
-
-# If still not available after install attempt, try npx as last resort
-if ! command -v babysitter &>/dev/null; then
-  blog "CLI not found after install, using npx fallback"
-  babysitter() { npx -y "@a5c-ai/babysitter-sdk@${SDK_VERSION}" "$@"; }
-  export -f babysitter
-fi
-
-# Capture stdin to a temp file so the CLI receives a clean EOF
-# (piping /dev/stdin directly can keep the Node.js event loop alive)
-INPUT_FILE=$(mktemp 2>/dev/null || echo "/tmp/hook-session-start-$$.json")
-cat > "$INPUT_FILE"
-
-blog "Hook input received ($(wc -c < "$INPUT_FILE") bytes)"
-
-RESULT=$(babysitter hook:run --hook-type session-start --harness github-copilot --plugin-root "$PLUGIN_ROOT" --json < "$INPUT_FILE" 2>"$LOG_DIR/babysitter-session-start-hook-stderr.log")
-EXIT_CODE=$?
-
-blog "CLI exit code=$EXIT_CODE"
-
-rm -f "$INPUT_FILE" 2>/dev/null
-printf '%s\n' "$RESULT"
-exit $EXIT_CODE

package/hooks/user-prompt-submitted.ps1

@@ -1,52 +0,0 @@
-# Babysitter userPromptSubmitted Hook for GitHub Copilot CLI (PowerShell)
-# Applies density-filter compression to long user prompts.
-#
-# NOTE: Output from this hook is IGNORED by Copilot CLI.
-# This hook is for logging and side-effects only.
-
-$ErrorActionPreference = "Continue"
-
-$PluginRoot = if ($env:COPILOT_PLUGIN_DIR) { $env:COPILOT_PLUGIN_DIR } else { Split-Path -Parent $PSScriptRoot }
-
-# Resolve babysitter CLI
-$hasBabysitter = [bool](Get-Command babysitter -ErrorAction SilentlyContinue)
-$useFallback = $false
-
-if (-not $hasBabysitter) {
-    $localBin = Join-Path $env:USERPROFILE ".local\bin\babysitter.cmd"
-    if (Test-Path $localBin) {
-        $env:PATH = "$(Split-Path $localBin);$env:PATH"
-        $hasBabysitter = $true
-    } else {
-        $versionsFile = Join-Path $PluginRoot "versions.json"
-        try {
-            $SdkVersion = (Get-Content $versionsFile -Raw | ConvertFrom-Json).sdkVersion
-            if (-not $SdkVersion) { $SdkVersion = "latest" }
-        } catch {
-            $SdkVersion = "latest"
-        }
-        $useFallback = $true
-    }
-}
-
-$GlobalRoot = if ($env:BABYSITTER_GLOBAL_STATE_DIR) { $env:BABYSITTER_GLOBAL_STATE_DIR } else { Join-Path $HOME ".a5c" }
-$LogDir = if ($env:BABYSITTER_LOG_DIR) { $env:BABYSITTER_LOG_DIR } else { Join-Path $GlobalRoot "logs" }
-New-Item -ItemType Directory -Path $LogDir -Force -ErrorAction SilentlyContinue | Out-Null
-
-# Capture stdin
-$InputFile = [System.IO.Path]::GetTempFileName()
-$input | Out-File -FilePath $InputFile -Encoding utf8
-
-$stderrLog = Join-Path $LogDir "babysitter-user-prompt-submitted-hook-stderr.log"
-
-try {
-    if ($useFallback) {
-        Get-Content $InputFile | & npx -y "@a5c-ai/babysitter-sdk@$SdkVersion" hook:run --hook-type user-prompt-submitted --harness github-copilot --json 2>$stderrLog | Out-Null
-    } elseif ($hasBabysitter) {
-        Get-Content $InputFile | & babysitter hook:run --hook-type user-prompt-submitted --harness github-copilot --json 2>$stderrLog | Out-Null
-    }
-} catch {}
-
-Remove-Item $InputFile -Force -ErrorAction SilentlyContinue
-
-exit 0

package/hooks/user-prompt-submitted.sh

@@ -1,31 +0,0 @@
-#!/bin/bash
-# Babysitter userPromptSubmitted Hook for GitHub Copilot CLI
-# Applies density-filter compression to long user prompts.
-# Delegates to SDK CLI: babysitter hook:run --hook-type user-prompt-submitted
-#
-# NOTE: Output from this hook is IGNORED by Copilot CLI.
-# This hook is for logging and side-effects only.
-
-PLUGIN_ROOT="${COPILOT_PLUGIN_DIR:-$(cd "$(dirname "$0")/.." && pwd)}"
-
-if ! command -v babysitter &>/dev/null; then 
-  # No CLI available — exit 0 (no-op, proceed with original command)
-  exit 0
-fi
-
-GLOBAL_ROOT="${BABYSITTER_GLOBAL_STATE_DIR:-$HOME/.a5c}"
-LOG_DIR="${BABYSITTER_LOG_DIR:-${GLOBAL_ROOT}/logs}"
-mkdir -p "$LOG_DIR" 2>/dev/null
-
-INPUT_FILE=$(mktemp 2>/dev/null || echo "/tmp/hook-user-prompt-submitted-$$.json")
-cat > "$INPUT_FILE"
-
-babysitter log --type hook --label "hook:user-prompt-submitted" --message "Hook invoked" --source shell-hook 2>/dev/null || true
-
-babysitter hook:run --hook-type user-prompt-submitted --harness github-copilot --json < "$INPUT_FILE" 2>"$LOG_DIR/babysitter-user-prompt-submitted-hook-stderr.log" || true
-
-babysitter log --type hook --label "hook:user-prompt-submitted" --message "Hook complete" --source shell-hook 2>/dev/null || true
-
-rm -f "$INPUT_FILE" 2>/dev/null
-
-exit 0