@a5c-ai/babysitter-github 5.0.1-staging.62666033 → 5.0.1-staging.686c8b317

package/README.md

@@ -28,7 +28,7 @@ Register the a5c.ai marketplace and install the plugin:
 
 ```bash
 # Register the marketplace
-copilot plugin marketplace add a5c-ai/babysitter
+copilot plugin marketplace add a5c-ai/babysitter-claude
 
 # Install the plugin
 copilot plugin install babysitter
@@ -36,11 +36,10 @@ copilot plugin install babysitter
 
 ### Direct GitHub install
 
-Install directly from the Git repository using Copilot CLI. Copilot CLI
-discovers the plugin via `.github/plugin/marketplace.json` at the repo root:
+Install directly from the generated external plugin repository:
 
 ```bash
-copilot plugin install a5c-ai/babysitter
+copilot plugin install a5c-ai/babysitter-github-copilot
 ```
 
 ### Alternative Installation (npm / development)
@@ -61,11 +60,11 @@ npm install -g @a5c-ai/babysitter-github
 babysitter-github install
 ```
 
-Or install from source:
+Or install from generated source:
 
 ```bash
-cd plugins/babysitter-github
-node bin/install.js
+npm run generate:plugins
+node artifacts/generated-plugins/github-copilot/bin/install.js
 ```
 
 Install into a specific workspace:
@@ -253,8 +252,7 @@ Copilot CLI looks for the plugin manifest in these paths, checked in order:
 The first match wins. This plugin uses `plugin.json` at the package root.
 
 For marketplace discovery, Copilot CLI looks for `.github/plugin/marketplace.json`
-at the repository root. This file lists all available plugins in the repo and is
-used when installing via `copilot plugin install OWNER/REPO`.
+at the repository root of the generated plugin repository.
 
 ### plugin.json Schema
 
@@ -404,7 +402,7 @@ repository root in `.github/plugin/marketplace.json`:
       "name": "babysitter",
       "description": "Multi-step workflow orchestration with event-sourced state",
       "version": "0.1.0",
-      "source": "./plugins/babysitter-github"
+      "source": "./"
     }
   ]
 }
@@ -461,7 +459,7 @@ These registries are available without running `marketplace add`.
 ## Plugin Structure (Directory Layout)
 
 ```
-plugins/babysitter-github/
+artifacts/generated-plugins/github-copilot/
   plugin.json              # Plugin manifest (skills, hooks, metadata)
   .github/plugin.json      # Plugin manifest (alternate discovery path)
   hooks.json               # Hook configuration (sessionStart, sessionEnd, userPromptSubmitted)
@@ -579,14 +577,14 @@ compatibility where PowerShell execution is available.
 git clone https://github.com/a5c-ai/babysitter.git
 cd babysitter
 npm install
-cd plugins/babysitter-github
+npm run generate:plugins
 node bin/install.js
 ```
 
 ### Publishing
 
 ```bash
-cd plugins/babysitter-github
+cd artifacts/generated-plugins/github-copilot
 npm run deploy            # Publish to npm (public)
 npm run deploy:staging    # Publish to npm with staging tag
 ```
@@ -594,7 +592,7 @@ npm run deploy:staging    # Publish to npm with staging tag
 ### Team installation
 
 ```bash
-cd plugins/babysitter-github
+cd artifacts/generated-plugins/github-copilot
 npm run team:install
 ```
 

package/bin/install-shared.js

@@ -104,7 +104,7 @@ function ensureMarketplaceEntry(marketplacePath, pluginRoot) {
     name: PLUGIN_NAME,
     source: relSource,
     description: "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
-    version: "5.0.0",
+    version: "5.0.1-staging.686c8b317",
     author: { name: "a5c.ai" },
   };
   if (idx >= 0) marketplace.plugins[idx] = entry;

package/commands/cleanup.md

