@a5c-ai/babysitter-codex 5.0.1-staging.ffad3b46492e → 5.1.1-staging.00ceebd28cf2

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "babysitter",
-  "version": "5.0.1-staging.ffad3b46492e",
+  "version": "5.1.1-staging.00ceebd28cf2",
   "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/README.md

@@ -11,9 +11,15 @@ This package ships a real Codex plugin bundle:
 
 It still uses the Babysitter SDK CLI and the shared `~/.a5c` process-library
 state. Global install writes the plugin bundle to `~/.agents/plugins/babysitter`
-and updates `~/.agents/plugins/marketplace.json` so Codex can load the plugin
-through its marketplace surface. Workspace install continues to materialize a
-workspace-local Codex surface for team setup.
+and updates `.agents/plugins/marketplace.json` (primary) so Codex can load the
+plugin through its marketplace surface. Codex also recognizes
+`.claude-plugin/marketplace.json` as a legacy marketplace path. Workspace
+install continues to materialize a workspace-local Codex surface for team setup.
+
+Codex now ships an official marketplace CLI (`codex plugin marketplace`) that
+supports `add`, `list`, `upgrade`, and `remove` subcommands. Plugin bundles
+installed through the marketplace are cached under
+`~/.codex/plugins/cache/$MARKETPLACE/$PLUGIN/$VERSION/`.
 
 ## Installation
 
@@ -40,6 +46,34 @@ npx --yes @a5c-ai/babysitter-codex install --global
 npx --yes @a5c-ai/babysitter-codex install --workspace /path/to/repo
 ```
 
+Alternatively, use the official Codex marketplace CLI to add the babysitter
+marketplace directly from GitHub:
+
+```bash
+codex plugin marketplace add a5c-ai/babysitter --ref staging --sparse .agents/plugins
+```
+
+Or from a local clone:
+
+```bash
+codex plugin marketplace add ./path/to/babysitter
+```
+
+Then browse and install:
+
+```bash
+codex plugin list --source babysitter
+codex plugin install babysitter --source babysitter
+```
+
+Other marketplace commands:
+
+```bash
+codex plugin marketplace list
+codex plugin marketplace upgrade babysitter
+codex plugin marketplace remove babysitter
+```
+
 Then open Codex and finish enabling the plugin from the plugin UI:
 
 ```text
@@ -64,6 +98,25 @@ The plugin provides:
 The process library is fetched and bound through the SDK CLI in
 `~/.a5c/active/process-library.json`.
 
+## Hook Environment Variables
+
+Codex exposes the following environment variables to hook scripts:
+
+| Variable | Description |
+|---|---|
+| `PLUGIN_ROOT` | Absolute path to the plugin root directory (native) |
+| `PLUGIN_DATA` | Persistent data directory for the plugin (native) |
+| `CLAUDE_PLUGIN_ROOT` | Compatibility alias for `PLUGIN_ROOT` |
+| `CLAUDE_PLUGIN_DATA` | Compatibility alias for `PLUGIN_DATA` |
+
+Hook scripts should prefer `PLUGIN_ROOT` / `PLUGIN_DATA` but can read the
+`CLAUDE_PLUGIN_ROOT` / `CLAUDE_PLUGIN_DATA` aliases for cross-harness
+compatibility with Claude Code plugins.
+
+Codex auto-detects hooks via `./hooks/hooks.json`. The `hooks` field in
+`.codex-plugin/plugin.json` accepts a path, an array of paths, an inline
+object, or an array of objects.
+
 ## Workspace Output
 
 After `install --workspace`, the important files are:

package/bin/install-shared.js

@@ -29,7 +29,7 @@ function writeFileIfChanged(filePath, contents) {
   try {
     const existing = fs.readFileSync(filePath, 'utf8');
     if (existing === contents) return false;
-  } catch {}
+  } catch (e) { process.stderr.write('[extensions-adapter] file read failed for ' + filePath + ', overwriting: ' + (e instanceof Error ? e.message : String(e)) + '\n'); }
   fs.mkdirSync(path.dirname(filePath), { recursive: true });
   fs.writeFileSync(filePath, contents);
   return true;
@@ -82,7 +82,7 @@ function writeJson(filePath, value) {
 function ensureExecutable(filePath) {
   try {
     fs.chmodSync(filePath, 0o755);
-  } catch {}
+  } catch (e) { process.stderr.write('[extensions-adapter] chmod failed for ' + filePath + ': ' + (e instanceof Error ? e.message : String(e)) + '\n'); }
 }
 
 function normalizeMarketplaceSourcePath(source, marketplacePath) {
@@ -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.1-staging.ffad3b46492e",
+    version: "5.1.1-staging.00ceebd28cf2",
     author: { name: "a5c.ai" },
   };
   if (idx >= 0) marketplace.plugins[idx] = entry;
