@a5c-ai/babysitter-gemini-cli 5.1.1-staging.fee05906043b → 6.0.0

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.1.1-staging.fee05906043b",
107
+ version: "6.0.0",
108
108
  author: { name: "a5c.ai" },
109
109
  };
110
110
  if (idx >= 0) marketplace.plugins[idx] = entry;
@@ -1,3 +1,3 @@
1
1
  description = "manage Babysitter blueprints. Use this command to list installed blueprints, browse marketplaces, install, update, uninstall, configure, or create a new blueprint."
2
2
 
3
- prompt = "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.\n\nIf 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.\n\nBlueprints can be installed at two scopes:\n\n- **global** (`--global`): stored under `~/.a5c/`, available for all projects\n- **project** (`--project`): stored under `<projectDir>/.a5c/`, project-specific\n\n## Marketplace Management\n\nMarketplaces 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.\n\n### Add a marketplace\n\n```bash\nbabysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]\n```\n\n### Update a marketplace\n\n```bash\nbabysitter blueprints:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]\n```\n\n### List blueprints in a marketplace\n\n```bash\nbabysitter blueprints:list-plugins --marketplace-name <name> --global|--project [--json]\n```\n\n## Blueprint Lifecycle\n\nFor `blueprint:install`, `blueprint:update`, `blueprint:configure`, and `blueprint:list-plugins`, the `--marketplace-name` flag is auto-detected when only one marketplace is cloned for the selected scope.\n\n```bash\nbabysitter blueprints:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprints:update --plugin-name <name> --marketplace-name <mp> --global|--project [--json]\nbabysitter blueprints:configure --plugin-name <name> --marketplace-name <mp> --global|--project [--json]\nbabysitter blueprints:uninstall --plugin-name <name> --marketplace-name <mp> --global|--project [--json]\n```\n\nThe `--plugin-name` flag is preserved for CLI compatibility with existing marketplace manifests. User-facing docs should call the installable a blueprint.\n\n## Registry Management\n\n```bash\nbabysitter blueprints:list-installed --global|--project [--json]\nbabysitter blueprints:update-registry --plugin-name <name> --plugin-version <ver> --marketplace-name <mp> --global|--project [--json]\nbabysitter blueprints:remove-from-registry --plugin-name <name> --global|--project [--json]\n```\n\n## Deprecated Aliases\n\nThe old `plugin:*` commands remain available as deprecated aliases for one release. Prefer `blueprint:*` in new docs, skills, and process instructions.\n\n## Agent Plugins Are Separate\n\nDo 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."
3
+ prompt = "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.\n\nIf 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.\n\nBlueprints can be installed at two scopes:\n\n- **global** (`--global`): stored under `~/.a5c/`, available for all projects\n- **project** (`--project`): stored under `<projectDir>/.a5c/`, project-specific\n\n## Marketplace Management\n\nMarketplaces 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.\n\n### Add a marketplace\n\n```bash\nbabysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] [--marketplace-branch <ref>] [--force] --global|--project [--json]\n```\n\n### Update a marketplace\n\n```bash\nbabysitter blueprints:update-marketplace --marketplace-name <name> [--marketplace-branch <ref>] --global|--project [--json]\n```\n\n### List blueprints in a marketplace\n\n```bash\nbabysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]\n```\n\n## Blueprint Lifecycle\n\nFor `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.\n\n```bash\nbabysitter blueprints:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprints:update --plugin-name <name> --marketplace-name <mp> --global|--project [--json]\nbabysitter blueprints:configure --plugin-name <name> --marketplace-name <mp> --global|--project [--json]\nbabysitter blueprints:uninstall --plugin-name <name> --marketplace-name <mp> --global|--project [--json]\n```\n\nThe `--plugin-name` flag is preserved for CLI compatibility with existing marketplace manifests. User-facing docs should call the installable a blueprint.\n\n## Registry Management\n\n```bash\nbabysitter blueprints:list-installed --global|--project [--json]\nbabysitter blueprints:update-registry --plugin-name <name> --plugin-version <ver> --marketplace-name <mp> --global|--project [--json]\nbabysitter blueprints:remove-from-registry --plugin-name <name> --global|--project [--json]\n```\n\n## Deprecated Aliases\n\nThe old `plugin:*` commands remain available as deprecated aliases for one release. Prefer `blueprint:*` in new docs, skills, and process instructions.\n\n## Agent Plugins Are Separate\n\nDo 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."
@@ -1,3 +1,3 @@
1
1
  description = "deprecated alias for the Babysitter blueprints command. Use /babysitter:blueprints for marketplace installables."
2
2
 
3
- prompt = "This command is a deprecated alias for `/babysitter:blueprints`.\n\nFor Babysitter marketplace installables, use blueprints terminology and the `babysitter blueprint:*` CLI command family:\n\n```bash\nbabysitter blueprint:list-installed --global|--project [--json]\nbabysitter blueprint:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] --global|--project [--json]\nbabysitter blueprint:list-plugins --marketplace-name <name> --global|--project [--json]\nbabysitter blueprint:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprint:update --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprint:configure --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprint:uninstall --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\n```\n\nThe `--plugin-name` flag remains for CLI compatibility with existing marketplace manifests. Describe the installable as a blueprint in user-facing text.\n\nAgent harness plugins are not renamed. `CLAUDE_PLUGIN_ROOT`, `PI_PLUGIN_ROOT`, `.claude/plugins/`, hooks-adapter, extensions-adapter, and agent plugin manifests remain plugin concepts."
3
+ prompt = "This command is a deprecated alias for `/babysitter:blueprints`.\n\nFor Babysitter marketplace installables, use blueprints terminology and the `babysitter blueprints:*` CLI command family:\n\n```bash\nbabysitter blueprints:list-installed --global|--project [--json]\nbabysitter blueprints:add-marketplace --marketplace-url <url> [--marketplace-path <relative-path>] --global|--project [--json]\nbabysitter blueprints:list-blueprints --marketplace-name <name> --global|--project [--json]\nbabysitter blueprints:install --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprints:update --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprints:configure --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\nbabysitter blueprints:uninstall --plugin-name <name> [--marketplace-name <mp>] --global|--project [--json]\n```\n\nThe `--plugin-name` flag remains for CLI compatibility with existing marketplace manifests. Describe the installable as a blueprint in user-facing text.\n\nAgent 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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@a5c-ai/babysitter-gemini-cli",
3
- "version": "5.1.1-staging.fee05906043b",
3
+ "version": "6.0.0",
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.1.1-staging.fee05906043b"
37
+ "@a5c-ai/babysitter-sdk": "6.0.0"
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.1.1-staging.fee05906043b",
3
+ "version": "6.0.0",
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.1.1-staging.fee05906043b",
3
- "extensionVersion": "5.1.1-staging.fee05906043b"
2
+ "sdkVersion": "6.0.0",
3
+ "extensionVersion": "6.0.0"
4
4
  }