@a5c-ai/babysitter-opencode 5.0.1-staging.d73033a7 → 5.0.1-staging.daf8e165bc4a

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,15 +7,43 @@ 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)
-- 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`.
@@ -363,13 +362,13 @@ Mark as FAIL if:
 - Parse the output and inspect the `resolvedFrom` field. Classify as follows:
   - `resolvedFrom: "pid-marker"` → mark as PASS ("Session ID derives from the live Claude Code ancestor process -- authoritative").
   - `resolvedFrom: "env-file"` → mark as PASS with a note ("CLAUDE_ENV_FILE was used; typically healthy").
-  - `resolvedFrom: "env-var"` → mark as WARN ("`BABYSITTER_SESSION_ID` is set without a corroborating PID marker. Likely stale from a prior Claude Code session -- see GitHub issue #130").
-    - Remediation: run `babysitter session:cleanup` and start a fresh Claude Code session, or `unset BABYSITTER_SESSION_ID` before invoking babysitter.
+  - `resolvedFrom: "env-var"` → mark as WARN ("`AGENT_SESSION_ID` is set without a corroborating PID marker. Likely stale from a prior Claude Code session -- see GitHub issue #130").
+    - Remediation: run `babysitter session:cleanup` and start a fresh Claude Code session, or `unset AGENT_SESSION_ID` before invoking babysitter.
   - `resolvedFrom: "none"` → mark as ERROR ("No session ID resolvable. Either no session-start hook fired, or the ancestor walk failed").
 
 **Env-var shadow check:**
 - Independently inspect `envVarPresent` and `envVarMatches` in the output.
-- If `envVarPresent && !envVarMatches`, mark as WARN ("`BABYSITTER_SESSION_ID` in env does not match the resolved session ID; a stale value is shadowing the authoritative one. Unset the env var").
+- If `envVarPresent && !envVarMatches`, mark as WARN ("`AGENT_SESSION_ID` in env does not match the resolved session ID; a stale value is shadowing the authoritative one. Unset the env var").
 
 ---
 
@@ -391,7 +390,7 @@ Mark as FAIL if:
 
 - Enumerate files in `~/.a5c/` matching the pattern `current-session-*-pid-*`.
 - Count markers per harness (derived from the filename).
-- If more than one live marker exists for the same harness, mark as INFO ("Multiple live Claude Code / harness sessions detected; ensure each shell scopes `BABYSITTER_SESSION_ID` appropriately -- the PID marker handles this automatically").
+- If more than one live marker exists for the same harness, mark as INFO ("Multiple live Claude Code / harness sessions detected; ensure each shell scopes `AGENT_SESSION_ID` appropriately -- the PID marker handles this automatically").
 - Otherwise mark as PASS.
 
 ---
@@ -502,7 +501,7 @@ babysitter session:cleanup --dry-run   # preview
 babysitter session:cleanup             # apply
 
 # 2. Unset a stale env var
-unset BABYSITTER_SESSION_ID
+unset AGENT_SESSION_ID
 
 # 3. Re-bind a run explicitly if needed
 babysitter session:resume --session-id <fresh-id> --state-dir ~/.a5c --run-id <runId> --runs-dir .a5c/runs

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]
@@ -231,9 +231,11 @@ SECONDARY COMMANDS
   effect status in your browser. Useful when running /yolo or /forever to watch
   progress without interrupting the run.
 
-  How it works: Runs npx @yoavmayer/babysitter-observer-dashboard@latest which watches
+  How it works: Runs npx @a5c-ai/babysitter-observer-dashboard@latest which watches
   the .a5c/runs/ directory (or a parent directory containing multiple projects) and
-  serves a live dashboard. The process is blocking -- it runs until you stop it.
+  serves a live dashboard. The process is blocking -- it runs until you stop it, and
+  it prints the local URL to share with the user. Do not use `babysitter observe`
+  as a fallback; the core Babysitter CLI does not expose that subcommand.
 
   Example: /babysitter:observe
   (opens browser showing all runs with live-updating task

package/skills/observe/SKILL.md

@@ -8,6 +8,11 @@ description: Launch the babysitter observer dashboard. Installs and runs the rea
 Run the babysitter observer dashboard:
 
 1. Determine the watch directory — this is usually the project's container directory (the parent of the project dir), or the current working directory if not specified.
-2. Launch the dashboard: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`
+2. Launch the standalone dashboard package: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`.
 3. This is a blocking process — it will keep running until stopped.
-4. Open the browser at the URL printed by the dashboard.
+4. Report the URL printed by the dashboard to the user, then open it in the browser.
+
+Do not fall back to `babysitter observe`; the core Babysitter CLI does not expose
+that subcommand. Some harness runtimes may provide a separate
+`agent-platform observe` surface, but this skill uses the verified standalone
+dashboard package.

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.
+This command is a deprecated alias for `/babysitter:blueprints`.
 
-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)
+For Babysitter marketplace installables, use blueprints terminology and the `babysitter blueprint:*` CLI command family:
 
 ```bash
-babysitter plugin:update --plugin-name <name> --marketplace-name <mp> --global|--project [--json]
+babysitter blueprint:list-installed --global|--project [--json]
+babysitter blueprint:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] --global|--project [--json]
+babysitter blueprint:list-plugins --marketplace-name <name> --global|--project [--json]
+babysitter blueprint:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprint:update --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprint:configure --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]
+babysitter blueprint:uninstall --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]`
+The `--plugin-name` flag remains for CLI compatibility with existing marketplace manifests. Describe the installable as a blueprint in user-facing text.
 
-Even reporting that a plugin's instructions were unclear helps improve it for the next user.
+Agent harness plugins are not renamed. `CLAUDE_PLUGIN_ROOT`, `PI_PLUGIN_ROOT`, `.claude/plugins/`, hooks-mux, extension-mux, and agent plugin manifests remain plugin concepts.

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.
+Run the Babysitter orchestration instructions directly through the CLI, without any user interaction or breakpoints. Use Bash to run `babysitter instructions:babysit-skill --harness opencode --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:
+
+$ARGUMENTS

package/versions.json

@@ -1,4 +1,4 @@
 {
-  "sdkVersion": "5.0.1-staging.d73033a7",
-  "pluginVersion": "0.1.0"
+  "sdkVersion": "5.0.1-staging.daf8e165bc4a",
+  "extensionVersion": "5.0.1-staging.daf8e165bc4a"
 }