@a5c-ai/babysitter-cursor 0.1.1-staging.d0170171 → 0.1.1-staging.f2d9bb68

package/.cursor-plugin/plugin.json

@@ -1,11 +1,10 @@
 {
-  "name": "babysitter-cursor",
+  "name": "babysitter",
   "version": "0.1.0",
   "description": "Babysitter orchestration plugin for Cursor IDE/CLI with lifecycle hooks and SDK-managed process-library bootstrapping",
   "author": {
     "name": "a5c.ai",
-    "email": "support@a5c.ai",
-    "url": "https://github.com/a5c-ai/babysitter"
+    "email": "support@a5c.ai"
   },
   "homepage": "https://github.com/a5c-ai/babysitter/tree/main/plugins/babysitter-cursor#readme",
   "repository": "https://github.com/a5c-ai/babysitter",
@@ -18,7 +17,6 @@
     "skills"
   ],
   "skills": "skills/",
-  "commands": [],
-  "hooks": "hooks.json",
-  "logo": null
+  "commands": "commands/",
+  "hooks": "hooks/hooks-cursor.json"
 }

package/README.md

@@ -27,22 +27,27 @@ npm install -g @a5c-ai/babysitter-sdk
 
 ### Via Cursor Marketplace (recommended)
 
-Install directly from the Cursor Marketplace:
+Install through Cursor's marketplace UI using the repo-root
+`/.cursor-plugin/marketplace.json` manifest:
 
-1. Open **Cursor IDE** and navigate to **Settings > Plugins**
-2. Search for **babysitter-cursor**
-3. Click **Install**
+1. Add this repository as a Cursor marketplace source
+2. Open the marketplace entry named **a5c-ai**
+3. Install the plugin named **babysitter**
 
 ### Via Babysitter plugin manager
 
+This path installs the Babysitter plugin package named
+`babysitter-cursor` from the SDK marketplace, not the Cursor UI plugin
+entry:
+
 ```bash
-babysitter plugin:install babysitter-cursor --marketplace-name a5c.ai --global
+babysitter plugin:install babysitter-cursor --marketplace-name a5c-ai --global
 ```
 
 ### Workspace installation
 
 ```bash
-babysitter plugin:install babysitter-cursor --marketplace-name a5c.ai --project
+babysitter plugin:install babysitter-cursor --marketplace-name a5c-ai --project
 ```
 
 If the workspace does not already have an active process-library binding, the
@@ -76,6 +81,8 @@ Copy the plugin directory to your local Cursor plugins path:
 
 ```bash
 cp -r plugins/babysitter-cursor ~/.cursor/plugins/local/babysitter-cursor
+# Or symlink for faster iteration:
+ln -s "$(pwd)/plugins/babysitter-cursor" ~/.cursor/plugins/local/babysitter-cursor
 ```
 
 ## Uninstallation
@@ -95,10 +102,11 @@ babysitter plugin:uninstall babysitter-cursor --global
 ```
 plugins/babysitter-cursor/
   .cursor-plugin/
-    plugin.json              # Cursor Marketplace manifest
-  plugin.json                # Plugin manifest (skills dir, hooks path, metadata)
-  hooks.json                 # Hook configuration (sessionStart, stop)
+    plugin.json              # Cursor plugin manifest (skills, commands, hooks, metadata)
+  plugin.json                # Babysitter plugin manifest (skills dir, hooks path, metadata)
+  hooks.json                 # Legacy/manual hook configuration
   hooks/
+    hooks-cursor.json        # Cursor plugin hook configuration
     session-start.sh         # SessionStart lifecycle hook (bash)
     session-start.ps1        # SessionStart lifecycle hook (PowerShell)
     stop-hook.sh             # Stop hook -- orchestration loop driver (bash)
@@ -129,7 +137,7 @@ plugins/babysitter-cursor/
 
 ## Hook Configuration
 
-The plugin declares lifecycle hooks in `hooks.json` using the version 1
+The plugin declares lifecycle hooks in `hooks/hooks-cursor.json` using the version 1
 format. Hook event names use camelCase (e.g., `sessionStart`, `stop`).
 
 ```json
