@a5c-ai/babysitter-opencode 5.0.1-staging.ef4e872c → 5.0.1-staging.f01483e80761

package/README.md

@@ -9,7 +9,7 @@ complex multi-step workflows -- powered by the Babysitter SDK.
 ## Plugin Structure
 
 ```
-plugins/babysitter-opencode/
+artifacts/generated-plugins/opencode/
   bin/
     cli.cjs              CLI entry point (babysitter-opencode command)
     install.cjs          Installation script
@@ -36,31 +36,29 @@ plugins/babysitter-opencode/
 
 ### Prerequisites
 
-Install the Babysitter SDK CLI:
+Install the Babysitter CLI once:
 
 ```bash
-npm install -g @a5c-ai/babysitter-sdk
+npm install -g @a5c-ai/babysitter
 ```
 
-### Method 1: npm global install (recommended)
+### Method 1: Babysitter harness install (recommended)
 
-```bash
-npm install -g @a5c-ai/babysitter-opencode
-```
-
-The `postinstall` script automatically copies the plugin into your current
-workspace's `.opencode/plugins/babysitter/` directory.
-
-To install into a specific workspace:
+Use the SDK helper for scriptable global or workspace installs. This is the canonical path used by the installer tests and resolves to `npx --yes @a5c-ai/babysitter-opencode install ...` under the hood:
 
 ```bash
-babysitter-opencode install --workspace /path/to/project
+# Global install
+babysitter harness:install-plugin opencode
+
+# Workspace install
+babysitter harness:install-plugin opencode --workspace /path/to/project
 ```
 
-### Method 2: Babysitter harness install
+### Method 2: Published package installer
 
 ```bash
-babysitter harness:install-plugin opencode
+npx --yes @a5c-ai/babysitter-opencode install --global
+npx --yes @a5c-ai/babysitter-opencode install --workspace /path/to/project
 ```
 
 ### Method 3: Manual copy
@@ -94,13 +92,13 @@ OpenCode config directory (`<userDataPath>/opencode/plugins/babysitter/`).
 
 ```bash
 # Auto-detects Accomplish during standard install
-npm install -g @a5c-ai/babysitter-opencode
+npx --yes @a5c-ai/babysitter-opencode install --global
 
 # Or target Accomplish explicitly
-babysitter-opencode install --accomplish
+npx --yes @a5c-ai/babysitter-opencode install --accomplish
 
 # Install to both standalone OpenCode and Accomplish
-babysitter-opencode install --global --accomplish
+npx --yes @a5c-ai/babysitter-opencode install --global --accomplish
 ```
 
 Accomplish stores OpenCode config at platform-specific locations:
@@ -206,7 +204,7 @@ babysitter process-library:active --json
 ## Running Tests
 
 ```bash
