chore: update RPM lockfile

.cursor/commands/pr-review-prioritizer.md

@@ -0,0 +1,147 @@
+# PR Review Prioritizer LLM Prompt
+
+You are a PR prioritization assistant that helps determine which pull request should be reviewed next based on a systematic scoring framework.
+
+## Your Task
+
+1. **Fetch PR Data**: Use the GitHub CLI to gather information about open pull requests
+2. **Apply Scoring Framework**: Calculate priority scores using the PR Prioritization Framework
+3. **Recommend Next Review**: Output the highest-priority PR that needs review
+
+## Step 1: Gather PR Information
+
+Use the following GitHub CLI commands to collect PR data:
+
+```bash
+# Get basic PR information
+gh pr list --state open --json number,title,author,createdAt,updatedAt,additions,deletions,isDraft,labels,reviewRequests,,comments,reviews,mergeable,baseRefName --limit 30
+
+```
+
+## Step 2: Apply Scoring Framework
+
+For each PR, calculate scores based on these metrics:
+
+### Age Score (Weight: 25%)
+- Calculate days since `createdAt`
+- Score mapping:
+  - 0-1 days: 0-20 points
+  - 2-3 days: 20-50 points  
+  - 4-7 days: 50-80 points
+  - 8+ days: 80-100 points
+
+### Size Score (Weight: 20%)
+- Use `additions + deletions` for total lines changed
+- Score mapping (inverse relationship):
+  - 1-50 lines: 80-100 points
+  - 51-200 lines: 60-79 points
+  - 201-500 lines: 40-59 points
+  - 501-1000 lines: 20-39 points
+  - 1000+ lines: 0-19 points
+
+
+### Author Wait Time Score (Weight: 15%)
+- Calculate hours since `updatedAt` (last author activity)
+- Check if author has responded to recent reviews
+- Score mapping:
+  - 0-2 hours: 90-100 points
+  - 2-8 hours: 70-89 points
+  - 8-24 hours: 40-69 points
+  - 1-2 days: 20-39 points
+  - 2+ days: 0-19 points
+
+### Change Type Score (Weight: 10%)
+- Analyze labels and title for change type:
+  - **Critical** (100 points): "hotfix", "security", "incident"
+  - **High** (75 points): "bug", "blocking"
+  - **Medium** (50 points): "feature", "enhancement"
+  - **Low** (25 points): "refactor", "docs", "test"
+  - **Very Low** (10 points): "style", "typo"
+
+## Step 3: Calculate Final Score
+
+```
+Total Score = (Age × 0.25) + (Size × 0.20) + (Wait Time × 0.15) + (Change Type × 0.10)
+```
+
+## Step 4: Apply Special Rules
+
+### Hotfix Override
+- If labels contain "hotfix" or title contains "[HOTFIX]": Set score to 100
+
+### Draft PR Exclusion  
+- Skip PRs where `isDraft: true` unless specifically requested
+- Skip PRs where status is draft or WIP
+
+### Closed PR Exclusion
+- Exclude closed PRs from the list entirely
+
+### Conflicting PR Exclusion
+- Exclude PRs that need rebasing AND have conflicting changes (mergeable: "CONFLICTING")
+- These PRs cannot be reviewed until conflicts are resolved
+
+### Stale PR Handling
+- If age > 14 days: Flag for author ping, but still calculate score
+- Include stale label in status column when present
+
+## Step 5: Output Format
+
+Provide output in this format:
+
+```
+## 🎯 Next PR to Review
+
+**PR #123: Fix critical authentication bug**
+- **Priority**: 🔴 Critical (Score: 87.5)
+- **Author**: @username
+- **Age**: 3 days
+- **Size**: 45 lines
+- **Link**: https://github.com/owner/repo/pull/123
+
+### Score Breakdown:
+- Age Score: 50 × 0.25 = 12.5
+- Size Score: 85 × 0.20 = 17.0
+- Dependency Score: 75 × 0.30 = 22.5
+- Wait Time Score: 90 × 0.15 = 13.5
+- Change Type Score: 75 × 0.10 = 7.5
+- **Total**: 87.5
+
+### Why This PR:
+- Blocks 2 other PRs
+- Author recently responded to feedback
+- Bug fix affecting user authentication
+- Manageable size for quick review
+
+---
+
+## 📋 All PRs by Priority
+
+| PR | Title | Priority | Score | Age | Size | Author | Status |
+|----|-------|----------|-------|-----|------|--------|--------|
+| [#123](https://github.com/owner/repo/pull/123) | Fix auth bug | 🔴 Critical | 87.5 | 3d | 45 | @user1 | Ready for review |
+| [#124](https://github.com/owner/repo/pull/124) | Add new feature | 🟡 Medium | 45.2 | 1d | 200 | @user2 | Needs approval |
+| [#125](https://github.com/owner/repo/pull/125) | Update docs | 🟢 Low | 23.1 | 5d | 20 | @user3 | Needs rebase (Stale) |
+```
+
+### Special Rules for Status Column:
+- Include both status and staleness in the same column
+- For example: "Needs review", "Approved", "Changes requested", "Needs rebase"
+- When stale label is present, append "(Stale)" to the status
+- Exclude closed PRs from the list entirely
+- Exclude draft PRs (isDraft: true) unless specifically requested
+- Exclude PRs with conflicting changes that need rebasing
+
+### Excluded PRs Section:
+- Include a section listing excluded PRs with clickable links
+- Format: `- **[#123](https://github.com/owner/repo/pull/123)**: Title - Reason for exclusion`
+- Group exclusions by reason (Conflicting/Rebase Issues, Draft PRs, etc.)
+
+### PR Table Sorting:
+- Sort PRs by score in descending order (highest score first)
+- For PRs with the same score, sort by priority in descending order (Critical > High > Medium > Low)
+- This ensures the most important PRs appear at the top of the table
+
+## Notes
+
+- Use this as a guide, not absolute rule - context matters
+- Do not implement the framework, just provide the output in the format specified

