power-pages: rename bootstrap-migrate-v3-to-v5 skill to migrate-bootstrap

Renames the skill directory, eval directory, SKILL.md name, all five
approval-gate ids, the approval-gates catalog section, the skill-tracking
entry (MigrateBootstrap / Site/AI/Skills/MigrateBootstrap), the README
entry, and the reference-doc mentions.

The pac pages bootstrap-migrate CLI verb is unrelated and left untouched.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: c10b282d-bbe9-4fab-ad9f-4bf333ad953b

Author: Tanvi Dahiya

…es/bootstrap-migrate-v3-to-v5/evals.json …power-pages/migrate-bootstrap/evals.jsonevals/power-pages/bootstrap-migrate-v3-to-v5/evals.json renamed to evals/power-pages/migrate-bootstrap/evals.json evals/power-pages/bootstrap-migrate-v3-to-v5/evals.json renamed to evals/power-pages/migrate-bootstrap/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "bootstrap-migrate-v3-to-v5",
+  "skill_name": "migrate-bootstrap",
   "evals": [
     {
       "id": 1,
@@ -21,7 +21,7 @@
         "A final consent gate is presented before the outward-facing upload",
         "pac pages upload (not upload-code-site) is run against the <folder>V5 directory",
         "The Bootstrap 5 runtime flag flip is explicitly verified after upload rather than trusting the upload exit code",
-        "The site is validated via /test-site and skill usage is recorded with --skillName BootstrapMigrateV3ToV5"
+        "The site is validated via /test-site and skill usage is recorded with --skillName MigrateBootstrap"
       ]
     },
     {

plugins/power-pages/README.md

@@ -390,7 +390,7 @@ Adds search engine optimization artifacts: `robots.txt`, `sitemap.xml`, and meta
 
 ### Migration
 
-#### `/bootstrap-migrate-v3-to-v5`
+#### `/migrate-bootstrap`
 
 > "Upgrade my Power Pages site from Bootstrap 3 to Bootstrap 5"
 

plugins/power-pages/references/approval-gates.md

@@ -685,17 +685,17 @@ New skill (Power Pages source & dependency security scan). Runs local static ana
 
 ---
 
-### 6.31 `bootstrap-migrate-v3-to-v5` (6 calls / 5 gates + 1 sub-prompt)
+### 6.31 `migrate-bootstrap` (6 calls / 5 gates + 1 sub-prompt)
 
 New skill (migrates a traditional Power Pages site from Bootstrap 3 to Bootstrap 5). The engine does the bulk class renames; the skill assists with residual hierarchy/CSS fixes, then uploads (which auto-flips the runtime flag).
 
 | ID | Kind | Category | Phase | Trigger / question | Cancel leaves |
 |---|---|---|---|---|---|
-| `bootstrap-migrate-v3-to-v5:1.confirm-env` | gate | consent | 1 | Echoes current env — *"Use this environment / choose another"*. Migrating against the wrong environment is destructive, so confirmation is mandatory. Covers the free-text env-URL sub-prompt in the same step. | nothing |
-| `bootstrap-migrate-v3-to-v5:2.1.select-site` | gate | plan | 2.1 | Multiple websites found — *"Which website to download?"* | nothing |
-| `bootstrap-migrate-v3-to-v5:4.run-engine` | gate | consent | 4 | *"Run the Bootstrap 5 migration on `<SITE_FOLDER>`?"* — engine writes a new `<SITE_FOLDER>V5` copy and never edits the source. | nothing |
-| `bootstrap-migrate-v3-to-v5:6.residual-fixes` | gate | progress | 6 | Per-category consent — *"Apply the `<category>` fixes to `<N>` file(s)?"* — repeated per residual category; changes are local to the V5 copy. | nothing |
-| `bootstrap-migrate-v3-to-v5:7.2.upload` | gate | final | 7.2 | First outward-facing change — *"Upload `<MIGRATED_FOLDER>` to `<ENV_NAME>`?"* — publishes the Bootstrap 5 site and auto-enables the runtime flag. | nothing |
+| `migrate-bootstrap:1.confirm-env` | gate | consent | 1 | Echoes current env — *"Use this environment / choose another"*. Migrating against the wrong environment is destructive, so confirmation is mandatory. Covers the free-text env-URL sub-prompt in the same step. | nothing |
+| `migrate-bootstrap:2.1.select-site` | gate | plan | 2.1 | Multiple websites found — *"Which website to download?"* | nothing |
+| `migrate-bootstrap:4.run-engine` | gate | consent | 4 | *"Run the Bootstrap 5 migration on `<SITE_FOLDER>`?"* — engine writes a new `<SITE_FOLDER>V5` copy and never edits the source. | nothing |
+| `migrate-bootstrap:6.residual-fixes` | gate | progress | 6 | Per-category consent — *"Apply the `<category>` fixes to `<N>` file(s)?"* — repeated per residual category; changes are local to the V5 copy. | nothing |
+| `migrate-bootstrap:7.2.upload` | gate | final | 7.2 | First outward-facing change — *"Upload `<MIGRATED_FOLDER>` to `<ENV_NAME>`?"* — publishes the Bootstrap 5 site and auto-enables the runtime flag. | nothing |
 
 ---
 ### Cross-plugin shared skills — out of catalog scope

plugins/power-pages/references/skill-tracking-reference.md

@@ -56,7 +56,7 @@ If the tracking script creates or updates site setting YAML files, include those
 | deploy-pipeline | DeployPipeline | Site/AI/Skills/DeployPipeline |
 | ensure-pipelines-host | EnsurePipelinesHost | Site/AI/Skills/EnsurePipelinesHost |
 | force-link-environment | ForceLinkEnvironment | Site/AI/Skills/ForceLinkEnvironment |
-| bootstrap-migrate-v3-to-v5 | BootstrapMigrateV3ToV5 | Site/AI/Skills/BootstrapMigrateV3ToV5 |
+| migrate-bootstrap | MigrateBootstrap | Site/AI/Skills/MigrateBootstrap |
 
 ## YAML Format
 

…ills/bootstrap-migrate-v3-to-v5/SKILL.md …-pages/skills/migrate-bootstrap/SKILL.mdplugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md renamed to plugins/power-pages/skills/migrate-bootstrap/SKILL.md plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md renamed to plugins/power-pages/skills/migrate-bootstrap/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: bootstrap-migrate-v3-to-v5
+name: migrate-bootstrap
 description: >-
   Migrates a traditional Power Pages site from Bootstrap 3 to Bootstrap 5. Downloads the
   site, runs the pac pages bootstrap-migrate engine, reviews the change report, applies
@@ -65,9 +65,9 @@ confirmed, and the required commands are available.
    then `pac auth create --environment "<URL>"` and re-verify. Capture the environment name, URL,
    and ID.
 
-<!-- gate: bootstrap-migrate-v3-to-v5:1.confirm-env | category=consent | cancel-leaves=nothing -->
+<!-- gate: migrate-bootstrap:1.confirm-env | category=consent | cancel-leaves=nothing -->
 
-> 🚦 **Gate (consent · bootstrap-migrate-v3-to-v5:1.confirm-env):** Confirm the target environment before any download, migration, or upload. Running the migration against the wrong environment is destructive, so this confirmation is mandatory.
+> 🚦 **Gate (consent · migrate-bootstrap:1.confirm-env):** Confirm the target environment before any download, migration, or upload. Running the migration against the wrong environment is destructive, so this confirmation is mandatory.
 
 4. Confirm the target environment with the user (`AskUserQuestion`: use this environment / choose
    another via `pac org list` + `pac org select`).
@@ -114,9 +114,9 @@ and `upload` confirmed available, `PAC_LOG` path captured.
   pac pages list
   ```
 
-<!-- gate: bootstrap-migrate-v3-to-v5:2.1.select-site | category=plan | cancel-leaves=nothing -->
+<!-- gate: migrate-bootstrap:2.1.select-site | category=plan | cancel-leaves=nothing -->
 
-  > 🚦 **Gate (plan · bootstrap-migrate-v3-to-v5:2.1.select-site):** Choose which website to download when more than one exists. Canceling leaves nothing changed.
+  > 🚦 **Gate (plan · migrate-bootstrap:2.1.select-site):** Choose which website to download when more than one exists. Canceling leaves nothing changed.
 
   Present the websites via `AskUserQuestion`, then download the selected site:
 
@@ -214,9 +214,9 @@ running the engine.
 
 **Actions**:
 
-<!-- gate: bootstrap-migrate-v3-to-v5:4.run-engine | category=consent | cancel-leaves=nothing -->
+<!-- gate: migrate-bootstrap:4.run-engine | category=consent | cancel-leaves=nothing -->
 
-> 🚦 **Gate (consent · bootstrap-migrate-v3-to-v5:4.run-engine):** Explicit consent before running `pac pages bootstrap-migrate`. The engine writes a new `<SITE_FOLDER>V5` copy and never edits the source, so canceling leaves nothing changed.
+> 🚦 **Gate (consent · migrate-bootstrap:4.run-engine):** Explicit consent before running `pac pages bootstrap-migrate`. The engine writes a new `<SITE_FOLDER>V5` copy and never edits the source, so canceling leaves nothing changed.
 
 1. Get explicit consent to run the engine (`AskUserQuestion`: "Run the Bootstrap 5 migration on
    `<SITE_FOLDER>`? This creates a new `<SITE_FOLDER>V5` copy and does not modify the original.").
@@ -277,9 +277,9 @@ the `MIGRATED_FOLDER` files.
 
 1. Group the residual items by category (grid hierarchy, navbar structure, panel/card styling,
    page-header, pager, btn-block, Liquid edge cases, partial paths).
-<!-- gate: bootstrap-migrate-v3-to-v5:6.residual-fixes | category=progress | cancel-leaves=nothing -->
+<!-- gate: migrate-bootstrap:6.residual-fixes | category=progress | cancel-leaves=nothing -->
 
-> 🚦 **Gate (progress · bootstrap-migrate-v3-to-v5:6.residual-fixes):** Per-category consent before applying each residual fix to the `MIGRATED_FOLDER` files. Changes are local to the V5 copy and committed per category; canceling leaves nothing outward-facing changed.
+> 🚦 **Gate (progress · migrate-bootstrap:6.residual-fixes):** Per-category consent before applying each residual fix to the `MIGRATED_FOLDER` files. Changes are local to the V5 copy and committed per category; canceling leaves nothing outward-facing changed.
 
 2. For **each category**, get per-category consent (`AskUserQuestion`: "Apply the `<category>` fixes
    to `<N>` file(s)?"). On consent:
@@ -314,9 +314,9 @@ Verify both (`Grep`/`Read`). If either is missing, the flag flip silently no-ops
 
 ### 7.2 Final consent gate, then upload
 
-<!-- gate: bootstrap-migrate-v3-to-v5:7.2.upload | category=final | cancel-leaves=nothing -->
+<!-- gate: migrate-bootstrap:7.2.upload | category=final | cancel-leaves=nothing -->
 
-> 🚦 **Gate (final · bootstrap-migrate-v3-to-v5:7.2.upload):** Final sign-off before the first outward-facing change. `pac pages upload` publishes the Bootstrap 5 site and auto-enables the runtime flag. Canceling before upload leaves the live site untouched.
+> 🚦 **Gate (final · migrate-bootstrap:7.2.upload):** Final sign-off before the first outward-facing change. `pac pages upload` publishes the Bootstrap 5 site and auto-enables the runtime flag. Canceling before upload leaves the live site untouched.
 
 This is the first **outward-facing** change. Get explicit consent (`AskUserQuestion`: "Upload
 `<MIGRATED_FOLDER>` to environment `<ENV_NAME>`? This publishes the Bootstrap 5 site and enables the
@@ -377,7 +377,7 @@ restart.
    panels/cards, forms, pagination) for layout regressions introduced by the migration.
 3. **Record skill usage** — follow `${PLUGIN_ROOT}/references/skill-tracking-reference.md`, passing
    `--projectRoot "<MIGRATED_FOLDER>"` (the folder containing `powerpages.config.json`) and
-   `--skillName "BootstrapMigrateV3ToV5"`. Tracking only writes when the project is a **code site**
+   `--skillName "MigrateBootstrap"`. Tracking only writes when the project is a **code site**
    (`.powerpages-site/site-settings/` exists); for a traditional/native download the script exits
    silently as a no-op — that is expected, so call it unconditionally and don't treat the no-op as an
    error. If tracking files are written, include them in the final commit.

…/references/bootstrap-v5-manual-fixes.md …/references/bootstrap-v5-manual-fixes.mdplugins/power-pages/skills/bootstrap-migrate-v3-to-v5/references/bootstrap-v5-manual-fixes.md renamed to plugins/power-pages/skills/migrate-bootstrap/references/bootstrap-v5-manual-fixes.md plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/references/bootstrap-v5-manual-fixes.md renamed to plugins/power-pages/skills/migrate-bootstrap/references/bootstrap-v5-manual-fixes.md

@@ -3,7 +3,7 @@
 `pac pages bootstrap-migrate` auto-applies the well-known class renames but can only **flag**
 structural ("hierarchy") changes and changes that require new CSS. Those appear in `logs.txt`
 as `Need hierarchy change for …` lines or as "replaced with styles" notes. This reference is the
-recipe book the `/bootstrap-migrate-v3-to-v5` skill uses in **Phase 6** to apply (or flag) each one.
+recipe book the `/migrate-bootstrap` skill uses in **Phase 6** to apply (or flag) each one.
 
 **Apply with per-category consent. Never blindly rewrite Liquid-entangled markup — flag it instead.**
 After each edit, re-check the affected lines against the file's `<file>-diff.json` so you don't

…references/migration-engine-reference.md …references/migration-engine-reference.mdplugins/power-pages/skills/bootstrap-migrate-v3-to-v5/references/migration-engine-reference.md renamed to plugins/power-pages/skills/migrate-bootstrap/references/migration-engine-reference.md plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/references/migration-engine-reference.md renamed to plugins/power-pages/skills/migrate-bootstrap/references/migration-engine-reference.md

@@ -1,6 +1,6 @@
 # Migration Engine Reference — `pac pages bootstrap-migrate` and the auto flag-flip
 
-This reference documents the CLI engine the `/bootstrap-migrate-v3-to-v5` skill orchestrates: what
+This reference documents the CLI engine the `/migrate-bootstrap` skill orchestrates: what
 `pac pages bootstrap-migrate` does, what it produces, and how `pac pages upload`
 automatically flips the server-side Bootstrap 5 runtime flag.