-cd plugins/babysitter-opencode
+cd artifacts/generated-plugins/opencode
 npm test
 ```
 

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.f01483e80761",
     author: { name: "a5c.ai" },
   };
   if (idx >= 0) marketplace.plugins[idx] = entry;

package/commands/call.md

@@ -4,4 +4,8 @@ argument-hint: Specific instructions for the run.
 allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
 ---
 
-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). Then continue executing the returned instructions in this same turn. Do not stop after the Skill tool returns; carry the requested run through to completion proof.
+
+User arguments for this command:
+
+$ARGUMENTS

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/commands/yolo.md

@@ -1,7 +1,11 @@
----
-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.
-argument-hint: Specific instructions for the run.
-allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
----
-
-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.
+---
+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.
+argument-hint: Specific instructions for the run.
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+Start the Babysitter run directly through the CLI, without any user interaction or breakpoints. Do not invoke the Skill tool and do not run an instructions-only command. In Claude Code, use Bash to run `babysitter harness:yolo --harness claude-code --workspace "$PWD" --prompt "<user arguments>" --json`; in Codex, run `babysitter harness:yolo --harness codex --workspace "$PWD" --prompt "<user arguments>" --json`; in other harnesses, use the same command with that harness id. Replace `<user arguments>` with the arguments shown below, wait for the command to finish, and treat the CLI completion proof as the result.
+
+User arguments for this command:
+
+$ARGUMENTS

package/hooks/babysitter-proxied-stop-hook.sh

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

package/hooks/hooks.json

@@ -26,14 +26,6 @@
         "timeoutMs": 30000
       }
     ],
-    "session.idle": [
-      {
-        "type": "command",
-        "script": "./hooks/babysitter-proxied-session-idle.js",
-        "description": "babysitter SessionIdle hook",
-        "timeoutMs": 30000
-      }
-    ],
     "shell.env": [
       {
         "type": "command",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-opencode",
-  "version": "5.0.1-staging.ef4e872c",
+  "version": "5.0.1-staging.f01483e80761",
   "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",
@@ -8,8 +8,7 @@
     "postinstall": "node bin/install.js",
     "preuninstall": "node bin/uninstall.js",
     "team:install": "node scripts/team-install.js",
-    "test": "node test/integration.test.js",
-    "sync:commands": "node scripts/sync-command-docs.cjs"
+    "test": "node test/integration.test.js"
   },
   "bin": {
     "babysitter-opencode": "bin/cli.js"
@@ -36,15 +35,14 @@
     "access": "public"
   },
   "dependencies": {
-    "@a5c-ai/babysitter-sdk": "5.0.1-staging.ef4e872c"
+    "@a5c-ai/babysitter-sdk": "5.0.1-staging.f01483e80761"
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/a5c-ai/babysitter.git",
-    "directory": "plugins/babysitter-opencode"
+    "url": "git+https://github.com/a5c-ai/babysitter-opencode.git"
   },
-  "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-opencode#readme",
+  "homepage": "https://github.com/a5c-ai/babysitter-opencode#readme",
   "bugs": {
-    "url": "https://github.com/a5c-ai/babysitter/issues"
+    "url": "https://github.com/a5c-ai/babysitter-opencode/issues"
   }
 }

package/plugin.json

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

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/accomplish-status/SKILL.md

@@ -29,7 +29,7 @@ Where `OPENCODE_CONFIG_DIR` is resolved from the `OPENCODE_CONFIG_DIR` environme
 Read the SDK version from `versions.json` to ensure version compatibility:
 
 ```bash
-SDK_VERSION=$(node -e "try{const fs=require('fs');const probes=['./plugins/babysitter-opencode/versions.json','./node_modules/@a5c-ai/babysitter-opencode/versions.json'];for(const probe of probes){if(fs.existsSync(probe)){console.log(JSON.parse(fs.readFileSync(probe,'utf8')).sdkVersion||'latest');process.exit(0)}}console.log('latest')}catch{console.log('latest')}")
+SDK_VERSION=$(node -e "try{const fs=require('fs');const probes=['./plugins/babysitter-unified/versions.json','./node_modules/@a5c-ai/babysitter-opencode/versions.json'];for(const probe of probes){if(fs.existsSync(probe)){console.log(JSON.parse(fs.readFileSync(probe,'utf8')).sdkVersion||'latest');process.exit(0)}}console.log('latest')}catch{console.log('latest')}")
 npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION
 
 CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"

package/skills/babysit/SKILL.md