@@ -139,16 +147,16 @@ format. Hook event names use camelCase (e.g., `sessionStart`, `stop`).
     "sessionStart": [
       {
         "type": "command",
-        "bash": "./hooks/session-start.sh",
-        "powershell": "./hooks/session-start.ps1",
+        "bash": "bash \"./hooks/session-start.sh\"",
+        "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/session-start.ps1\"",
         "timeoutSec": 30
       }
     ],
     "stop": [
       {
         "type": "command",
-        "bash": "./hooks/stop-hook.sh",
-        "powershell": "./hooks/stop-hook.ps1",
+        "bash": "bash \"./hooks/stop-hook.sh\"",
+        "powershell": "powershell -NoProfile -ExecutionPolicy Bypass -File \"./hooks/stop-hook.ps1\"",
         "loop_limit": null
       }
     ]
@@ -265,7 +273,7 @@ When Cursor attempts to end its turn, this hook intercepts the exit and:
 
 This is what keeps Babysitter iterating autonomously -- each turn performs
 one orchestration phase, and the stop hook decides whether to loop or yield.
-The `loop_limit: null` setting in `hooks.json` allows unlimited iterations.
+The `loop_limit: null` setting in `hooks/hooks-cursor.json` allows unlimited iterations.
 
 **Important:** The stop hook uses `{followup_message: "..."}` to signal
 continuation, NOT `{decision: "block"}`. This is a Cursor-specific
@@ -305,7 +313,7 @@ The Cursor marketplace manifest lives at `.cursor-plugin/plugin.json`:
 
 ```json
 {
-  "name": "babysitter-cursor",
+  "name": "babysitter",
   "version": "0.1.0",
   "description": "Babysitter orchestration plugin for Cursor IDE/CLI ...",
   "author": {
@@ -317,36 +325,35 @@ The Cursor marketplace manifest lives at `.cursor-plugin/plugin.json`:
   "repository": "https://github.com/a5c-ai/babysitter",
   "license": "MIT",
   "skills": "skills/",
-  "hooks": "hooks.json"
+  "hooks": "hooks/hooks-cursor.json"
 }
 ```
 
 The `skills` field points to the skills directory where Cursor
 auto-discovers `SKILL.md` files in subdirectories. The `hooks` field
-references the `hooks.json` configuration file.
+references the `hooks/hooks-cursor.json` configuration file.
 
 ### Marketplace Manifest
 
-To distribute through a marketplace, add the plugin to the marketplace's
-`marketplace.json`:
+The repo-root Cursor marketplace manifest lives at `/.cursor-plugin/marketplace.json`:
 
 ```json
 {
-  "name": "a5c.ai",
+  "name": "a5c-ai",
   "owner": {
-    "name": "a5c.ai",
+    "name": "a5c-ai",
     "email": "support@a5c.ai"
   },
   "metadata": {
     "description": "Babysitter orchestration plugins",
-    "version": "1.0.0"
+    "pluginRoot": "plugins"
   },
   "plugins": [
     {
-      "name": "babysitter-cursor",
+      "name": "babysitter",
       "description": "Multi-step workflow orchestration for Cursor IDE",
       "version": "0.1.0",
-      "source": "./plugins/babysitter-cursor"
+      "source": "babysitter-cursor"
     }
   ]
 }
@@ -355,9 +362,9 @@ To distribute through a marketplace, add the plugin to the marketplace's
 ### User Commands
 
 ```bash
