Further improve robustness of version parsing and error messages

- Use substring() instead of split() to handle edge cases in version parsing
- Replace Node.js inline require with grep for better portability in CI
- Add validation for empty version strings

Co-authored-by: longsizhuo <114939201+longsizhuo@users.noreply.github.com>

Author: Copilot

.github/workflows/content-check.yml

@@ -56,7 +56,7 @@ jobs:
             echo "This indicates a pnpm version mismatch or corrupted lockfile"
             echo ""
             echo "Expected pnpm version from package.json:"
-            node -p "require('./package.json').packageManager || 'not specified'" || echo "Could not read package.json"
+            grep -o 'pnpm@[^"]*' package.json | head -1 || echo "Could not extract version"
             echo ""
             echo "Actual pnpm version:"
             pnpm --version || echo "pnpm not found"

.github/workflows/deploy.yml

@@ -45,7 +45,7 @@ jobs:
             echo "This indicates a pnpm version mismatch or corrupted lockfile"
             echo ""
             echo "Expected pnpm version from package.json:"
-            node -p "require('./package.json').packageManager || 'not specified'" || echo "Could not read package.json"
+            grep -o 'pnpm@[^"]*' package.json | head -1 || echo "Could not extract version"
             echo ""
             echo "Actual pnpm version:"
             pnpm --version || echo "pnpm not found"

scripts/check-pnpm-version.mjs

@@ -30,10 +30,12 @@ try {
     process.exit(1);
   }
 
-  const expectedVersion = packageManager.split('@')[1];
+  // Extract version: "pnpm@10.20.0" -> "10.20.0"
+  const expectedVersion = packageManager.substring(packageManager.indexOf('@') + 1);
 
-  if (!expectedVersion) {
+  if (!expectedVersion || expectedVersion.trim() === '') {
     console.error('❌ Error: Could not parse pnpm version from packageManager field');
+    console.error(`   packageManager value: ${packageManager}`);
     process.exit(1);
   }