@@ -130,7 +130,7 @@ function runPostInstall(pluginRoot) {
   if (fs.existsSync(postInstall)) {
     spawnSync(process.execPath, [postInstall], {
       cwd: pluginRoot, stdio: 'inherit',
-      env: { ...process.env, PLUGIN_ROOT: pluginRoot },
+      env: { ...process.env, PLUGIN_ROOT: pluginRoot, CLAUDE_PLUGIN_ROOT: pluginRoot },
     });
   }
 }
@@ -147,7 +147,7 @@ function resolveCliCommand(packageRoot) {
   const versionsPath = path.join(packageRoot, 'versions.json');
   const versions = readJson(versionsPath) || {};
   const ver = versions.sdkVersion || 'latest';
-  return `npx -y @a5c-ai/babysitter-sdk@${ver}`;
+  return `npm exec --yes --package @a5c-ai/babysitter-sdk@${ver} -- babysitter`;
 }
 
 function runCli(packageRoot, cliArgs, options = {}) {

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

@@ -1,7 +1,7 @@
 #!/bin/bash
 # Session Start — installs SDK if needed, then runs hook handler.
 set -euo pipefail
-PLUGIN_ROOT="${PLUGIN_ROOT:-$(cd "$(dirname "$0")/.." && pwd)}"
+PLUGIN_ROOT="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$(cd "$(dirname "$0")/.." && pwd)}}"
 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")
 if ! command -v babysitter &>/dev/null; then
   npm i -g "@a5c-ai/babysitter-sdk@${SDK_VERSION}" --loglevel=error 2>/dev/null || \

package/hooks.json

@@ -6,7 +6,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-session-start.sh\" --json"
+            "command": "adapters-hooks invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-session-start.sh\" --json"
           }
         ]
       }
@@ -17,7 +17,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-stop.sh\" --json"
+            "command": "adapters-hooks invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-stop.sh\" --json"
           }
         ]
       }
@@ -28,7 +28,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-user-prompt-submit.sh\" --json"
+            "command": "adapters-hooks invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-user-prompt-submit.sh\" --json"
           }
         ]
       }
@@ -39,7 +39,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-pre-tool-use.sh\" --json"
+            "command": "adapters-hooks invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-pre-tool-use.sh\" --json"
           }
         ]
       }
@@ -50,7 +50,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-post-tool-use.sh\" --json"
+            "command": "adapters-hooks invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-post-tool-use.sh\" --json"
           }
         ]
       }
