refactor(power-pages): rename migrate-sdm-to-edm skill to migrate-datamodel + report/telemetry updates

Rename skill 'migrate-sdm-to-edm' -> 'migrate-datamodel' across the folder, SKILL.md frontmatter name, all script path references, telemetry SKILL_NAME, the live-report footer, and the skill-tracking table (MigrateDatamodel). Descriptive SDM->EDM report filenames/content are intentionally left unchanged.

Add skill_completed 1DS telemetry via new scripts/emit-telemetry.js (Option A): builds a per-phase rollup from migration-state.json into eventInfo, fails closed, and honors the plugin kill switch. Wired into the final phase of SKILL.md.

Remove the Power Pages VS Code extension dependency from the remediation diff: drop the PP-VSCode import button/guide, importer-only JSON fields, and base64 file contents; slim remediation-diff.json to a skill-owned manifest with absolute livePath/stagedPath; add per-file 'Copy diff command' buttons that copy 'code --diff' (single-quoted absolute paths, works in any terminal/shell, no extension) plus a clipboard script with a file:// fallback.

Convert the Overview boilerplate into grouped bullet points and drop the stale hardcoded sub-step counts (live counts remain in the stats grid and Plan section).

Add an 'AI-generated content may be incorrect' disclaimer to the live report and the customization/migration report footers.

Rename the foundation package reference PowerPagesCore -> PowerPages_Core (6 references).

Author: sparrow1303

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

@@ -42,7 +42,7 @@ If the tracking script creates or updates site setting YAML files, include those
 | add-cloud-flow | AddCloudFlow | Site/AI/Skills/AddCloudFlow |
 | add-ai-webapi | AddAiWebapi | Site/AI/Skills/AddAiWebapi |
 | integrate-backend | IntegrateBackend | Site/AI/Skills/IntegrateBackend |
-| migrate-sdm-to-edm | MigrateSdmToEdm | Site/AI/Skills/MigrateSdmToEdm |
+| migrate-datamodel | MigrateDatamodel | Site/AI/Skills/MigrateDatamodel |
 | scan-site | ScanSite | Site/AI/Skills/ScanSite |
 | manage-headers | ManageHeaders | Site/AI/Skills/ManageHeaders |
 | manage-firewall | ManageFirewall | Site/AI/Skills/ManageFirewall |

…-sdm-to-edm/BugBash-MigrateSdmToEdm.docx …e-datamodel/BugBash-MigrateSdmToEdm.docxplugins/power-pages/skills/migrate-sdm-to-edm/BugBash-MigrateSdmToEdm.docx renamed to plugins/power-pages/skills/migrate-datamodel/BugBash-MigrateSdmToEdm.docx plugins/power-pages/skills/migrate-sdm-to-edm/BugBash-MigrateSdmToEdm.docx renamed to plugins/power-pages/skills/migrate-datamodel/BugBash-MigrateSdmToEdm.docx

@@ -1,11 +1,11 @@
 # HTML Reports Integration Guide
 
-This document explains how to integrate the HTML report templates and generation scripts into the `migrate-sdm-to-edm` skill workflow.
+This document explains how to integrate the HTML report templates and generation scripts into the `migrate-datamodel` skill workflow.
 
 ## Folder Structure
 
 ```
-plugins/power-pages/skills/migrate-sdm-to-edm/
+plugins/power-pages/skills/migrate-datamodel/
 ├── assets/
 │   ├── customization-report.html      # Template for customization report
 │   ├── sdm-to-edm-migration-report.html    # Template for execution report
@@ -37,7 +37,7 @@ pac pages migrate-datamodel --webSiteId "<WEBSITE_ID>" --siteCustomizationReport
 # ... parsing logic ...
 
 # Phase 8 step 3: Generate HTML report
-node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration-reports.js" \
+node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/generate-migration-reports.js" \
   --customization-report "./migration-report/SiteCustomization.csv" \
   --site-name "<SITE_NAME>" \
   --website-id "<WEBSITE_ID>" \
@@ -53,7 +53,7 @@ echo "Customization report: file://$(pwd)/migration-reports/customization-report
 For automatable fixes (Data Model Extensions only), the same script is invoked with `--automate` and `--env-url`:
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration-reports.js" \
+node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/generate-migration-reports.js" \
   --site-name "<SITE_NAME>" \
   --website-id "<WEBSITE_ID>" \
   --siteCustomizationReportPath "./migration-report/SiteCustomization.csv" \
@@ -81,7 +81,7 @@ The script creates missing string attributes via Dataverse Web API and logs resu
 # Track all commands, results, and timing
 
 # At end of Phase 12: generate execution report
-node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration-reports.js" \
+node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/generate-migration-reports.js" \
   --site-name "<SITE_NAME>" \
   --website-id "<WEBSITE_ID>" \
   --portal-id "<PORTAL_ID>" \
@@ -183,7 +183,7 @@ During skill execution, collect:
 The skill calls the script after parsing the CSV from PAC CLI:
 
 ```powershell
-node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration-reports.js" `
+node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/generate-migration-reports.js" `
   --customization-report "<REPORT_PATH>" `
   --site-name "<SITE_NAME>" `
   --website-id "<WEBSITE_ID>" `
@@ -198,7 +198,7 @@ Open the generated HTML report in your browser: `file://<OUTPUT_DIR>/customizati
 The same script runs with `--automate` to apply safe fixes via Dataverse API (Data Model Extensions only):
 
 ```powershell
-node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration-reports.js" `
+node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/generate-migration-reports.js" `
   --site-name "<SITE_NAME>" `
   --website-id "<WEBSITE_ID>" `
   --siteCustomizationReportPath "<REPORT_PATH>" `
@@ -213,7 +213,7 @@ node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration
 At the end of post-migration validation:
 
 ```powershell
-node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-sdm-to-edm/scripts/generate-migration-reports.js" `
+node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/generate-migration-reports.js" `
   --site-name "<SITE_NAME>" `
   --website-id "<WEBSITE_ID>" `
   --portal-id "<PORTAL_ID>" `

…ages/skills/migrate-sdm-to-edm/DESIGN.md …pages/skills/migrate-datamodel/DESIGN.mdplugins/power-pages/skills/migrate-sdm-to-edm/DESIGN.md renamed to plugins/power-pages/skills/migrate-datamodel/DESIGN.md plugins/power-pages/skills/migrate-sdm-to-edm/DESIGN.md renamed to plugins/power-pages/skills/migrate-datamodel/DESIGN.md

@@ -146,6 +146,7 @@ <h1>Site Customization Report</h1>
 
     <div class="footer">
       <p>Generated by Power Pages Migration Tool · Report created on {{REPORT_DATE}}</p>
+      <p>AI-generated content may be incorrect</p>
     </div>
   </div>
 </body>

…-edm/Migrate SDM to EDM [Design doc].pdf …odel/Migrate SDM to EDM [Design doc].pdfplugins/power-pages/skills/migrate-sdm-to-edm/Migrate SDM to EDM [Design doc].pdf renamed to plugins/power-pages/skills/migrate-datamodel/Migrate SDM to EDM [Design doc].pdf plugins/power-pages/skills/migrate-sdm-to-edm/Migrate SDM to EDM [Design doc].pdf renamed to plugins/power-pages/skills/migrate-datamodel/Migrate SDM to EDM [Design doc].pdf

@@ -610,6 +610,7 @@ <h2>
 
     <div class="footer">
       <p>Generated by Power Pages Migration Tool | Report created on {{REPORT_DATE}}</p>
+      <p>AI-generated content may be incorrect</p>
     </div>
   </div>
 </body>