@botonic/nx-plugin 2.30.0 → 2.31.1-alpha.0

package/src/migrations/install-claude-update-skills/install-claude-update-skills.migration.js

@@ -1,290 +0,0 @@
-"use strict";
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __export = (target, all) => {
-  for (var name in all)
-    __defProp(target, name, { get: all[name], enumerable: true });
-};
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-var install_claude_update_skills_migration_exports = {};
-__export(install_claude_update_skills_migration_exports, {
-  default: () => installClaudeUpdateSkills
-});
-module.exports = __toCommonJS(install_claude_update_skills_migration_exports);
-var import_devkit = require("@nx/devkit");
-const BOTONIC_BOT_UPDATE_SKILL = `---
-name: botonic-bot-update
-description: >
-  Update a single Botonic bot app to the current workspace version \u2014 applies pending bot-app
-  generators and bumps @botonic/* dependencies. Use when user says "update bot",
-  "apply bot migrations", or "update <bot-name>". Run /botonic-update first to upgrade the
-  workspace itself.
----
-
-# Update Botonic Bot
-
-## Workflow: Update Bot App to Current Workspace Version
-
-### Step 0: Detect Package Manager
-
-Check which package manager the workspace uses:
-
-- If \`pnpm-lock.yaml\` exists \u2192 use \`pnpm\`
-- Else \u2192 use \`npm\`
-
-Use the detected package manager for all subsequent commands.
-
-### Step 1: Get Target Version
-
-Read \`node_modules/@botonic/nx-plugin/package.json\` \u2192 \`.version\` field.
-This is the version the workspace was updated to and the target for this bot.
-
-If the file does not exist, tell user: "Could not find @botonic/nx-plugin in node_modules. Run /botonic-update first to install the latest version."
-
-### Step 2: Discover Bots
-
-Run \`bash .claude/scripts/update-bot/discover-bots.sh\` from the workspace root.
-Expected output: JSON list of bots with name, path, current \`@botonic/core\` version.
-
-### Step 3: Ask Which Bot
-
-Present the bot list to the user. Ask which SINGLE bot to update.
-**CRITICAL**: Never accept more than one bot. If user asks for multiple, explain why and ask them to pick one.
-
-### Step 4: Check Bot's Current State
-
-Read the selected bot's \`package.json\` (at \`<bot-path>/package.json\`):
-- Extract the current \`@botonic/core\` version (strip \`^\` / \`~\` prefixes for comparison).
-
-Read \`.botonic/pending-bot-migrations.json\` if it exists:
-- Filter entries where \`appliedTo\` does NOT include \`<bot-name>\`.
-
-Determine:
-- \`hasVersionGap\`: bot's \`@botonic/core\` version \u2260 target version
-- \`hasPendingMigrations\`: any filtered pending migration entries exist
-
-If **neither** is true, report: "\`<bot-name>\` is already at v\`<target>\` with no pending migrations. All up to date." and stop.
-
-### Step 5: Ask Target Version (only when pending migrations exist)
-
-If \`hasPendingMigrations\`:
-- Show distinct \`version\` values from the pending migrations (sorted ascending).
-- Ask the user: "Which version would you like to update to?" (default: latest in list).
-- Only apply migrations whose \`version\` \u2264 chosen target version.
-
-If there are **no** pending migrations (version gap only), skip this step \u2014 use the target version from Step 1.
-
-### Step 6: Check Git State
-
-Run \`git status --porcelain\`. If output is non-empty, STOP.
-Tell user: "Please commit or stash changes before updating."
-
-### Step 7: Create Branch
-
-\`git checkout -b update/<bot-name>-to-v<target>\`
-
-### Step 8: Apply Pending Migrations (if any)
-
-For each pending migration (in version order, filtered to \`version\` \u2264 target):
-
-1. Run: \`<package-manager> nx g <generator> --project=<bot-name>\`
-2. If \`migrationGuide\` path exists, READ it. Follow verification checklist and manual steps.
-3. \`git add -A && git commit -m "chore(<bot-name>): apply <generator-name>"\`
-4. Mark bot as applied: update \`.botonic/pending-bot-migrations.json\` \u2014 add \`<bot-name>\` to the \`appliedTo\` array for this entry.
-5. \`git add .botonic/pending-bot-migrations.json && git commit --amend --no-edit\`
-
-### Step 9: Bump @botonic/* Versions
-
-Check if the bot's \`@botonic/core\` version (after any migrations) still differs from the target version.
-
-If it does, edit \`<bot-path>/package.json\`:
-- Update **all** \`@botonic/*\` entries in \`dependencies\`, \`devDependencies\`, and \`peerDependencies\` to the exact target version (no \`^\` or \`~\`).
-
-\`git add <bot-path>/package.json && git commit -m "chore(<bot-name>): bump @botonic/* to v<target>"\`
-
-Skip this step only if the versions already match.
-
-### Step 10: Final Verification
-
-- \`nx build <bot-name>\`
-- Report: list all commits made, any remaining manual steps from migration guides
-- Suggest: \`nx serve-bot <bot-name>\` for manual testing
-
-## Examples
-
-### Example 1: Bot with pending migrations and a version gap
-
-User says: "Update my-bot" (currently on v2.17.0, workspace on v2.19.0, 2 pending migrations)
-
-1. Target version: 2.19.0 (from node_modules)
-2. discover-bots.sh \u2192 my-bot on v2.17.0
-3. Check state: hasVersionGap=true, hasPendingMigrations=true (v2.18.0, v2.19.0)
-4. Ask target: "Available versions: 2.18.0, 2.19.0. Update to which? [default: 2.19.0]"
-5. Branch: update/my-bot-to-v2.19.0
-6. Apply v2.18.0 generator \u2192 commit \u2192 mark applied
-7. Apply v2.19.0 generator \u2192 commit \u2192 mark applied
-8. Bump @botonic/* to 2.19.0 in package.json \u2192 commit
-9. Report: "Done. 2 generators applied + version bumped to v2.19.0."
-
-### Example 2: New version with no bot-app migrations (version gap only)
-
-User says: "Update my-bot" (currently on v2.17.0, workspace on v2.18.0, no pending migrations)
-
-1. Target version: 2.18.0 (from node_modules)
-2. discover-bots.sh \u2192 my-bot on v2.17.0
-3. Check state: hasVersionGap=true, hasPendingMigrations=false
-4. No version selection prompt needed
-5. Branch: update/my-bot-to-v2.18.0
-6. Skip Step 8 (no migrations)
-7. Bump @botonic/* to 2.18.0 in package.json \u2192 commit
-8. Report: "Done. No migrations needed \u2014 @botonic/* bumped to v2.18.0."
-
-### Example 3: Bot already up to date
-
-User says: "Update customer-bot" (on v2.19.0, workspace on v2.19.0, no pending migrations)
-
-1. Target version: 2.19.0
-2. Check state: hasVersionGap=false, hasPendingMigrations=false
-3. Report: "customer-bot is already at v2.19.0 with no pending migrations. All up to date."
-
-### Example 4: Multiple bots requested (refuse)
-
-User says: "Update all bots"
-Response: "I update one bot at a time to ensure each migration is properly verified. Which bot would you like to start with? [list bots]"
-
-## Troubleshooting
-
-### Error: Generator reports "already up to date"
-
-Cause: The bot code was already manually updated before running the generator.
-Solution: The generator is idempotent and skipped correctly. Mark it as applied and continue to the version bump step.
-
-### Error: Build fails after generator
-
-Cause: Custom bot code uses removed/changed APIs.
-Solution:
-
-1. Read the migration guide "What it cannot handle" section
-2. Follow "Manual migration steps" for custom patterns
-3. Check TypeScript: \`npx tsc --noEmit\`
-`;
-const BOTONIC_UPDATE_SKILL = `---
-name: botonic-update
-description: >
-  Update the Botonic workspace to the latest version by running nx migrate. Use when user says
-  "update botonic", "upgrade botonic", "update workspace", or wants to update @botonic/nx-plugin
-  to the latest version. If pending bot migrations are queued afterward, instruct user to run
-  /botonic-bot-update per bot.
----
-
-# Update Botonic Workspace
-
-## Workflow: Update Botonic to Latest Version
-
-### Step 0: Detect Package Manager
-
-Check which package manager the workspace uses:
-
-- If \`pnpm-lock.yaml\` exists \u2192 use \`pnpm\`
-- Else \u2192 use \`npm\`
-
-Use the detected package manager for all subsequent commands.
-
-### Step 1: Check Current State
-
-Run \`npm view @botonic/nx-plugin version\` to get the latest available version.
-Check \`node_modules/@botonic/nx-plugin/package.json\` for the currently installed version.
-
-If already on latest, report "already up to date" and stop.
-
-### Step 2: Check Git State
-
-Run \`git status --porcelain\`. If output is non-empty, STOP.
-Tell user: "Please commit or stash changes before updating."
-
-### Step 3: Run Nx Migrate
-
-\`\`\`
-npx nx migrate @botonic/nx-plugin@latest
-\`\`\`
-
-This updates \`package.json\` and creates \`migrations.json\`.
-
-If output says "no migrations to run" and \`package.json\` was already at the latest version, stop and report "already up to date".
-
-### Step 4: Install Dependencies
-
-\`\`\`
-<package-manager> install
-\`\`\`
-
-### Step 5: Run Workspace Migrations
-
-\`\`\`
-<package-manager> nx migrate --run-migrations
-\`\`\`
-
-This runs any workspace-level migrations shipped by the target \`@botonic/nx-plugin\` version.
-
-If that version also queues bot-app generators, it may write \`.botonic/pending-bot-migrations.json\` for \`/botonic-bot-update\`.
-
-### Step 6: Commit
-
-\`\`\`
-git add -A && git commit -m "chore: update @botonic/nx-plugin to v<version>"
-\`\`\`
-
-### Step 7: Report
-
-Report:
-
-- New version installed
-- Any workspace changes applied
-- Whether \`.botonic/pending-bot-migrations.json\` was created and how many generators are pending
-- If generators are pending, instruct user to run \`/botonic-bot-update\` to apply them per bot
-`;
-const OLD_FILES = [
-  ".cursor/commands/update-bot.md",
-  ".cursor/commands/update-botonic.md",
-  ".claude/commands/update-bot.md",
-  ".claude/commands/update-botonic.md"
-];
-async function installClaudeUpdateSkills(tree) {
-  let removedCount = 0;
-  for (const filePath of OLD_FILES) {
-    if (tree.exists(filePath)) {
-      tree.delete(filePath);
-      removedCount++;
-    }
-  }
-  tree.write(
-    ".claude/skills/botonic-bot-update/SKILL.md",
-    BOTONIC_BOT_UPDATE_SKILL
-  );
-  tree.write(".claude/skills/botonic-update/SKILL.md", BOTONIC_UPDATE_SKILL);
-  await (0, import_devkit.formatFiles)(tree);
-  if (removedCount > 0) {
-    import_devkit.logger.info(
-      `  \u2705 Removed ${removedCount} old command stub(s) (.cursor/commands/, .claude/commands/)`
-    );
-  }
-  import_devkit.logger.info(
-    `  \u2705 Installed .claude/skills/botonic-bot-update/SKILL.md (was /update-bot)`
-  );
-  import_devkit.logger.info(
-    `  \u2705 Installed .claude/skills/botonic-update/SKILL.md (was /update-botonic)`
-  );
-  import_devkit.logger.info(
-    `  \u2139\uFE0F  Use /botonic-bot-update to apply pending bot migrations and /botonic-update to upgrade the workspace`
-  );
-}