Sync legacy JSON mirrors to power-pages v2.5.0 after merging #203

main #203 replaced the legacy .claude-plugin symlinks with committed JSON
mirror files and changed validate-legacy-compatibility.js to require each
mirror to JSON-deep-equal its source. This branch bumped the power-pages
sources (marketplace.json + .plugin/plugin.json) to 2.5.0 before #203 landed,
so merging main brought the mirrors back as regular files frozen at 2.4.0 —
failing validate-repository-metadata.

Update the two power-pages mirrors (.claude-plugin/marketplace.json entry +
plugins/power-pages/.claude-plugin/plugin.json) to 2.5.0 so they match their
sources. Only the version field drifted.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: tyaginidhi

.claude-plugin/marketplace.json

@@ -13,7 +13,7 @@
             "source": "./plugins/power-pages",
             "description": "Power Pages development and management plugin for Claude Code and GitHub Copilot",
             "category": "development",
-            "version": "2.4.0",
+            "version": "2.5.0",
             "license": "MIT",
             "tags": [
                 "power platform",

plugins/power-pages/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "power-pages",
-  "version": "2.4.0",
+  "version": "2.5.0",
   "description": "Create and deploy Power Pages sites using modern development approaches. Supports code sites (SPAs) with React, Angular, Vue, or Astro. Includes ALM orchestration (plan-alm) with a solution-splitting decision tree, per-solution pipelines, Azure Blob asset advisory, manifest schema v2 for multi-solution deployments, and force-link remediation for cross-host pipeline migrations.",
   "author": {
     "name": "Microsoft",