@a5c-ai/babysitter-gemini-cli 5.0.1-staging.e920fef118ef → 5.0.1-staging.fa900f15bc4d

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a5c-ai/babysitter-gemini-cli",
-  "version": "5.0.1-staging.e920fef118ef",
+  "version": "5.0.1-staging.fa900f15bc4d",
   "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",
@@ -34,7 +34,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@a5c-ai/babysitter-sdk": "5.0.1-staging.e920fef118ef"
+    "@a5c-ai/babysitter-sdk": "5.0.1-staging.fa900f15bc4d"
   },
   "repository": {
     "type": "git",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "babysitter",
-  "version": "5.0.1-staging.e920fef118ef",
+  "version": "5.0.1-staging.fa900f15bc4d",
   "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/babysit/SKILL.md

@@ -9,6 +9,17 @@ version: 0.1.3
 
 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
@@ -17,11 +28,13 @@ Read the SDK version from `versions.json` to ensure version compatibility:
 
 ```bash
 SDK_VERSION=$(node -e "try{console.log(JSON.parse(require('fs').readFileSync('${CLAUDE_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@$SDK_VERSION || npm i -g @a5c-ai/babysitter-sdk@latest
 
 CLI="npx -y @a5c-ai/babysitter-sdk@$SDK_VERSION"
 ```
 
+If the pinned version fails to install (e.g. not yet published), the fallback installs `latest`.
+
 If `babysitter` is already installed globally at the correct version, you may use `CLI="babysitter"` instead.
 
 ### jq

package/versions.json

@@ -1,4 +1,4 @@
 {
-  "sdkVersion": "5.0.1-staging.e920fef118ef",
-  "extensionVersion": "5.0.1-staging.e920fef118ef"
+  "sdkVersion": "5.0.1-staging.fa900f15bc4d",
+  "extensionVersion": "5.0.1-staging.fa900f15bc4d"
 }