@@ -61,7 +61,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "a5c-hooks-mux invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-session-end.sh\" --json"
+            "command": "adapters-hooks invoke --adapter codex --handler \"bash .codex/hooks/babysitter-proxied-session-end.sh\" --json"
           }
         ]
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-codex",
-  "version": "5.0.1-staging.ffad3b46492e",
+  "version": "5.1.1-staging.00ceebd28cf2",
   "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
   "scripts": {
     "test": "npm run validate:ci",

package/skills/babysit/SKILL.md

@@ -1,13 +1,25 @@
 ---
 name: babysit
-description: >-
-  Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called explicitly. (babysit, babysitter, with a process, orchestrate, orchestrate a run, workflow, loop until, etc.)
+description: Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called explicitly. (babysit, babysitter, with a process, orchestrate, orchestrate a run, workflow, loop until, etc.)
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+version: 0.1.3
 ---
 
 # babysit
 
 Follow the commands below exactly. but apply judgement and creativity to get the job done. no matter how small or simple the task may seem, you must use the babysitter SDK and run lifecycle to execute it. This is non-negotiable. If you are asked to do something that seems like it could be done with a simple tool call, you must still use the babysitter SDK to create a run, define tasks, execute them, and complete the run. This is how you will learn and demonstrate mastery of the babysitter system. Always follow the full process, even for trivial tasks.
 
+Subagents that need a scratch checkout or working directory must create it under
+`/tmp/<descriptive-name>/`, not under `.a5c/runs/<runId>/work`. Before returning
+deliverables, validate that no run-dir worktree was left behind, for example:
+
+```bash
+find .a5c/runs -maxdepth 3 -name work -type d -print
+```
+
+That command should print nothing. If it prints a non-empty work directory, move
+or remove only the scratch data you created before returning.
+
 ## Dependencies
 
 ### Babysitter SDK and CLI
@@ -15,13 +27,19 @@ Follow the commands below exactly. but apply judgement and creativity to get the
 Read the SDK version from `versions.json` to ensure version compatibility:
 
 ```bash
-SDK_VERSION=$(node -e "try{console.log(JSON.parse(require('fs').readFileSync('${CODEX_PLUGIN_ROOT}/versions.json','utf8')).sdkVersion||'latest')}catch{console.log('latest')}")
-npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION
-
-CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"
+SDK_VERSION=$(node -e "try{console.log(JSON.parse(require('fs').readFileSync('${PLUGIN_ROOT}/versions.json','utf8')).sdkVersion||'latest')}catch{console.log('latest')}")
+npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION || npm i -g @a5c-ai/babysitter-sdk@latest
+
+if command -v babysitter >/dev/null 2>&1 && babysitter --version >/dev/null 2>&1; then
+  CLI="babysitter"
+else
+  CLI="npm exec --yes --package @a5c-ai/babysitter-sdk@$SDK_VERSION -- babysitter"
+fi
 ```
 
-If `babysitter` is already installed globally at the correct version, you may use `CLI="babysitter"` instead.
+If the pinned version fails to install (e.g. not yet published), the fallback installs `latest`.
+
+If a stale or broken global shim fails with `MODULE_NOT_FOUND`, repair it with `npm rm -g @a5c-ai/babysitter @a5c-ai/babysitter-sdk && npm i -g @a5c-ai/babysitter-sdk@$SDK_VERSION`, then re-run `babysitter --version`.
 
 ### jq
 
@@ -29,13 +47,13 @@ Make sure `jq` is installed and available in the path. If not, install it.
 
 ## Instructions
 
-Run the following command to get full orchestration instructions:
+Run the following command to get full instructions:
 
 ```bash
 $CLI instructions:babysit-skill --harness codex --interactive
 ```
 
-For non-interactive runs (e.g., with `-p` flag or no question tool):
+For non-interactive mode (running with `-p` flag or no AskUserQuestion tool):
 
 ```bash
 $CLI instructions:babysit-skill --harness codex --no-interactive

package/skills/blueprints/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: blueprints
+description: manage Babysitter blueprints. Use this command to list installed blueprints, browse marketplaces, install, update, uninstall, configure, or create a new blueprint.
+---
+
+# blueprints
+
+This command installs and manages Babysitter blueprints. A blueprint is a version-managed package of contextual instructions or deterministic Babysitter processes, not a conventional software plugin.
+
+If the command is run without arguments, list installed blueprints with their name, version, marketplace, installation date, and last update date. Also list configured marketplaces and show how to add the default marketplace when none exist.
+
+Blueprints can be installed at two scopes:
+
+- **global** (`--global`): stored under `~/.a5c/`, available for all projects
+- **project** (`--project`): stored under `<projectDir>/.a5c/`, project-specific
+
+## Marketplace Management
+
+Marketplaces are git repositories containing a `marketplace.json` manifest and blueprint package directories. The SDK clones new marketplaces to `.a5c/blueprints/marketplaces/` for the selected scope and reads legacy `.a5c/marketplaces/` clones for compatibility.
+
+### Add a marketplace
+
+```bash
+babysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]
+```
+
+### Update a marketplace
+
+```bash
+babysitter blueprints:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]
+```
+
+### List blueprints in a marketplace
+
+```bash
+babysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]
+```
+
+## Blueprint Lifecycle
+
+For `blueprint:install`, `blueprint:update`, `blueprint:configure`, and `blueprint:list-blueprints`, the `--marketplace-name` flag is auto-detected when only one marketplace is cloned for the selected scope.
+
+```bash
+babysitter blueprints:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprints:update --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
+babysitter blueprints:configure --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
+babysitter blueprints:uninstall --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
+```
+
+The `--plugin-name` flag is preserved for CLI compatibility with existing marketplace manifests. User-facing docs should call the installable a blueprint.
+
+## Registry Management
+
+```bash
+babysitter blueprints:list-installed --global|--project [--json]
+babysitter blueprints:update-registry --plugin-name <name> --plugin-version <ver> --marketplace-name <mp> --global|--project [--json]
+babysitter blueprints:remove-from-registry --plugin-name <name> --global|--project [--json]
+```
+
+## Deprecated Aliases
+
+The old `plugin:*` commands remain available as deprecated aliases for one release. Prefer `blueprint:*` in new docs, skills, and process instructions.
+
+## Agent Plugins Are Separate
+
+Do not rename or reinterpret agent harness plugins while handling blueprints. `CLAUDE_PLUGIN_ROOT`, `PI_PLUGIN_ROOT`, `.claude/plugins/`, hooks-adapter, extensions-adapter, and agent plugin manifests stay plugin-specific.

package/skills/check-forbidden-markers/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: check-forbidden-markers
+description: Pre-deploy gate that scans built JS chunks for forbidden substring markers (saga-era / obsolete code paths) listed in a project-local forbidden-markers.txt
+---
+
+# check-forbidden-markers
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). Compose the gate from the shared helper at `library/processes/shared/forbidden-markers-scanner.js` (issue #477).
+
+## What this gate does
+
+Reads a list of literal substring markers from `scripts/forbidden-markers.txt` (blank lines and `#`-prefixed comments stripped) and greps every `.js` chunk under `.vercel/output/static/_next/static/chunks/` (Next.js / Vercel default; configurable) for any occurrence. Reports structured hits per `(marker, chunk)` pair with occurrence counts. Designed to chain between `vercel build --prod` and `vercel deploy --prod`.
+
+Use this gate when a refactor or restart-from-baseline replaced load-bearing code paths and you need a structural guarantee the obsolete symbols never re-ship. Burned-in evidence: cookbook VI-9 / VI-12 near-miss revivals during the 2026-05 iOS-Safari saga; the prototype lives at `cookbook/scripts/check-no-forbidden.mjs` and shipped two upstream contributions before being generalized as this gate.
+
+## When to use
+
+- **Pre-deploy.** Insert after build, before deploy. Block the deploy when `ok: false`.
+- **Post-restart.** After a baseline rollback + step-by-step re-add, snapshot the saga-era markers in `forbidden-markers.txt` and let CI hold the line.
+- **Post-refactor.** When old helper / handler / module names must not coexist with the new ones in the same bundle.
+
+## Expected config locations
+
+- `scripts/forbidden-markers.txt` — one marker per line, `#` for comments. The list is the contract; the gate is mechanical. Commit this file to source control.
+- `.vercel/output/static/_next/static/chunks/` — default scan target. Override for non-Vercel frameworks via the `--chunks-dir` flag or the `chunksDir` task input.
+
+A missing markers file is a no-op (`ok: true`, `reason: 'missing-markers-file'`) — misconfiguration is never a deploy block. A missing chunks directory is likewise a no-op (`reason: 'missing-chunks-dir'`) so the gate is safe to chain into `check:all` before the build runs.
+
+## Exit semantics
+
+| Reason                  | `ok`   | Deploy decision                |
+|-------------------------|--------|--------------------------------|
+| `missing-markers-file`  | true   | Pass (no gate active)          |
+| `missing-chunks-dir`    | true   | Pass (run before build)        |
+| `empty-markers`         | true   | Pass (list is empty)           |
+| `no-chunks`             | true   | Pass (nothing to scan)         |
+| `clean`                 | true   | Pass — proceed to deploy       |
+| `hits`                  | false  | **BLOCK** — surface hits, ask for triage |
+
+For each hit, the gate emits `{ marker, chunk, count }` so the operator sees the exact marker string, the absolute chunk path, and the number of occurrences in that chunk. Multiple hits across chunks for the same marker are reported separately.
+
+## Programmatic surface
+
+```js
+import { scanForbiddenMarkers, checkForbiddenMarkersTask } from '@a5c-ai/babysitter-library/processes/shared';
+
+// Direct call:
+const result = await scanForbiddenMarkers({
+  markersFile: 'scripts/forbidden-markers.txt',
+  chunksDir:   '.vercel/output/static/_next/static/chunks',
+});
+if (!result.ok) {
+  // result.hits: Array<{ marker, chunk, count }>
+  // result.reason === 'hits'
+  process.exit(1);
+}
+
+// Or dispatched as a babysitter task:
+const gate = await ctx.task(checkForbiddenMarkersTask, {
+  projectDir: '.',
+  // markersFile / chunksDir are inferred from projectDir if omitted
+});
+```
+
+## Reference
+
+- Issue: https://github.com/a5c-ai/babysitter/issues/477
+- Helper module: `library/processes/shared/forbidden-markers-scanner.js`
+- Origin (cookbook prototype): `cookbook/scripts/check-no-forbidden.mjs` (81 lines)

