fix: remove all RHOAIENG project references from docs and commands

Replace RHOAIENG-specific Jira issue key examples with generic PROJ-XXXXX
placeholders across cve.find.md, cve.fix.md, and README.md to make the
workflow fully team-agnostic.

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

Author: vmrh21

workflows/cve-fixer/.claude/commands/cve.find.md

@@ -13,8 +13,8 @@ Example:
 Querying Jira... Found 2 CVEs
 
 Results:
-- RHOAIENG-49745: CVE-2025-68121
-- RHOAIENG-48536: CVE-2025-61726
+- PROJ-49745: CVE-2025-68121
+- PROJ-48536: CVE-2025-61726
 
 Report: artifacts/cve-fixer/find/cve-issues-20260226-145018.md
 ```

workflows/cve-fixer/.claude/commands/cve.fix.md

@@ -34,7 +34,7 @@ Summary:
 1. **Load CVEs from Find Output or User-Specified Jira Issue**
 
    **Option A: User specifies one or more Jira issues**
-   - If user provides one or more Jira issue IDs (e.g., `/cve.fix RHOAIENG-4973` or `/cve.fix RHOAIENG-4973 RHOAIENG-5821`):
+   - If user provides one or more Jira issue IDs (e.g., `/cve.fix PROJ-4973` or `/cve.fix PROJ-4973 PROJ-5821`):
      - Process each issue independently -- extract CVE ID and component from each
      - Use the provided Jira issue ID(s) directly
      - Fetch the issue details from Jira API
@@ -687,7 +687,7 @@ Summary:
        - **If using `/cve.find` output (Option B)**:
          - Read the latest `/cve.find` output from `artifacts/cve-fixer/find/`
          - Search for all Jira issues that mention this specific CVE ID in their summary
-         - Extract the issue IDs (e.g., RHOAIENG-17794, RHOAIENG-16619, etc.)
+         - Extract the issue IDs (e.g., PROJ-12345, PROJ-12346, etc.)
          - Collect all issue IDs for this CVE
      - Generate comprehensive PR description with:
        - CVE details and severity
@@ -698,9 +698,9 @@ Summary:
        - Risk assessment table
        - Links to CVE advisories
        - **Jira issue references**: List the extracted Jira issue IDs as plain text WITHOUT hyperlinks
-         - ✅ Correct: `Resolves: RHOAIENG-17794, RHOAIENG-16619, RHOAIENG-16616`
-         - ❌ Wrong: `Resolves: [RHOAIENG-17794](https://redhat.atlassian.net/browse/RHOAIENG-17794)`
-         - ❌ Wrong: `Multiple RHOAIENG issues for CVE-2024-21538 across different release branches`
+         - ✅ Correct: `Resolves: PROJ-12345, PROJ-12346, PROJ-12347`
+         - ❌ Wrong: `Resolves: [PROJ-12345](https://redhat.atlassian.net/browse/PROJ-12345)`
+         - ❌ Wrong: `Multiple Jira issues for CVE-2024-21538 across different release branches`
          - Do NOT create markdown links for Jira issues
          - Do NOT use generic descriptions - list the ACTUAL issue IDs
          - Just list the issue IDs separated by commas
@@ -719,7 +719,7 @@ This PR fixes **CVE-YYYY-XXXXX** by upgrading <package> from X.X.X to Y.Y.Y.
 - **Impact**: [Description]
 - **Vulnerable versions**: X.X.X - X.X.X
 - **Fixed version**: Y.Y.Y
-- **Jira Issues**: RHOAIENG-XXXXX, RHOAIENG-YYYYY
+- **Jira Issues**: PROJ-XXXXX, PROJ-YYYYY
 
 ### Test Results
 
@@ -896,12 +896,12 @@ Fix all open CVEs from /cve.find output (default):
 
 Fix specific Jira issue:
 ```
-/cve.fix RHOAIENG-4973
+/cve.fix PROJ-4973
 ```
 
 Fix multiple specific Jira issues:
 ```
-/cve.fix RHOAIENG-4973 RHOAIENG-5821
+/cve.fix PROJ-4973 PROJ-5821
 ```
 
 Fix with custom message:
@@ -910,7 +910,7 @@ Fix with custom message:
 ```
 
 **How it works**:
-- If you provide Jira issue IDs (e.g., RHOAIENG-XXXXX), the workflow will fix those specific issues
+- If you provide Jira issue IDs (e.g., PROJ-XXXXX), the workflow will fix those specific issues
 - If you don't provide Jira IDs, the workflow will:
   1. Read the latest `/cve.find` output
   2. Extract all CVEs with `Status: Open`
@@ -1097,5 +1097,5 @@ After completing this phase:
 - Include CVE ID in commit title
 - Document breaking changes in commit body
 - Reference Jira issues being resolved (plain text IDs, no hyperlinks)
-  - Example: `Resolves RHOAIENG-17794, RHOAIENG-427`
+  - Example: `Resolves PROJ-12345, PROJ-427`
 - Add Co-Authored-By for AI agent assistance

workflows/cve-fixer/README.md

@@ -202,8 +202,8 @@ Implement remediations for CVEs discovered in Jira by creating pull requests wit
 **Usage:**
 ```bash
 /cve.fix                           # Will prompt for component and Jira issues
-/cve.fix RHOAIENG-12345           # Fix specific Jira issue
-/cve.fix RHOAIENG-12345,RHOAIENG-12346  # Fix multiple issues
+/cve.fix PROJ-12345           # Fix specific Jira issue
+/cve.fix PROJ-12345,PROJ-12346  # Fix multiple issues
 ```
 
 **What it does:**
@@ -281,7 +281,7 @@ artifacts/cve-fixer/
 # Step 2: Review the discovered issues in artifacts/cve-fixer/find/
 
 # Step 3: Implement fixes and create PRs
-/cve.fix RHOAIENG-12345,RHOAIENG-12346
+/cve.fix PROJ-12345,PROJ-12346
 
 # Step 4: Review the created PRs and merge when ready
 ```