@@ -14,7 +14,7 @@ Orchestrate `.a5c/runs/<runId>/` through iterative execution.
 Read the SDK version from `versions.json` to ensure version compatibility:
 
 ```bash
-SDK_VERSION=$(node -e "try{const fs=require('fs');const probes=['./plugins/babysitter-opencode/versions.json','./node_modules/@a5c-ai/babysitter-opencode/versions.json'];for(const probe of probes){if(fs.existsSync(probe)){console.log(JSON.parse(fs.readFileSync(probe,'utf8')).sdkVersion||'latest');process.exit(0)}}console.log('latest')}catch{console.log('latest')}")
+SDK_VERSION=$(node -e "try{const fs=require('fs');const probes=['./plugins/babysitter-unified/versions.json','./node_modules/@a5c-ai/babysitter-opencode/versions.json'];for(const probe of probes){if(fs.existsSync(probe)){console.log(JSON.parse(fs.readFileSync(probe,'utf8')).sdkVersion||'latest');process.exit(0)}}console.log('latest')}catch{console.log('latest')}")
 
 npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION
 CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"

package/skills/call/SKILL.md

@@ -5,4 +5,8 @@ description: Orchestrate a babysitter run. use this command to start babysitting
 
 # call
 
-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). Then continue executing the returned instructions in this same turn. Do not stop after the Skill tool returns; carry the requested run through to completion proof.
+
+User arguments for this command:
+
+$ARGUMENTS

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/skills/yolo/SKILL.md

@@ -5,4 +5,8 @@ description: Orchestrate a babysitter run. use this command to start babysitting
 
 # 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.
+Start the Babysitter run directly through the CLI, without any user interaction or breakpoints. Do not invoke the Skill tool and do not run an instructions-only command. In Claude Code, use Bash to run `babysitter harness:yolo --harness claude-code --workspace "$PWD" --prompt "<user arguments>" --json`; in Codex, run `babysitter harness:yolo --harness codex --workspace "$PWD" --prompt "<user arguments>" --json`; in other harnesses, use the same command with that harness id. Replace `<user arguments>` with the arguments shown below, wait for the command to finish, and treat the CLI completion proof as the result.
+
+User arguments for this command:
+
+$ARGUMENTS

package/versions.json

@@ -1,4 +1,4 @@
 {
-  "sdkVersion": "5.0.1-staging.ef4e872c",
-  "extensionVersion": "5.0.0"
+  "sdkVersion": "5.0.1-staging.f01483e80761",
+  "extensionVersion": "5.0.1-staging.f01483e80761"
 }

package/hooks/babysitter-proxied-session-idle.js

@@ -1,24 +0,0 @@
-#!/usr/bin/env node
-"use strict";
-var execSync = require("child_process").execSync;
-var path = require("path");
-var readFileSync = require("fs").readFileSync;
-
-var PLUGIN_ROOT = process.env.PLUGIN_ROOT || process.env.PLUGIN_ROOT || path.resolve(__dirname, "..");
-var stdin = "";
-try { stdin = readFileSync(0, "utf8"); } catch {}
-try {
-  var result = execSync("bash " + JSON.stringify(path.join(PLUGIN_ROOT, "hooks/session-idle.sh")), {
-    input: stdin,
-    stdio: ["pipe", "pipe", "pipe"],
-    timeout: 30000,
-    env: Object.assign({}, process.env, {
-      HOOK_TYPE: process.env.HOOK_TYPE || "",
-      ADAPTER_NAME: process.env.ADAPTER_NAME || "opencode",
-      PLUGIN_ROOT: PLUGIN_ROOT
-    })
-  });
-  process.stdout.write(result);
-} catch (e) {
-  process.stdout.write("{}\n");
-}

package/hooks/babysitter-proxied-session-idle.sh

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

package/scripts/sync-command-docs.cjs

@@ -1,107 +0,0 @@
-'use strict';
-
-const path = require('path');
-const {
-  listMarkdownBasenames,
-  reportCheckResult,
-  syncCommandMirrors,
-  syncSkillsFromCommands,
-  writeFileIfChanged,
-} = require('../../../scripts/plugin-command-sync-lib.cjs');
-
-const PACKAGE_ROOT = path.resolve(__dirname, '..');
-const REPO_ROOT = path.resolve(PACKAGE_ROOT, '..', '..');
-const ROOT_COMMANDS = path.join(REPO_ROOT, 'plugins', 'babysitter', 'commands');
-const COMMANDS_ROOT = path.join(PACKAGE_ROOT, 'commands');
-const SKILLS_ROOT = path.join(PACKAGE_ROOT, 'skills');
-const LABEL = 'babysitter-opencode sync';
-
-const BABYSIT_SKILL = `---
-name: babysit
-description: Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
----
-
-# babysit
-
-Orchestrate \`.a5c/runs/<runId>/\` through iterative execution.
-
-## Dependencies
-
-### Babysitter SDK and CLI
-
-Read the SDK version from \`versions.json\` to ensure version compatibility:
-
-\`\`\`bash
-SDK_VERSION=$(node -e "try{const fs=require('fs');const probes=['./plugins/babysitter-opencode/versions.json','./node_modules/@a5c-ai/babysitter-opencode/versions.json'];for(const probe of probes){if(fs.existsSync(probe)){console.log(JSON.parse(fs.readFileSync(probe,'utf8')).sdkVersion||'latest');process.exit(0)}}console.log('latest')}catch{console.log('latest')}")
-
-npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION
-CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"
-\`\`\`
-
-## Instructions
-
-Run the following command to get full orchestration instructions:
-
-\`\`\`bash
-babysitter instructions:babysit-skill --harness opencode --interactive
-\`\`\`
-
-For non-interactive mode:
-
-\`\`\`bash
-babysitter instructions:babysit-skill --harness opencode --no-interactive
-\`\`\`
-
-Follow the instructions returned by the command above to orchestrate the run.
-`;
-
-function getCommandNames() {
-  return listMarkdownBasenames(ROOT_COMMANDS);
-}
-
-function main() {
-  const check = process.argv.includes('--check');
-  const commandNames = getCommandNames();
-  const mirrorResult = syncCommandMirrors({
-    label: LABEL,
-    sourceRoot: ROOT_COMMANDS,
-    targetRoot: COMMANDS_ROOT,
-    names: commandNames,
-    check,
-    cwd: PACKAGE_ROOT,
-  });
-  const skillsResult = syncSkillsFromCommands({
-    label: LABEL,
-    sourceRoot: COMMANDS_ROOT,
-    skillsRoot: SKILLS_ROOT,
-    names: commandNames,
-    check,
-    cwd: PACKAGE_ROOT,
-  });
-
-  const babysitSkillPath = path.join(SKILLS_ROOT, 'babysit', 'SKILL.md');
-  if (check) {
-    const fs = require('fs');
-    const stale = [...mirrorResult.stale, ...skillsResult.stale];
-    const current = fs.existsSync(babysitSkillPath)
-      ? fs.readFileSync(babysitSkillPath, 'utf8')
-      : null;
-    if (current !== BABYSIT_SKILL) {
-      stale.push(path.relative(PACKAGE_ROOT, babysitSkillPath));
-    }
-    reportCheckResult(LABEL, stale);
-    return;
-  }
-
-  const babysitUpdated = writeFileIfChanged(babysitSkillPath, BABYSIT_SKILL) ? 1 : 0;
-  const updated = mirrorResult.updated + skillsResult.updated + babysitUpdated;
-
-  if (updated === 0) {
-    console.log(`[${LABEL}] no OpenCode command or skill changes were needed.`);
-    return;
-  }
-
-  console.log(`[${LABEL}] updated ${updated} OpenCode command/skill file(s).`);
-}
-
-main();