package/skills/cleanup/SKILL.md

@@ -7,7 +7,13 @@ description: Clean up .a5c/runs and .a5c/processes directories. Aggregates insig
 
 Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
 
-Create and run a cleanup process using the process at `skills\babysit\process\cradle\cleanup-runs.js/processes/cleanup-runs.js`.
+Resolve the active process library with:
+
+```bash
+babysitter process-library:active --json
+```
+
+Read `binding.dir` from that JSON and create/run the cleanup process from `cradle/cleanup-runs.js#process` relative to that active library root. Do not use plugin-cache-relative cradle paths.
 
 Implementation notes (for the process):
 - Parse arguments for `--dry-run` flag (if present, set dryRun: true in inputs) and `--keep-days N` (default: 7)

package/skills/contrib/SKILL.md

@@ -5,30 +5,30 @@ description: Submit feedback or contribute to babysitter project
 
 # contrib
 
-Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
-
-## Process Routing
-
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+## Process Routing
+
 Contribution processes live under the active process library's `cradle/` directory. Resolve the active library root with `babysitter process-library:active --json` and route based on arguments:
-
-### Issue-based (opens a GitHub issue in a5c-ai/babysitter)
- * **Bug report** → `cradle/bug-report.js#process` — Report a bug in the SDK, CLI, process library, etc.
- * **Feature request** → `cradle/feature-request.js#process` — Request a new feature or enhancement
- * **Documentation question** → `cradle/documentation-question.js#process` — Ask about undocumented behavior or missing docs
-
-### PR-based (forks repo, creates branch, submits PR to a5c-ai/babysitter)
- * **Bugfix** → `cradle/bugfix.js#process` — User already has the fix for a bug
- * **Feature implementation** → `cradle/feature-implementation-contribute.js#process` — User already has a feature implementation
- * **Harness integration** → `cradle/feature-harness-integration-contribute.js#process` — User has a harness (CI/CD, IDE, editor) integration
- * **Library contribution** → `cradle/library-contribution.js#process` — New or improved process/skill/subagent for the library
- * **Documentation answer** → `cradle/documentation-contribute-answer.js#process` — User has an answer for an unanswered docs question
-
-### Router (when arguments are empty or general)
- * **Contribute** → `cradle/contribute.js#process` — Explains contribution types and routes to the specific process
-
-## Contribution Rules
-
- * PR-based contributions: fork the babysitter repo (a5c-ai/babysitter) for the user, ask to star if not already starred, perform changes, submit PR
- * Issue-based contributions: gather details, search for duplicates, review, then open an issue in a5c-ai/babysitter
- * Add breakpoints (permissions) before ALL gh actions (fork, star, submit PR/issue) to allow user review and cancellation
+
+### Issue-based (opens a GitHub issue in a5c-ai/babysitter)
+ * **Bug report** → `cradle/bug-report.js#process` — Report a bug in the SDK, CLI, process library, etc.
+ * **Feature request** → `cradle/feature-request.js#process` — Request a new feature or enhancement
+ * **Documentation question** → `cradle/documentation-question.js#process` — Ask about undocumented behavior or missing docs
+
+### PR-based (forks repo, creates branch, submits PR to a5c-ai/babysitter)
+ * **Bugfix** → `cradle/bugfix.js#process` — User already has the fix for a bug
+ * **Feature implementation** → `cradle/feature-implementation-contribute.js#process` — User already has a feature implementation
+ * **Harness integration** → `cradle/feature-harness-integration-contribute.js#process` — User has a harness (CI/CD, IDE, editor) integration
+ * **Library contribution** → `cradle/library-contribution.js#process` — New or improved process/skill/subagent for the library
+ * **Documentation answer** → `cradle/documentation-contribute-answer.js#process` — User has an answer for an unanswered docs question
+
+### Router (when arguments are empty or general)
+ * **Contribute** → `cradle/contribute.js#process` — Explains contribution types and routes to the specific process
+
+## Contribution Rules
+
+ * PR-based contributions: fork the babysitter repo (a5c-ai/babysitter) for the user, ask to star if not already starred, perform changes, submit PR
+ * Issue-based contributions: gather details, search for duplicates, review, then open an issue in a5c-ai/babysitter
+ * Add breakpoints (permissions) before ALL gh actions (fork, star, submit PR/issue) to allow user review and cancellation
  * If arguments are empty: use the `contribute.js` router process to show options and route accordingly

