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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -104,7 +104,7 @@ function ensureMarketplaceEntry(marketplacePath, pluginRoot) {
104
104
  name: PLUGIN_NAME,
105
105
  source: relSource,
106
106
  description: "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
107
- version: "5.0.1-staging.fa900f15bc4d",
107
+ version: "5.0.1-staging.ffad3b46492e",
108
108
  author: { name: "a5c.ai" },
109
109
  };
110
110
  if (idx >= 0) marketplace.plugins[idx] = entry;
@@ -1,3 +1,3 @@
1
1
  description = "Launch the babysitter observer dashboard. Installs and runs the real-time observer UI that watches babysitter runs, displaying task progress, journal events, and orchestration state in your browser."
2
2
 
3
- prompt = "Run the babysitter observer dashboard:\n\n1. 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.\n2. Launch the standalone dashboard package: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`.\n3. This is a blocking process — it will keep running until stopped.\n4. Report the URL printed by the dashboard to the user, then open it in the browser.\n\nDo not fall back to `babysitter observe`; the core Babysitter CLI does not expose\nthat subcommand. Some harness runtimes may provide a separate\n`babysitter-agent observe` surface, but this skill uses the verified standalone\ndashboard package."
3
+ prompt = "Run the babysitter observer dashboard:\n\n1. 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.\n2. Launch the standalone dashboard package: `npx -y @a5c-ai/babysitter-observer-dashboard@latest --watch-dir <dir>`.\n3. This is a blocking process — it will keep running until stopped.\n4. Report the URL printed by the dashboard to the user, then open it in the browser.\n\nDo not fall back to `babysitter observe`; the core Babysitter CLI does not expose\nthat subcommand. Some harness runtimes may provide a separate\n`agent-platform observe` surface, but this skill uses the verified standalone\ndashboard package."
@@ -1,3 +1,3 @@
1
1
  description = "Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run."
2
2
 
3
- prompt = "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.\n\nUser arguments for this command:\n\n$ARGUMENTS"
3
+ prompt = "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.\n\nUser arguments for this command:\n\n$ARGUMENTS"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@a5c-ai/babysitter-gemini-cli",
3
- "version": "5.0.1-staging.fa900f15bc4d",
3
+ "version": "5.0.1-staging.ffad3b46492e",
4
4
  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
5
5
  "scripts": {
6
6
  "deploy": "npm publish --access public",
@@ -34,7 +34,7 @@
34
34
  "access": "public"
35
35
  },
36
36
  "dependencies": {
37
- "@a5c-ai/babysitter-sdk": "5.0.1-staging.fa900f15bc4d"
37
+ "@a5c-ai/babysitter-sdk": "5.0.1-staging.ffad3b46492e"
38
38
  },
39
39
  "repository": {
40
40
  "type": "git",
package/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "babysitter",
3
- "version": "5.0.1-staging.fa900f15bc4d",
3
+ "version": "5.0.1-staging.ffad3b46492e",
4
4
  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
5
5
  "author": "a5c.ai",
6
6
  "license": "MIT",
package/versions.json CHANGED
@@ -1,4 +1,4 @@
1
1
  {
2
- "sdkVersion": "5.0.1-staging.fa900f15bc4d",
3
- "extensionVersion": "5.0.1-staging.fa900f15bc4d"
2
+ "sdkVersion": "5.0.1-staging.ffad3b46492e",
3
+ "extensionVersion": "5.0.1-staging.ffad3b46492e"
4
4
  }