package/scripts/sync-command-surfaces.js

@@ -1,52 +0,0 @@
-#!/usr/bin/env node
-/**
- * Sync command surfaces from the canonical babysitter plugin.
- *
- * Copies command .md files from the cursor/codex plugins or generates
- * them from the SDK CLI command definitions. Used during build/deploy
- * to keep command surfaces in sync across harness plugins.
- */
-
-"use strict";
-
-const fs = require("fs");
-const path = require("path");
-
-const PLUGIN_ROOT = path.resolve(__dirname, "..");
-const COMMANDS_DIR = path.join(PLUGIN_ROOT, "commands");
-
-// Check mode
-const checkOnly = process.argv.includes("--check");
-
-function main() {
-  // Verify commands directory exists and has files
-  if (!fs.existsSync(COMMANDS_DIR)) {
-    console.error("ERROR: commands/ directory not found");
-    process.exit(1);
-  }
-
-  const files = fs.readdirSync(COMMANDS_DIR).filter(f => f.endsWith(".md"));
-  if (files.length === 0) {
-    console.error("ERROR: No command .md files found in commands/");
-    process.exit(1);
-  }
-
-  console.log(`Found ${files.length} command files:`);
-  for (const file of files) {
-    const content = fs.readFileSync(path.join(COMMANDS_DIR, file), "utf8");
-    const hasHeader = content.startsWith("---");
-    const status = hasHeader ? "OK" : "MISSING FRONTMATTER";
-    console.log(`  ${file} [${status}]`);
-    if (checkOnly && !hasHeader) {
-      process.exit(1);
-    }
-  }
-
-  if (checkOnly) {
-    console.log("\nAll command files are valid.");
-  } else {
-    console.log("\nCommand surfaces synced.");
-  }
-}
-
-main();