package/skills/help/SKILL.md

@@ -180,13 +180,13 @@ SECONDARY COMMANDS
   a fuzzy comparison step before strict assertion. Implement this fix?")
 
 
-/babysitter:plugins [action]
-  Manage babysitter plugins: list installed plugins, browse marketplaces, install,
-  update, configure, uninstall, or create new plugins. Plugins are version-managed
-  instruction packages (not executable code) that guide the agent through install,
-  configure, and uninstall steps via markdown files.
+/babysitter:blueprints [action]
+  Manage Babysitter blueprints: list installed blueprints, browse marketplaces,
+  install, update, configure, uninstall, or create new blueprints. Blueprints are
+  version-managed instruction packages or process bundles that guide the agent
+  through install, configure, and uninstall steps.
 
-  Without arguments: shows installed plugins (name, version, marketplace, dates) and
+  Without arguments: shows installed blueprints (name, version, marketplace, dates) and
   available marketplaces. With arguments: routes to the specific action.
 
   Key actions:
@@ -194,11 +194,11 @@ SECONDARY COMMANDS
   - configure <name> --global|--project: fetch configure.md and walk through options
   - update <name> --global|--project: resolve migration chain via BFS and apply steps
   - uninstall <name> --global|--project: fetch uninstall.md and execute removal
-  - create: scaffold a new plugin package with the meta/plugin-creation process
+  - create: scaffold a new blueprint package
 
-  Example: /babysitter:plugins install sound-hooks --project
+  Example: /babysitter:blueprints install sound-hooks --project
   (fetches sound-hooks from marketplace, reads install.md, walks you through player
-  detection, sound selection, hook configuration, and registers in plugin-registry.json)
+  detection, sound selection, hook configuration, and registers the blueprint)
 
 
 /babysitter:contrib [feedback]

package/skills/plan/SKILL.md

@@ -5,4 +5,14 @@ description: Plan a babysitter run. use this command to plan a complex workflow,
 
 # plan
 
-Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). focus on creating the best process possible, but without creating and running the actual run.
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). Focus on creating the best process possible, but without creating and running the actual run.
+
+Before drafting the process, run Phase 0 -- REUSE-AUDIT: extract keyword nouns and verbs from the request, scan for matching existing migrations, API routes, environment variables, SDK dependencies, and imports, honor `.a5c/reuse-audit.json` when present, and put a `Reuse-audit findings (REVIEW BEFORE PROCEEDING)` block before Phase 1 of the plan.
+
+## Process Shape Selection
+
+Choose the process shape before authoring `process.js`:
+
+- Use a flat phase list when the spec is well-defined, the work is wiring or composition, the bug class is already known if this is a fix, and execution should proceed sequentially through clear phases.
+- Use a HYPOTHESES tree when the bug class is unknown, forensics are required, multiple causal models compete, and each hypothesis needs its own observations, falsifying observations, and follow-up phases.
+- Rule of thumb: if the first phase is "investigate", use HYPOTHESES-tree mode. If the first phase is "implement X", use flat-phase-list mode.

package/skills/plugins/SKILL.md

@@ -1,257 +1,24 @@
 ---
 name: plugins
-description: manage babysitter plugins. use this command to see the list of installed babysitter plugins, their status, and manage them (install, update, uninstall, list from marketplace, add marketplace, configure plugin, create new plugin, etc).
+description: deprecated alias for the Babysitter blueprints command. Use /babysitter:blueprints for marketplace installables.
 ---
 
 # plugins
 