@@ -10,11 +10,33 @@ Create and run a cleanup process using the process at `skills\babysit\process\cr
 
 Implementation notes (for the process):
 - Parse arguments for `--dry-run` flag (if present, set dryRun: true in inputs) and `--keep-days N` (default: 7)
-- The process scans .a5c/runs/ for completed/failed runs, aggregates insights, writes summaries, then removes old data
-- Always show the user what will be removed before removing (in interactive mode via breakpoints)
-- In non-interactive mode (yolo), proceed with cleanup using defaults
-- The insights file goes to docs/run-history-insights.md
-- Only remove terminal runs (completed/failed) older than the keep-days threshold
-- Never remove active/in-progress runs
-- Remove orphaned process files not referenced by remaining runs
-- After cleanup, show remaining run count and disk usage
+
+CRITICAL: The cleanup MUST follow this exact phase order. Do NOT delete any run before Phase 2 completes.
+
+Phase 1 — Scan:
+- Scan .a5c/runs/ for all runs
+- Classify each as terminal (completed/failed) or active (in-progress/created)
+- Identify terminal runs older than the keep-days threshold as removal candidates
+- Never mark active/in-progress runs for removal
+- Count and report: total runs, terminal, active, removal candidates, disk usage
+
+Phase 2 — Aggregate insights (BEFORE any deletion):
+- For EVERY removal candidate, read its run.json and journal/ events
+- Extract: processId, prompt, status, event count, created date, task summaries
+- Group by process type and extract patterns (retry counts, convergence behavior, failure modes)
+- Append a new dated section to docs/run-history-insights.md with:
+  - Summary statistics (runs removed, disk freed, runs retained)
+  - Run categories with counts and descriptions
+  - Key patterns observed (multi-batch convergence, retry behavior, etc.)
+  - What worked well / what didn't from the run data
+- This file MUST be written and verified before proceeding to Phase 3
+
+Phase 3 — Confirm removal:
+- In interactive mode, show the user what will be removed via a breakpoint
+- In non-interactive mode (yolo), proceed with defaults
+- In dry-run mode, stop here and show what would be removed
+
+Phase 4 — Remove:
+- Delete the terminal runs older than keep-days threshold
+- Identify and remove orphaned process files not referenced by remaining runs
+- Show remaining run count and disk usage after cleanup

package/commands/doctor.md

@@ -156,7 +156,6 @@ If it exists:
 **Goal:** Inspect babysitter session files for health and detect runaway loops.
 
 - Search for session state files using Glob:
-  - `plugins/babysitter/skills/babysit/state/*.md`
   - `.a5c/state/*.md`
   - `.a5c/state/*.json`
 - For each session state file found:
@@ -260,7 +259,7 @@ Mark as PASS if total size < 500MB and no files > 10MB. Mark as WARN if total si
 
 ### 10a. Hook Registration
 
-- Locate the plugin root. Check for `CLAUDE_PLUGIN_ROOT` env var, or search for `plugins/babysitter/hooks/hooks.json` by walking up from the current directory.
+- Locate the plugin root. Check for `CLAUDE_PLUGIN_ROOT` env var first, or search for a babysitter `hooks.json` by walking up from the current directory.
 - If found, read `hooks.json` and verify:
   - A `Stop` hook entry exists with a command referencing `babysitter-stop-hook.sh`.
   - A `SessionStart` hook entry exists with a command referencing `babysitter-session-start-hook.sh`.
@@ -315,7 +314,7 @@ If the stop hook shows NO evidence of execution (no log entries, no journal even
 
 Perform these diagnostic steps in order and report the first failure found:
 
-1. **Plugin not installed**: Check if `plugins/babysitter/` exists relative to the project root and if `CLAUDE_PLUGIN_ROOT` is set. If the plugin directory doesn't exist, report: "Plugin not installed — the babysitter plugin directory is missing."
+1. **Plugin not installed**: Check if `CLAUDE_PLUGIN_ROOT` is set or if a babysitter plugin directory exists relative to the project root. If neither exists, report: "Plugin not installed — the babysitter plugin directory is missing."
 
 2. **Plugin not enabled**: Check for Claude settings files:
    - `~/.claude/settings.json` — look for `babysitter` in `enabledPlugins`.

package/hooks/babysitter-proxied-post-tool-use.ps1

@@ -0,0 +1,12 @@
+# PowerShell hook wrapper — sets env vars and delegates to bash
+$env:HOOK_TYPE = 'post-tool-use'
+$env:ADAPTER_NAME = 'copilot'
+$env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
+
+$input_data = [Console]::In.ReadToEnd()
+$result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
+if ($LASTEXITCODE -eq 0 -and $result) {
+  Write-Output $result
+} else {
+  Write-Output '{}'
+}

package/hooks/babysitter-proxied-post-tool-use.sh

@@ -0,0 +1,3 @@
+#!/bin/bash
+set -euo pipefail
+babysitter hook:run --harness unified --hook-type post-tool-use --json

package/hooks/babysitter-proxied-pre-compact.ps1

@@ -0,0 +1,12 @@
+# PowerShell hook wrapper — sets env vars and delegates to bash
+$env:HOOK_TYPE = 'pre-compact'
+$env:ADAPTER_NAME = 'copilot'
+$env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
+
+$input_data = [Console]::In.ReadToEnd()
+$result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
+if ($LASTEXITCODE -eq 0 -and $result) {
+  Write-Output $result
+} else {
+  Write-Output '{}'
+}

package/hooks/babysitter-proxied-pre-compact.sh

@@ -0,0 +1,3 @@
+#!/bin/bash
+set -euo pipefail
+babysitter hook:run --harness unified --hook-type pre-compact --json

package/hooks/babysitter-proxied-pre-tool-use.ps1

@@ -0,0 +1,12 @@
+# PowerShell hook wrapper — sets env vars and delegates to bash
+$env:HOOK_TYPE = 'pre-tool-use'
+$env:ADAPTER_NAME = 'copilot'
+$env:PLUGIN_ROOT = Split-Path -Parent (Split-Path -Parent $PSScriptRoot)
+
+$input_data = [Console]::In.ReadToEnd()
+$result = $input_data | & bash "$PSScriptRoot/../$($MyInvocation.MyCommand.Name -replace '\.ps1$','.sh')" 2>$null
+if ($LASTEXITCODE -eq 0 -and $result) {
+  Write-Output $result
+} else {
+  Write-Output '{}'
+}

package/hooks/babysitter-proxied-pre-tool-use.sh

@@ -0,0 +1,3 @@
+#!/bin/bash
+set -euo pipefail
+babysitter hook:run --harness unified --hook-type pre-tool-use --json

package/hooks.json

@@ -17,6 +17,30 @@
         "timeoutSec": 15
       }
     ],
+    "preToolUse": [
+      {
+        "type": "command",
+        "bash": "./hooks/babysitter-proxied-pre-tool-use.sh",
+        "powershell": "./hooks/babysitter-proxied-pre-tool-use.ps1",
+        "timeoutSec": 30
+      }
+    ],
+    "postToolUse": [
+      {
+        "type": "command",
+        "bash": "./hooks/babysitter-proxied-post-tool-use.sh",
+        "powershell": "./hooks/babysitter-proxied-post-tool-use.ps1",
+        "timeoutSec": 30
+      }
+    ],
+    "PreCompact": [
+      {
+        "type": "command",
+        "bash": "./hooks/babysitter-proxied-pre-compact.sh",
+        "powershell": "./hooks/babysitter-proxied-pre-compact.ps1",
+        "timeoutSec": 30
+      }
+    ],
     "sessionEnd": [
       {
         "type": "command",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-github",
-  "version": "5.0.1-staging.62666033",
+  "version": "5.0.1-staging.686c8b317",
   "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
   "scripts": {
     "deploy": "npm publish --access public",
@@ -36,15 +36,14 @@
     "access": "public"
   },
   "dependencies": {
-    "@a5c-ai/babysitter-sdk": "5.0.1-staging.62666033"
+    "@a5c-ai/babysitter-sdk": "5.0.1-staging.686c8b317"
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/a5c-ai/babysitter.git",
-    "directory": "plugins/babysitter-github"
+    "url": "git+https://github.com/a5c-ai/babysitter-github-copilot.git"
   },
-  "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-github#readme",
+  "homepage": "https://github.com/a5c-ai/babysitter-github-copilot#readme",
   "bugs": {
-    "url": "https://github.com/a5c-ai/babysitter/issues"
+    "url": "https://github.com/a5c-ai/babysitter-github-copilot/issues"
   }
 }

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "babysitter",
-  "version": "5.0.1-staging.62666033",
+  "version": "5.0.1-staging.686c8b317",
   "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
   "author": {
     "name": "a5c.ai"

package/scripts/create-release-tag.mjs

@@ -0,0 +1,18 @@
+#!/usr/bin/env node
+import { spawnSync } from 'node:child_process';
+import { existsSync, readFileSync } from 'node:fs';
+
+function run(command, args) {
+  const result = spawnSync(command, args, { encoding: 'utf8', stdio: 'inherit' });
+  if (result.status !== 0) process.exit(result.status || 1);
+}
+
+const branch = process.env.GITHUB_REF_NAME || 'develop';
+const sha = (process.env.GITHUB_SHA || '').slice(0, 12);
+const version = existsSync('package.json') ? JSON.parse(readFileSync('package.json', 'utf8')).version : JSON.parse(readFileSync('versions.json', 'utf8')).sdkVersion;
+const normalized = String(version).replace(/[^0-9A-Za-z._-]/g, '-');
+const tag = 'release/' + branch + '/v' + normalized + '-' + sha;
+run('git', ['config', 'user.name', 'github-actions[bot]']);
+run('git', ['config', 'user.email', 'github-actions[bot]@users.noreply.github.com']);
+run('git', ['tag', tag]);
+run('git', ['push', 'origin', tag]);

package/scripts/publish-from-tag.mjs

@@ -0,0 +1,41 @@
+#!/usr/bin/env node
+import { spawnSync } from 'node:child_process';
+import { readFileSync } from 'node:fs';
+
+function run(command, args, options = {}) {
+  const result = spawnSync(command, args, { stdio: options.stdio || 'inherit', encoding: options.encoding });
+  if (result.status !== 0 && !options.allowFailure) process.exit(result.status || 1);
+  return result;
+}
+
+function npmView(packageSpec) {
+  return run('npm', ['view', packageSpec, 'version'], { allowFailure: true, stdio: 'pipe', encoding: 'utf8' }).status === 0;
+}
+
+const pkg = JSON.parse(readFileSync('package.json', 'utf8'));
+const ref = process.env.GITHUB_REF_NAME || '';
+const branch = ref.split('/')[1] || 'develop';
+const tag = branch === 'main' ? 'latest' : branch;
+
+if (!process.env.NODE_AUTH_TOKEN) {
+  console.log('NODE_AUTH_TOKEN is not configured; skipping npm publish.');
+  process.exit(0);
+}
+
+if (npmView(pkg.name + '@' + pkg.version)) {
+  console.log(pkg.name + '@' + pkg.version + ' already exists; ensuring dist-tag ' + tag + '.');
+  run('npm', ['dist-tag', 'add', pkg.name + '@' + pkg.version, tag], { allowFailure: true });
+  process.exit(0);
+}
+
+for (const field of ['dependencies', 'peerDependencies', 'optionalDependencies']) {
+  for (const [name, version] of Object.entries(pkg[field] || {})) {
+    if (!name.startsWith('@a5c-ai/') || version.startsWith('^') || version.startsWith('~') || version === '*' || version.startsWith('workspace:')) continue;
+    if (!npmView(name + '@' + version)) {
+      console.log('Required internal dependency ' + name + '@' + version + ' is not published yet; skipping npm publish.');
+      process.exit(0);
+    }
+  }
+}
+
+run('npm', ['publish', '--access', 'public', '--tag', tag]);

package/skills/cleanup/SKILL.md

@@ -11,11 +11,33 @@ Create and run a cleanup process using the process at `skills\babysit\process\cr
 
 Implementation notes (for the process):
 - Parse arguments for `--dry-run` flag (if present, set dryRun: true in inputs) and `--keep-days N` (default: 7)
-- The process scans .a5c/runs/ for completed/failed runs, aggregates insights, writes summaries, then removes old data
-- Always show the user what will be removed before removing (in interactive mode via breakpoints)
-- In non-interactive mode (yolo), proceed with cleanup using defaults
-- The insights file goes to docs/run-history-insights.md
-- Only remove terminal runs (completed/failed) older than the keep-days threshold
-- Never remove active/in-progress runs
-- Remove orphaned process files not referenced by remaining runs
-- After cleanup, show remaining run count and disk usage
+
+CRITICAL: The cleanup MUST follow this exact phase order. Do NOT delete any run before Phase 2 completes.
+
+Phase 1 — Scan:
+- Scan .a5c/runs/ for all runs
+- Classify each as terminal (completed/failed) or active (in-progress/created)
+- Identify terminal runs older than the keep-days threshold as removal candidates
+- Never mark active/in-progress runs for removal
+- Count and report: total runs, terminal, active, removal candidates, disk usage
+
+Phase 2 — Aggregate insights (BEFORE any deletion):
+- For EVERY removal candidate, read its run.json and journal/ events
+- Extract: processId, prompt, status, event count, created date, task summaries
+- Group by process type and extract patterns (retry counts, convergence behavior, failure modes)
+- Append a new dated section to docs/run-history-insights.md with:
+  - Summary statistics (runs removed, disk freed, runs retained)
+  - Run categories with counts and descriptions
+  - Key patterns observed (multi-batch convergence, retry behavior, etc.)
+  - What worked well / what didn't from the run data
+- This file MUST be written and verified before proceeding to Phase 3
+
+Phase 3 — Confirm removal:
+- In interactive mode, show the user what will be removed via a breakpoint
+- In non-interactive mode (yolo), proceed with defaults
+- In dry-run mode, stop here and show what would be removed
+
+Phase 4 — Remove:
+- Delete the terminal runs older than keep-days threshold
+- Identify and remove orphaned process files not referenced by remaining runs
+- Show remaining run count and disk usage after cleanup

package/skills/doctor/SKILL.md

@@ -157,7 +157,6 @@ If it exists:
 **Goal:** Inspect babysitter session files for health and detect runaway loops.
 
 - Search for session state files using Glob:
-  - `plugins/babysitter/skills/babysit/state/*.md`
   - `.a5c/state/*.md`
   - `.a5c/state/*.json`
 - For each session state file found:
@@ -261,7 +260,7 @@ Mark as PASS if total size < 500MB and no files > 10MB. Mark as WARN if total si
 
 ### 10a. Hook Registration
 
-- Locate the plugin root. Check for `CLAUDE_PLUGIN_ROOT` env var, or search for `plugins/babysitter/hooks/hooks.json` by walking up from the current directory.
+- Locate the plugin root. Check for `CLAUDE_PLUGIN_ROOT` env var first, or search for a babysitter `hooks.json` by walking up from the current directory.
 - If found, read `hooks.json` and verify:
   - A `Stop` hook entry exists with a command referencing `babysitter-stop-hook.sh`.
   - A `SessionStart` hook entry exists with a command referencing `babysitter-session-start-hook.sh`.
@@ -316,7 +315,7 @@ If the stop hook shows NO evidence of execution (no log entries, no journal even
 
 Perform these diagnostic steps in order and report the first failure found:
 
-1. **Plugin not installed**: Check if `plugins/babysitter/` exists relative to the project root and if `CLAUDE_PLUGIN_ROOT` is set. If the plugin directory doesn't exist, report: "Plugin not installed — the babysitter plugin directory is missing."
+1. **Plugin not installed**: Check if `CLAUDE_PLUGIN_ROOT` is set or if a babysitter plugin directory exists relative to the project root. If neither exists, report: "Plugin not installed — the babysitter plugin directory is missing."
 
 2. **Plugin not enabled**: Check for Claude settings files:
    - `~/.claude/settings.json` — look for `babysitter` in `enabledPlugins`.

package/versions.json

@@ -1,4 +1,4 @@
 {
-  "sdkVersion": "5.0.1-staging.62666033",
-  "extensionVersion": "5.0.0"
+  "sdkVersion": "5.0.1-staging.686c8b317",
+  "extensionVersion": "5.0.1-staging.686c8b317"
 }

package/scripts/sync-command-surfaces.js

@@ -1,20 +0,0 @@
-#!/usr/bin/env node
-'use strict';
-
-const path = require('path');
-const { spawnSync } = require('child_process');
-
-const REPO_ROOT = path.resolve(__dirname, '..', '..');
-const syncScript = path.join(REPO_ROOT, 'scripts', 'sync-plugin-commands.cjs');
-const args = [syncScript, '--target', 'github-copilot'];
-
-if (process.argv.includes('--check')) {
-  args.push('--check');
-}
-
-const result = spawnSync(process.execPath, args, {
-  cwd: REPO_ROOT,
-  stdio: 'inherit',
-});
-
-process.exit(result.status ?? 1);