.cursor/rules/add_extension_metadata.mdc

@@ -0,0 +1,235 @@
+---
+description: AI-guided workflow for adding dynamic plugin metadata to the RHDH Extensions Catalog
+globs: catalog-entities/marketplace/**,docs/dynamic-plugins/**
+alwaysApply: false
+---
+# RHDH Extensions Catalog - Plugin Metadata Workflow
+
+This cursor rule provides an automated workflow for adding dynamic plugin metadata to the RHDH Extensions Catalog.
+
+## Important Documentation
+
+**Primary Reference**: Read `catalog-entities/marketplace/README.md` for:
+- Detailed YAML structure and field explanations
+- Complete examples (3scale plugin)
+- RHDH-local testing setup
+- Troubleshooting guide
+
+This rule focuses on the **workflow automation** and **validation** aspects not covered in the README.
+
+## Prerequisites
+
+Before starting, ensure you have:
+
+1. **Successfully exported plugin** from [RHDH Plugin Export Overlays](https://github.com/redhat-developer/rhdh-plugin-export-overlays)
+   - OCI URL from build output (e.g., `oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/aws-ecs:pr_1426__0.6.0!aws-ecs`)
+   - Plugin version and integrity information
+
+2. **Required tools installed**:
+   ```bash
+   # Check if tools are installed
+   command -v yq &> /dev/null || echo "❌ Install yq (Go version): brew install yq (macOS) or snap install yq (Linux)"
+   command -v ajv &> /dev/null || echo "❌ Install ajv-cli: npm install -g ajv-cli"
+   command -v gh &> /dev/null || echo "❌ Install GitHub CLI: brew install gh (macOS)"
+   ```
+
+   **Important**: Ensure you have the **Go-based version of yq** (mikefarah/yq), not the Python version (kislyuk/yq).
+   Verify with: `yq --version` (should show "mikefarah/yq")
+
+## Interactive Information Gathering
+
+When adding a plugin, gather the following information:
+
+### Required Information
+1. **Plugin Identification**
+   - Plugin name (e.g., `aws-ecs`, `todo`)
+   - NPM package name (e.g., `@aws/amazon-ecs-plugin-for-backstage`)
+   - Namespace (e.g., `rhdh` for Red Hat maintained, `community` for community plugins)
+
+2. **Technical Details**
+   - OCI URL from overlay build
+   - Plugin version
+   - Backstage version compatibility
+   - Role: `frontend-plugin` or `backend-plugin`
+
+3. **User-Facing Information**
+   - Title and short description (2-3 lines for tile view)
+   - Long description (markdown, for expanded view)
+   - Category (one of: AI, Analytics, CI/CD, Cloud, Compliance, Cost, Developer Tools, Docs, Feature Flags, Kubernetes, Monitoring, Productivity, Reporting, Search, Security, Storage, Supply Chain, Testing)
+   - Tags (lowercase, kebab-case)
+   - Support level: `production`, `tech-preview`, or `dev-preview`
+
+4. **Links**
+   - Homepage/documentation URL
+   - Source code repository
+   - Bug tracker URL
+
+## Workflow Steps
+
+### Step 1: Create Feature Branch
+
+```bash
+# Ensure we're on latest main
+git fetch origin && git checkout main && git pull origin main
+
+# Create feature branch
+git checkout -b add-{plugin-name}-plugin-metadata
+```
+
+### Step 2: Tool Verification
+
+```bash
+# Verify required tools
+for tool in yq ajv gh; do
+  command -v $tool &> /dev/null && echo "✓ $tool installed" || echo "❌ $tool missing"
+done
+
+# Verify yq is the Go version
+yq --version | grep -q "mikefarah" && echo "✓ yq is Go version (mikefarah/yq)" || echo "❌ Wrong yq version - install mikefarah/yq"
+```
+
+### Step 3: Generate Package Metadata
+
+For plugins from the overlay repository, use the marketplace CLI:
+
+```bash
+# Generate package metadata from dynamic-plugins.default.yaml
+npx --yes @red-hat-developer-hub/marketplace-cli generate \
+  --namespace rhdh \
+  -p dynamic-plugins.default.yaml \
+  -o catalog-entities/marketplace/packages
+
+# For external plugins, create manually using examples in README
+```
+
+### Step 4: Create/Edit Plugin Metadata
+
+Create `catalog-entities/marketplace/plugins/{plugin-name}.yaml`:
+- Use `catalog-entities/marketplace/plugins/3scale.yaml` as a template
+- See README for complete field descriptions
+
+### Step 5: Update Index Files
+
+**Important**: Add entries in **alphabetical order**!
+
+Use the AI agent's editing capabilities to:
+1. Add `- ./{plugin-name}.yaml` to `catalog-entities/marketplace/packages/all.yaml` in alphabetical order
+2. Add `- ./{plugin-name}.yaml` to `catalog-entities/marketplace/plugins/all.yaml` in alphabetical order
+
+The AI agent will automatically determine the correct alphabetical position and insert the entries accordingly.
+
+### Step 6: Validate Files
+
+```bash
+# Navigate to marketplace directory
+cd catalog-entities/marketplace
+
+# Download schemas to temp directory (ajv doesn't support remote schemas well)
+mkdir -p /tmp/rhdh-schemas
+curl -s "https://raw.githubusercontent.com/redhat-developer/rhdh-plugins/main/workspaces/marketplace/json-schema/packages.json" \
+  -o /tmp/rhdh-schemas/packages.json
+curl -s "https://raw.githubusercontent.com/redhat-developer/rhdh-plugins/main/workspaces/marketplace/json-schema/plugins.json" \
+  -o /tmp/rhdh-schemas/plugins.json
+
+# Convert YAML to JSON and validate Package against local schema
+echo "Validating packages/{plugin-name}.yaml..."
+yq eval packages/{plugin-name}.yaml -o json > /tmp/rhdh-schemas/package-temp.json
+ajv validate -s /tmp/rhdh-schemas/packages.json -d /tmp/rhdh-schemas/package-temp.json
+
+# Convert YAML to JSON and validate Plugin against local schema
+echo "Validating plugins/{plugin-name}.yaml..."
+yq eval plugins/{plugin-name}.yaml -o json > /tmp/rhdh-schemas/plugin-temp.json
+ajv validate -s /tmp/rhdh-schemas/plugins.json -d /tmp/rhdh-schemas/plugin-temp.json
+
+# Clean up temp files
+rm /tmp/rhdh-schemas/package-temp.json /tmp/rhdh-schemas/plugin-temp.json
+```
+
+**Note**: This uses the Go-based `yq` syntax (`yq eval file.yaml -o json`). If validation fails, check that you have the correct yq version installed.
+
+### Step 7: Test Locally (Optional)
+
+Follow the RHDH-local testing instructions in the README:
+1. Clone `rhdh-local` repository
+2. Mount your local catalog in `compose.yaml`
+3. Set `catalog.processingInterval: { seconds: 15 }` in `app-config.yaml`
+4. Start with `docker compose up -d`
+5. Check http://localhost:7007 → Catalog → Extensions
+
+### Step 8: Create Pull Request
+
+```bash
+# Stage changes
+git add catalog-entities/marketplace/packages/{plugin-name}.yaml
+git add catalog-entities/marketplace/plugins/{plugin-name}.yaml
+git add catalog-entities/marketplace/packages/all.yaml
+git add catalog-entities/marketplace/plugins/all.yaml
+
+# Commit with descriptive message
+git commit -m "feat: add {plugin-name} plugin to RHDH marketplace
+
+- Added Package entity with OCI URL and version
+- Added Plugin entity with description and metadata
+- Updated all.yaml indexes in alphabetical order"
+
+# Create PR
+gh pr create --title "feat: add {plugin-name} plugin to marketplace" \
+  --body "## Summary
+- Added {plugin-name} plugin metadata to Extensions Catalog
+- Package: \`{npm-package-name}\` version {version}
+- Support level: {support-level}
+
+## Checklist
+- [ ] Package and Plugin YAML files created
+- [ ] Schemas validate successfully
+- [ ] Added to all.yaml files alphabetically
+- [ ] Tested locally with rhdh-local (if applicable)"
+```
+
+## Validation Checklist
+
+Before submitting:
+- [ ] Tools installed (`yq` Go version, `ajv-cli`, `gh`)
+- [ ] Package YAML validates against schema
+- [ ] Plugin YAML validates against schema
+- [ ] Both added to `all.yaml` files in **alphabetical order**
+- [ ] Namespace consistent between Package and Plugin
+- [ ] OCI URL correctly formatted
+- [ ] All required fields populated
+
+## Common Issues
+
+### Schema Validation Fails
+```bash
+# Debug by checking JSON conversion (using Go-based yq)
+yq eval your-file.yaml -o json | jq '.'
+
+# Common issues:
+# - Missing required fields
+# - Wrong field types
+# - Invalid enum values (e.g., wrong category)
+```
+
+### Wrong yq Version
+```bash
+# Check if you have the Go version
+yq --version
+
+# Should show: yq (https://github.com/mikefarah/yq/) version X.X.X
+
+# If you have the Python version (kislyuk/yq), uninstall and install Go version:
+# macOS: brew install mikefarah/yq/yq
+# Linux: snap install yq
+```
+
+### OCI URL Format
+Correct format: `oci://registry/path:tag!package-name`
+- Must include `!package-name` suffix
+- Tag typically includes PR number and version
+
+## References
+
+- [README with detailed documentation](../../catalog-entities/marketplace/README.md)
+- [Extension Schemas](https://github.com/redhat-developer/rhdh-plugins/tree/main/workspaces/marketplace/json-schema)
+- [RHDH Local Testing](https://github.com/redhat-developer/rhdh-local)
+- [Dynamic Plugins Documentation](https://docs.redhat.com/en/documentation/red_hat_developer_hub)