-This command installs and manages plugins for babysitter. A plugin is a version-managed package of contextual instructions (for install, uninstall, configure, and update/migrate between versions), not a conventional software plugin.
-
-if the command is run without arguments, it lists all installed plugins with their name, version, marketplace, installation date, and last update date. as well as marketplaces added to the system. and instructions on how to install new plugins from marketplaces.
-if there are no marketplaces added, add the default marketplace:
-```bash
-babysitter plugin:add-marketplace --marketplace-url https://github.com/a5c-ai/babysitter --marketplace-path plugins/a5c/marketplace/marketplace.json --global --json
-```
-
-Plugins can be installed at two scopes:
-- **global** (`--global`): stored under `~/.a5c/`, available for all projects
-- **project** (`--project`): stored under `<projectDir>/.a5c/`, project-specific
-
-## Marketplace Management
-
-Marketplaces are git repositories containing a `marketplace.json` manifest and plugin package directories. The SDK clones them locally with `--depth 1`.
-
-**Storage locations:**
-- Global: `~/.a5c/marketplaces/<name>/`
-- Project: `<projectDir>/.a5c/marketplaces/<name>/`
-
-The marketplace name is derived from the git URL's last path segment (stripping `.git` suffix and trailing slashes).
-
-### Adding a marketplace
-
-```bash
-babysitter plugin:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]
-```
-
-Clones the marketplace repository to the local marketplaces directory. Use `--marketplace-path` to specify the relative path to `marketplace.json` within the repo (for monorepos or repos where the manifest is not at the root). Use `--marketplace-branch` to clone a specific branch, tag, or ref (defaults to the repo's default branch). Use `--force` to replace an existing marketplace clone (deletes and re-clones).
-
-### Updating a marketplace
-
-```bash
-babysitter plugin:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]
-```
-
-Runs `git pull` on the local marketplace clone to fetch latest changes. Use `--marketplace-branch` to switch to a different branch before pulling (works even with shallow clones).
-
-### Listing plugins in a marketplace
-
-```bash
-babysitter plugin:list-plugins --marketplace-name <name> --global|--project [--json]
-```
-
-Reads the `marketplace.json` manifest and returns all available plugins sorted alphabetically by name. Each entry includes: name, description, latestVersion, versions array, packagePath, tags, and author.
-
-## Plugin Installation
-
-**Note:** For `plugin:install`, `plugin:update`, `plugin:configure`, and `plugin:list-plugins`, the `--marketplace-name` flag is auto-detected when only one marketplace is cloned for the given scope. You can omit it if there's only one marketplace.
-
-### Flow
-
-1. Update the marketplace: `babysitter plugin:update-marketplace --marketplace-name <name> --global|--project`
-2. Check current state: `babysitter plugin:list-installed --global|--project` to see installed plugins and versions
-3. Install the plugin:
-
-```bash
-babysitter plugin:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
-```
-
-This command resolves the plugin package path from the marketplace manifest, reads `install.md` from the plugin package directory, and returns the installation instructions. If an `install-process.js` file exists, the instructions may reference it as an automated install process.
-
-4. The agent performs the installation steps as defined in `install.md`
-5. The agent updates the registry:
-
-```bash
-babysitter plugin:update-registry --plugin-name <name> --plugin-version <ver> --marketplace-name <mp> --global|--project [--json]
-```
-
-## Plugin Update (with migrations)
-
-```bash
-babysitter plugin:update --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
-```
-
-This command:
-1. Reads the currently installed version from the registry
-2. Resolves the latest version from the marketplace manifest
-3. Looks in the plugin package's `migrations/` directory for migration files
-4. Uses BFS over the migration graph to find the shortest path from the installed version to the target version
-5. Returns the ordered migration instructions (content of each migration file in sequence)
-
-**Migration filename format:** `<fromVersion>_to_<toVersion>.<ext>` where:
-- Versions may contain alphanumerics, dots, dashes (e.g. `1.0.0`, `2.0.0-beta`)
-- Extensions: `.md` for markdown instructions, `.js` for executable process files
-- Examples: `1.0.0_to_1.1.0.md`, `2.0.0-beta_to_2.0.0.js`
-
-After performing the migration steps, update the registry:
-
-```bash
-babysitter plugin:update-registry --plugin-name <name> --plugin-version <new-ver> --marketplace-name <mp> --global|--project [--json]
-```
-
-## Plugin Uninstallation
-
-```bash
-babysitter plugin:uninstall --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
-```
-
-Reads `uninstall.md` from the plugin package directory and returns the uninstall instructions. After performing the uninstall steps, remove from registry:
-
-```bash
-babysitter plugin:remove-from-registry --plugin-name <name> --global|--project [--json]
-```
-
-## Plugin Configuration
-
-```bash
-babysitter plugin:configure --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
-```
-
-Reads `configure.md` from the plugin package directory and returns configuration instructions.
-
-## Registry Management
-
-The plugin registry (`plugin-registry.json`) tracks installed plugins with schema version `2026.01.plugin-registry-v1`. Writes use atomic file operations (temp + rename) for crash safety.
-
-**Storage locations:**
-- Global: `~/.a5c/plugin-registry.json`
-- Project: `<projectDir>/.a5c/plugin-registry.json`
-
-### List installed plugins
-
-```bash
-babysitter plugin:list-installed --global|--project [--json]
-```
-
-Returns all installed plugins sorted alphabetically. In `--json` mode, returns an array of registry entries. In human mode, displays a formatted table with name, version, marketplace, and timestamps.
-
-### Remove from registry
-
-```bash
-babysitter plugin:remove-from-registry --plugin-name <name> --global|--project [--json]
-```
-
-Removes a plugin entry from the registry. Returns error if the plugin is not present.
-
-## Plugin Creation
-
-To create a new plugin package from scratch, use the `meta/plugin-creation` babysitter process. This process guides you through requirements analysis, structure design, instruction authoring, optional process file generation, validation, and marketplace integration.
-
-### Using the plugin creation process
-
-Orchestrate a babysitter run with the plugin creation process:
-
-```bash
-# Create inputs file
-cat > /tmp/plugin-inputs.json << 'EOF'
-{
-  "pluginName": "my-plugin",
-  "description": "What the plugin does — be specific about install/configure/uninstall behavior",
-  "scope": "project",
-  "outputDir": "./plugins",
-  "components": {
-    "installProcess": false,
-    "configureProcess": false,
-    "uninstallProcess": false,
-    "migrations": false,
-    "processFiles": false
-  },
-  "marketplace": {
-    "name": "my-marketplace",
-    "author": "my-org",
-    "tags": ["category1", "category2"]
-  }
-}
-EOF
-
-# Create and run
-babysitter run:create \
-  --process-id meta/plugin-creation \
-  --entry library/specializations/meta/plugin-creation.js#process \
-  --inputs /tmp/plugin-inputs.json \
-  --prompt "Create a new babysitter plugin package" \
-  --json
-```
-
-### What the process generates
-
-The process creates a complete plugin package directory:
-
-| File | Description |
-|------|-------------|
-| `install.md` | Agent-readable installation instructions with numbered steps |
-| `uninstall.md` | Reversal instructions for clean removal |
-| `configure.md` | Configuration options table and adjustment instructions |
-| `install-process.js` | *(optional)* Automated babysitter process for complex install steps |
-| `configure-process.js` | *(optional)* Automated configuration process |
-| `process/main.js` | *(optional)* Main process the plugin contributes |
-| `marketplace-entry.json` | Ready-to-use marketplace.json entry for publishing |
-
-### Process phases
-
-1. **Requirements Analysis** — Analyzes plugin purpose, prerequisites, config options, file structure
-2. **Structure Design** — Plans directory layout and file inventory (with review breakpoint)
-3. **Instruction Authoring** — Writes install.md, uninstall.md, configure.md
-4. **Process Files** — Creates optional babysitter process files (install-process.js, configure-process.js, process/main.js)
-5. **Validation** — Verifies package completeness, instruction quality, path correctness
-6. **Marketplace Integration** — Generates marketplace.json entry for publishing
-
-### Quick creation (without orchestration)
-
-For simple plugins that only need instruction files, you can create the package manually following the structure below and the [Plugin Author Guide](docs/plugins/plugin-author-guide.md).
-
-## Plugin Package Structure
-
-```
-my-plugin/
-  package.json         # Optional (name field used as plugin ID, falls back to directory name)
-  install.md           # Markdown instructions for installation
-  uninstall.md         # Markdown instructions for removal
-  configure.md         # Markdown instructions for configuration
-  install-process.js   # Optional automated install process
-  uninstall-process.js # Optional automated uninstall process
-  configure-process.js # Optional automated configure process
-  migrations/          # Version migration files
-    1.0.0_to_1.1.0.md
-    1.1.0_to_2.0.0.js
-  process/             # Process definition files (collected recursively)
-    main.js
-```
-
-## All CLI Commands Summary
-
-All commands accept `--json` for machine-readable output and `--global|--project`.
-
-| Command | Required Flags | Description |
-|---------|---------------|-------------|
-| `plugin:add-marketplace` | `--marketplace-url`, `--global\|--project` [`--marketplace-path`, `--marketplace-branch`, `--force`] | Clone a marketplace repository |
-| `plugin:update-marketplace` | `--marketplace-name`, `--global\|--project` [`--marketplace-branch`] | Pull latest marketplace changes (optionally switch branch) |
-| `plugin:list-plugins` | `--marketplace-name`, `--global\|--project` | List available plugins in a marketplace |
-| `plugin:install` | `--plugin-name`, `--marketplace-name`, `--global\|--project` | Get install instructions for a plugin |
-| `plugin:uninstall` | `--plugin-name`, `--marketplace-name`, `--global\|--project` | Get uninstall instructions for a plugin |
-| `plugin:update` | `--plugin-name`, `--marketplace-name`, `--global\|--project` | Resolve migration chain and get update instructions |
-| `plugin:configure` | `--plugin-name`, `--marketplace-name`, `--global\|--project` | Get configuration instructions for a plugin |
-| `plugin:list-installed` | `--global\|--project` | List all installed plugins |
-| `plugin:update-registry` | `--plugin-name`, `--plugin-version`, `--marketplace-name`, `--global\|--project` | Register or update a plugin entry |
-| `plugin:remove-from-registry` | `--plugin-name`, `--global\|--project` | Remove a plugin entry from the registry |
-
-## After Plugin Work: Contribute Back
-
-After working with plugins, prompt the user to share improvements or report issues:
-
-- **Improved a plugin's install/configure/uninstall instructions**: `/babysitter:contrib library contribution: improved [plugin-name] [install|configure|uninstall] instructions`
-- **Created a new plugin**: `/babysitter:contrib library contribution: new plugin [plugin-name] -- [description]`
-- **Found a bug in a plugin or the plugin system**: `/babysitter:contrib bug report: [description, e.g. "plugin:update-registry fails when marketplace hasn't been cloned"]`
-- **Plugin install/configure instructions were confusing or wrong**: `/babysitter:contrib bug report: [plugin-name] install instructions [description of what was wrong]`
-- **Have an idea for a new plugin**: `/babysitter:contrib feature request: plugin idea -- [description]`
-
-Even reporting that a plugin's instructions were unclear helps improve it for the next user.
+This command is a deprecated alias for `/babysitter:blueprints`.
+
+For Babysitter marketplace installables, use blueprints terminology and the `babysitter blueprints:*` CLI command family:
+
+```bash
+babysitter blueprints:list-installed --global|--project [--json]
+babysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] --global|--project [--json]
+babysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]
+babysitter blueprints:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprints:update --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprints:configure --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprints:uninstall --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+```
+
+The `--plugin-name` flag remains for CLI compatibility with existing marketplace manifests. Describe the installable as a blueprint in user-facing text.
+
+Agent harness plugins are not renamed. `CLAUDE_PLUGIN_ROOT`, `PI_PLUGIN_ROOT`, `.claude/plugins/`, hooks-adapter, extensions-adapter, and agent plugin manifests remain plugin concepts.

package/skills/project-install/SKILL.md

@@ -5,8 +5,8 @@ description: Set up a project for babysitting. Guides you through onboarding a n
 
 # project-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/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

@@ -5,7 +5,7 @@ description: Orchestrate a babysitter run. use this command to start babysitting
 
 # yolo
 
-Run the Babysitter orchestration instructions directly through the CLI, without any user interaction or breakpoints. In Claude Code, use Bash to run `babysitter instructions:babysit-skill --harness claude-code --no-interactive`; in Codex, run `babysitter instructions:babysit-skill --harness codex --no-interactive`; in other harnesses, use the same command with that harness id. Then follow the returned instructions in this same turn until completion proof is produced. Do not stop after reading the instructions, do not invoke the Skill tool first, and use the non-interactive/no-breakpoints path when the instructions offer a mode choice.
+Run the Babysitter orchestration instructions directly through the CLI, without any user interaction or breakpoints. Use Bash to run `babysitter instructions:babysit-skill --harness codex --no-interactive`, then follow the returned instructions in this same turn until completion proof is produced. Do not stop after reading the instructions, do not invoke the Skill tool first, and use the non-interactive/no-breakpoints path when the instructions offer a mode choice.
 
 User arguments for this command: