@a5c-ai/babysitter-opencode 5.0.1-staging.ae29cffafe6a → 5.0.1-staging.af82b26593a7

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.1-staging.ae29cffafe6a",
+    version: "5.0.1-staging.af82b26593a7",
     author: { name: "a5c.ai" },
   };
   if (idx >= 0) marketplace.plugins[idx] = entry;

package/commands/observe.md

@@ -13,5 +13,5 @@ Run the babysitter observer dashboard:
 
 Do not fall back to `babysitter observe`; the core Babysitter CLI does not expose
 that subcommand. Some harness runtimes may provide a separate
-`babysitter-agent observe` surface, but this skill uses the verified standalone
+`agent-platform observe` surface, but this skill uses the verified standalone
 dashboard package.

package/commands/yolo.md

@@ -4,7 +4,7 @@ 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-agent yolo --harness claude-code --workspace "$PWD" --prompt "<user arguments>" --json`; in Codex, run `babysitter-agent 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.
+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.
 
 User arguments for this command:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-opencode",
-  "version": "5.0.1-staging.ae29cffafe6a",
+  "version": "5.0.1-staging.af82b26593a7",
   "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",
@@ -35,7 +35,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@a5c-ai/babysitter-sdk": "5.0.1-staging.ae29cffafe6a"
+    "@a5c-ai/babysitter-sdk": "5.0.1-staging.af82b26593a7"
   },
   "repository": {
     "type": "git",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "babysitter",
-  "version": "5.0.1-staging.ae29cffafe6a",
+  "version": "5.0.1-staging.af82b26593a7",
   "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/skills/observe/SKILL.md

@@ -14,5 +14,5 @@ Run the babysitter observer dashboard:
 
 Do not fall back to `babysitter observe`; the core Babysitter CLI does not expose
 that subcommand. Some harness runtimes may provide a separate
-`babysitter-agent observe` surface, but this skill uses the verified standalone
+`agent-platform observe` surface, but this skill uses the verified standalone
 dashboard package.

package/skills/yolo/SKILL.md

@@ -5,7 +5,7 @@ description: Orchestrate a babysitter run. use this command to start babysitting
 
 # yolo
 
-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-agent yolo --harness claude-code --workspace "$PWD" --prompt "<user arguments>" --json`; in Codex, run `babysitter-agent 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.
+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.
 
 User arguments for this command:
 

package/versions.json

@@ -1,4 +1,4 @@
 {
-  "sdkVersion": "5.0.1-staging.ae29cffafe6a",
-  "extensionVersion": "5.0.1-staging.ae29cffafe6a"
+  "sdkVersion": "5.0.1-staging.af82b26593a7",
+  "extensionVersion": "5.0.1-staging.af82b26593a7"
 }