-babysitter plugin:add-marketplace --marketplace-url https://github.com/a5c-ai/babysitter --global
-babysitter plugin:list-plugins --marketplace-name a5c.ai --global
-babysitter plugin:install babysitter-cursor --marketplace-name a5c.ai --global
+babysitter plugin:add-marketplace --marketplace-url https://github.com/a5c-ai/babysitter --marketplace-path plugins/a5c/marketplace/marketplace.json --global
+babysitter plugin:list-plugins --marketplace-name a5c-ai --global
+babysitter plugin:install babysitter-cursor --marketplace-name a5c-ai --global
 ```
 
 ## Troubleshooting
@@ -378,6 +385,9 @@ Also check log output in `<plugin-root>/.a5c/logs/`:
 - `babysitter-stop-hook-stderr.log`
 - `babysitter-session-start-hook-stderr.log`
 
+- `$HOME/.a5c/logs/` and relevant logs and run/session specific logs there
+
+
 ### Run stuck or not progressing
 
 Check the run status and diagnose:
@@ -429,7 +439,7 @@ modes.
 On native Windows, hook execution depends on shell configuration. The
 plugin includes both `bash` (.sh) and `powershell` (.ps1) hook scripts
 to maximize compatibility. If hooks do not fire, try running from Git Bash
-or WSL. The `hooks.json` file includes `powershell` entries alongside
+or WSL. The Cursor hook manifest includes explicit `powershell` entries alongside
 `bash` entries for Windows PowerShell execution support.
 
 ## Development / Contributing

package/bin/install-shared.js

@@ -5,7 +5,7 @@ const os = require('os');
 const path = require('path');
 const { spawnSync } = require('child_process');
 
-const PLUGIN_NAME = 'babysitter-cursor';
+const PLUGIN_NAME = 'babysitter';
 const PLUGIN_CATEGORY = 'Coding';
 const HOOK_SCRIPT_NAMES = [
   'session-start.sh',
@@ -20,12 +20,17 @@ const DEFAULT_MARKETPLACE = {
   },
   plugins: [],
 };
+const MANAGED_HOOKS_CONFIG_PATHS = [
+  path.join('hooks', 'hooks-cursor.json'),
+  'hooks.json',
+];
 const PLUGIN_BUNDLE_ENTRIES = [
   '.cursor-plugin',
   'plugin.json',
   'hooks.json',
   'hooks',
   'skills',
+  'commands',
   'versions.json',
   '.cursorrules',
 ];
@@ -52,7 +57,7 @@ function getHomePluginRoot() {
   if (process.env.BABYSITTER_CURSOR_PLUGIN_DIR) {
     return path.resolve(process.env.BABYSITTER_CURSOR_PLUGIN_DIR, PLUGIN_NAME);
   }
-  return path.join(getCursorHome(), 'plugins', PLUGIN_NAME);
+  return path.join(getCursorHome(), 'plugins', 'local', PLUGIN_NAME);
 }
 
 function getHomeMarketplacePath() {
@@ -135,15 +140,33 @@ function readJson(filePath) {
   return JSON.parse(fs.readFileSync(filePath, 'utf8'));
 }
 
+function getManagedHooksConfigPath(packageRoot) {
+  for (const relativePath of MANAGED_HOOKS_CONFIG_PATHS) {
+    const candidate = path.join(packageRoot, relativePath);
+    if (fs.existsSync(candidate)) {
+      return candidate;
+    }
+  }
+  return null;
+}
+
 function writeJson(filePath, value) {
   writeFileIfChanged(filePath, `${JSON.stringify(value, null, 2)}\n`);
 }
 
+function normalizeMarketplaceName(name) {
+  const raw = String(name || '').trim();
+  const sanitized = raw
+    .replace(/[^A-Za-z0-9_-]+/g, '-')
+    .replace(/^-+|-+$/g, '');
+  return sanitized || DEFAULT_MARKETPLACE.name;
+}
+
 function ensureMarketplaceEntry(marketplacePath, pluginSourcePath) {
   const marketplace = fs.existsSync(marketplacePath)
     ? readJson(marketplacePath)
     : { ...DEFAULT_MARKETPLACE, plugins: [] };
-  marketplace.name = marketplace.name || DEFAULT_MARKETPLACE.name;
+  marketplace.name = normalizeMarketplaceName(marketplace.name);
   marketplace.interface = marketplace.interface || {};
   marketplace.interface.displayName =
     marketplace.interface.displayName || DEFAULT_MARKETPLACE.interface.displayName;
@@ -186,8 +209,8 @@ function removeMarketplaceEntry(marketplacePath) {
 }
 
 function mergeManagedHooksConfig(packageRoot, cursorHome) {
-  const hooksJsonPath = path.join(packageRoot, 'hooks.json');
-  if (!fs.existsSync(hooksJsonPath)) return;
+  const hooksJsonPath = getManagedHooksConfigPath(packageRoot);
+  if (!hooksJsonPath) return;
   const managedConfig = readJson(hooksJsonPath);
   const managedHooks = managedConfig.hooks || {};
   const hooksConfigPath = path.join(cursorHome, 'hooks.json');
@@ -358,6 +381,7 @@ module.exports = {
   copyPluginBundle,
   ensureGlobalProcessLibrary,
   ensureMarketplaceEntry,
+  getManagedHooksConfigPath,
   getCursorHome,
   getHomeMarketplacePath,
   getHomePluginRoot,
@@ -366,4 +390,5 @@ module.exports = {
   removeMarketplaceEntry,
   warnWindowsHooks,
   writeJson,
+  normalizeMarketplaceName,
 };

package/bin/install.js

@@ -20,7 +20,7 @@ function main() {
   const pluginRoot = getHomePluginRoot();
   const marketplacePath = getHomeMarketplacePath();
 
-  console.log(`[babysitter-cursor] Installing plugin to ${pluginRoot}`);
+  console.log(`[babysitter] Installing plugin to ${pluginRoot}`);
 
   try {
     copyPluginBundle(PACKAGE_ROOT, pluginRoot);
@@ -28,17 +28,17 @@ function main() {
     installCursorSurface(PACKAGE_ROOT, cursorHome);
 
     const active = ensureGlobalProcessLibrary(PACKAGE_ROOT);
-    console.log(`[babysitter-cursor]   marketplace: ${marketplacePath}`);
-    console.log(`[babysitter-cursor]   process library: ${active.binding?.dir}`);
+    console.log(`[babysitter]   marketplace: ${marketplacePath}`);
+    console.log(`[babysitter]   process library: ${active.binding?.dir}`);
     if (active.defaultSpec?.cloneDir) {
-      console.log(`[babysitter-cursor]   process library clone: ${active.defaultSpec.cloneDir}`);
+      console.log(`[babysitter]   process library clone: ${active.defaultSpec.cloneDir}`);
     }
-    console.log(`[babysitter-cursor]   process library state: ${active.stateFile}`);
+    console.log(`[babysitter]   process library state: ${active.stateFile}`);
     warnWindowsHooks();
-    console.log('[babysitter-cursor] Installation complete!');
-    console.log('[babysitter-cursor] Restart Cursor to pick up the installed plugin and config changes.');
+    console.log('[babysitter] Installation complete!');
+    console.log('[babysitter] Restart Cursor to pick up the installed plugin and config changes.');
   } catch (err) {
-    console.error(`[babysitter-cursor] Failed to install plugin: ${err.message}`);
+    console.error(`[babysitter] Failed to install plugin: ${err.message}`);
     process.exitCode = 1;
   }
 }

package/bin/uninstall.js

@@ -19,10 +19,10 @@ function main() {
   if (fs.existsSync(pluginRoot)) {
     try {
       fs.rmSync(pluginRoot, { recursive: true, force: true });
-      console.log(`[babysitter-cursor] Removed ${pluginRoot}`);
+      console.log(`[babysitter] Removed ${pluginRoot}`);
       removedPlugin = true;
     } catch (err) {
-      console.warn(`[babysitter-cursor] Warning: Could not remove plugin directory ${pluginRoot}: ${err.message}`);
+      console.warn(`[babysitter] Warning: Could not remove plugin directory ${pluginRoot}: ${err.message}`);
     }
   }
 
@@ -30,11 +30,11 @@ function main() {
   removeManagedHooks(cursorHome);
 
   if (!removedPlugin) {
-    console.log('[babysitter-cursor] Plugin directory not found, config and hooks cleaned if present.');
+    console.log('[babysitter] Plugin directory not found, config and hooks cleaned if present.');
     return;
   }
 
-  console.log('[babysitter-cursor] Restart Cursor to complete uninstallation.');
+  console.log('[babysitter] Restart Cursor to complete uninstallation.');
 }
 
 main();

package/commands/assimilate.md

@@ -0,0 +1,37 @@
+---
+description: Assimilate an external methodology, harness, or specification into babysitter process definitions with skills and agents.
+argument-hint: Target to assimilate (e.g. repo URL, harness name, or spec path)
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+Use the assimilation domain processes from the active process library to convert external sources into well-defined babysitter process definitions with accompanying skills/ and agents/ directories.
+
+If the workspace does not already have an active process-library binding, initialize it first through the shared global SDK binding:
+
+```bash
+babysitter process-library:active --json
+```
+
+Run the process after formalizing it.
+
+Available assimilation workflows:
+- **methodology-assimilation** (`specializations/domains/assimilation/workflows/methodology-assimilation`) - Learns an external methodology from its repo and converts procedural instructions, commands, and manual flows into babysitter processes with refactored skills and agents. Supports output as methodology or specialization.
+- **harness integration** (`specializations/domains/assimilation/harness/*`) - Integrates babysitter SDK with a specific AI coding harness (generic, codex, opencode, gemini-cli, openclaw, antigravity).
+
+During the interview phase, determine which assimilation workflow to use based on the user's target:
+- If the target is a **repo URL or methodology name** then use the methodology-assimilation workflow.
+- If the target is a **harness name** (e.g. codex, opencode, antigravity) then use the matching harness process.
+- If the target is a **specification or other source** then adapt the methodology-assimilation workflow for the spec format.
+- If unclear, ask the user to clarify the assimilation target and type.
+
+## After Assimilation: Contribute Back
+
+After successfully assimilating a methodology or harness integration, prompt the user to share it with the community. The assimilated process definitions, skills, and agents could benefit other babysitter users:
+
+- **Completed a methodology assimilation**: `/babysitter:contrib library contribution: assimilated [methodology-name] into babysitter process definitions`
+- **Completed a harness integration**: `/babysitter:contrib library contribution: [harness-name] harness integration`
+- **Hit issues during assimilation** (e.g. unsupported patterns, missing SDK features): `/babysitter:contrib bug report: assimilation of [target] failed because [description]` or `/babysitter:contrib feature request: [what the SDK needs to support]`
+
+Even just reporting that an assimilation didn't work well helps improve babysitter for everyone.

package/commands/call.md

@@ -0,0 +1,7 @@
+---
+description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow.
+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
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).

package/commands/cleanup.md

@@ -0,0 +1,20 @@
+---
+description: Clean up .a5c/runs and .a5c/processes directories. Aggregates insights from completed/failed runs into docs/run-history-insights.md, then removes old run data and orphaned process files.
+argument-hint: "[--dry-run] [--keep-days N] Optional flags. --dry-run shows what would be removed without deleting. --keep-days N keeps runs newer than N days (default 7)."
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+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`.
+
+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

package/commands/contrib.md

@@ -0,0 +1,33 @@
+---
+description: Submit feedback or contribute to babysitter project
+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
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+## Process Routing
+
+Contribution processes live under the active process library's `cradle/` directory. Resolve the active library root with `babysitter process-library:active --json` and route based on arguments:
+
+### Issue-based (opens a GitHub issue in a5c-ai/babysitter)
+ * **Bug report** → `cradle/bug-report.js#process` — Report a bug in the SDK, CLI, process library, etc.
+ * **Feature request** → `cradle/feature-request.js#process` — Request a new feature or enhancement
+ * **Documentation question** → `cradle/documentation-question.js#process` — Ask about undocumented behavior or missing docs
+
+### PR-based (forks repo, creates branch, submits PR to a5c-ai/babysitter)
+ * **Bugfix** → `cradle/bugfix.js#process` — User already has the fix for a bug
+ * **Feature implementation** → `cradle/feature-implementation-contribute.js#process` — User already has a feature implementation
+ * **Harness integration** → `cradle/feature-harness-integration-contribute.js#process` — User has a harness (CI/CD, IDE, editor) integration
+ * **Library contribution** → `cradle/library-contribution.js#process` — New or improved process/skill/subagent for the library
+ * **Documentation answer** → `cradle/documentation-contribute-answer.js#process` — User has an answer for an unanswered docs question
+
+### Router (when arguments are empty or general)
+ * **Contribute** → `cradle/contribute.js#process` — Explains contribution types and routes to the specific process
+
+## Contribution Rules
+
+ * PR-based contributions: fork the babysitter repo (a5c-ai/babysitter) for the user, ask to star if not already starred, perform changes, submit PR
+ * Issue-based contributions: gather details, search for duplicates, review, then open an issue in a5c-ai/babysitter
+ * Add breakpoints (permissions) before ALL gh actions (fork, star, submit PR/issue) to allow user review and cancellation
+ * If arguments are empty: use the `contribute.js` router process to show options and route accordingly