Fix skill spec compliance and add automation scripts

Review all 7 RHDH skills against the Agent Skills open standard and fix
all flagged issues.

Metadata and reference fixes:
- Fix all frontmatter name fields to lowercase-hyphens
- Rewrite descriptions to third person per spec
- Fix broken reference paths across overlay workflows
- Normalize CLI naming in workflow files
- Add missing reference_index entries in rhdh skill
- Fix stale hardcoded version tags in env-reference.md
- Add missing gotchas to create-frontend-plugin and generate-frontend-wiring

New automation scripts (stdlib-only Python per ADR-0002):
- rhdh-local: fetch-plugin-metadata.py
- create-backend-plugin: scaffold.py
- create-frontend-plugin: scaffold.py
- overlay: analyze-pr.py, triage-prs.py
- export-and-package: export-plugin.py

Bug fixes:
- Fix Windows path separator inconsistency in sync.py
- Skip Unix permission check on Windows in test suite

Author: schultzp2020

skills/create-backend-plugin/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: RHDH Backend Dynamic Plugin Bootstrap
-description: This skill should be used when the user asks to "create RHDH backend plugin", "bootstrap backend dynamic plugin", "create backstage backend plugin for RHDH", "new backend plugin for Red Hat Developer Hub", "create dynamic backend plugin", "scaffold RHDH backend plugin", "new scaffolder action", "create catalog processor", or mentions creating a new backend plugin, backend module, or server-side functionality for Red Hat Developer Hub or RHDH. This skill is specifically for backend plugins - for frontend plugins, use the separate frontend plugin skill.
+name: create-backend-plugin
+description: Bootstraps a new backend dynamic plugin for Red Hat Developer Hub (RHDH). Use when the user asks to "create RHDH backend plugin", "bootstrap backend dynamic plugin", "create backstage backend plugin for RHDH", "new backend plugin for Red Hat Developer Hub", "create dynamic backend plugin", "scaffold RHDH backend plugin", "new scaffolder action", "create catalog processor", or mentions creating a new backend plugin, backend module, or server-side functionality for Red Hat Developer Hub or RHDH. This skill is specifically for backend plugins - for frontend plugins, use the separate frontend plugin skill.
 ---
 
 ## Purpose
 
-Bootstrap a new **backend** dynamic plugin for Red Hat Developer Hub (RHDH). RHDH is the enterprise-ready Backstage applicationthat supports dynamic plugins - plugins that can be installed or uninstalled without rebuilding the application.
+Bootstrap a new **backend** dynamic plugin for Red Hat Developer Hub (RHDH). RHDH is the enterprise-ready Backstage application that supports dynamic plugins - plugins that can be installed or uninstalled without rebuilding the application.
 
 > **Note:** This skill covers **backend plugins only**. Frontend dynamic plugins have different requirements (Scalprum configuration, mount points, dynamic routes) and are covered in a separate skill.
 
@@ -49,36 +49,40 @@ Check the target RHDH version and find the compatible Backstage version. Consult
 
 Ask the user which RHDH version they are targeting if not specified.
 
-## Step 2: Create Backstage Application
+## Steps 2-3: Create Backstage Application & Backend Plugin
 
-Create a new Backstage application in the current directory using the version-appropriate create-app:
+Use the scaffold script to automate app creation, dependency installation, and plugin generation in one command:
 
 ```bash
-# For RHDH 1.8 (adjust version as needed)
-echo "backstage" | npx @backstage/create-app@0.7.3 --path .
+python skills/create-backend-plugin/scripts/scaffold.py \
+  --rhdh-version 1.9 \
+  --plugin-id my-plugin \
+  --path ./my-app
 ```
 
-After creation, install dependencies:
-
-```bash
-yarn install
-```
+The script:
+- Looks up the correct `@backstage/create-app` version for the target RHDH release
+- Creates the Backstage app (idempotent — skips if `package.json` already exists)
+- Runs `yarn install`
+- Generates the backend plugin via `yarn new --select backend-plugin --option id=<plugin-id>`
 
- The only purpose this serves is to ensure you can later create the plugin using the correct version of the Backstage CLI. All development and testing will be done in the plugin directory.
+Use `--json` for structured output, or `--create-app-version` to override the auto-detected version. Run with `--help` for all options.
 
-## Step 3: Create Backend Plugin
+### Manual alternative
 
-Generate a new backend plugin using the Backstage CLI:
+If you prefer to run the commands manually:
 
 ```bash
-yarn new
-```
+# Step 2: Create Backstage app
+# Consult ../rhdh/references/versions.md for the correct create-app version
+echo "backstage" | npx @backstage/create-app@0.7.3 --path .
+yarn install
 
-When prompted:
+# Step 3: Create backend plugin
+yarn new --select backend-plugin --option id=my-plugin
+```
 
-1. Select **"backend-plugin"** as the plugin type
-2. Enter a plugin ID (e.g., `my-plugin`)
-3. The plugin will be created at `plugins/<plugin-id>-backend/`
+The only purpose of the Backstage app is to ensure you can create the plugin using the correct version of the Backstage CLI. All development and testing will be done in the plugin directory.
 
 The generated plugin structure:
 
@@ -191,6 +195,8 @@ For local development/testing, copy `dist-dynamic` to RHDH's `dynamic-plugins-ro
 cp -r dist-dynamic /path/to/rhdh/dynamic-plugins-root/<plugin-id>-backend-dynamic
 ```
 
+> **Windows note:** Use `xcopy /E /I dist-dynamic \path\to\rhdh\dynamic-plugins-root\<plugin-id>-backend-dynamic` or `robocopy dist-dynamic \path\to\rhdh\dynamic-plugins-root\<plugin-id>-backend-dynamic /E` instead of `cp -r`.
+
 See `examples/dynamic-plugins.yaml` for a complete configuration example.
 
 ## Common Issues