docs: cleanup README and FIELD_REFERENCE to remove unimplemented features

Author: vmrh21

workflows/cve-fixer/FIELD_REFERENCE.md

@@ -13,7 +13,7 @@ This document provides detailed information about the configuration fields in `.
 ### description
 - **Type:** string
 - **Purpose:** Explains workflow purpose in UI
-- **Current Value:** "This workflow can be used to scan your code base for CVEs and fix discovered CVEs"
+- **Current Value:** "Automate remediation of CVE issues reported by ProdSec team in Jira by creating pull requests with dependency updates and patches"
 - **Guidelines:** 1-3 sentences, clear and specific about workflow capabilities
 
 ### systemPrompt
@@ -81,17 +81,13 @@ This document provides detailed information about the configuration fields in `.
 
 ### Adding a new output type
 
-If you want to track additional artifacts (e.g., "Remediation Scripts"):
+If you want to track additional artifacts (e.g., "Test Results"):
 
 ```json
 "results": {
-  "Scan Results": "artifacts/cve-fixer/scans/**/*.json",
-  "Analysis Reports": "artifacts/cve-fixer/analysis/**/*.md",
-  "Priority Matrices": "artifacts/cve-fixer/priorities/**/*.md",
+  "Jira CVE Issues": "artifacts/cve-fixer/find/**/*.md",
   "Fix Implementations": "artifacts/cve-fixer/fixes/**/*",
-  "Verification Results": "artifacts/cve-fixer/verification/**/*.md",
-  "Remediation Reports": "artifacts/cve-fixer/reports/**/*.md",
-  "Remediation Scripts": "artifacts/cve-fixer/scripts/**/*.sh"
+  "Test Results": "artifacts/cve-fixer/tests/**/*.log"
 }
 ```
 
@@ -102,15 +98,15 @@ To use a different base directory (e.g., `security-artifacts/`):
 1. Update `systemPrompt` OUTPUT LOCATIONS section:
 ```
 OUTPUT LOCATIONS:
-- Create all scan results in: security-artifacts/cve-fixer/scans/
-...
+- Create all Jira CVE findings in: security-artifacts/cve-fixer/find/
+- Create all fix implementations in: security-artifacts/cve-fixer/fixes/
 ```
 
 2. Update `results` paths:
 ```json
 "results": {
-  "Scan Results": "security-artifacts/cve-fixer/scans/**/*.json",
-  ...
+  "Jira CVE Issues": "security-artifacts/cve-fixer/find/**/*.md",
+  "Fix Implementations": "security-artifacts/cve-fixer/fixes/**/*"
 }
 ```
 
@@ -139,25 +135,6 @@ KEY RESPONSIBILITIES:
 ...
 ```
 
-## Agent Files
-
-Agent persona files are located in `.claude/agents/` and follow this structure:
-
-```markdown
-# {Name} - {Role}
-## Role
-## Expertise
-## Responsibilities
-## Communication Style
-## When to Invoke
-## Tools and Techniques
-## Key Principles
-## Example Artifacts
-```
-
-**Current Agent:**
-- `vera-security-engineer.md` - Security engineering specialist for CVE remediation
-
 ## Command Files
 
 Slash command files are located in `.claude/commands/` and follow this structure:
@@ -181,8 +158,7 @@ Slash command files are located in `.claude/commands/` and follow this structure
 ## File Naming Conventions
 
 - **Workflow directory:** `workflows/cve-fixer/`
-- **Agent files:** `{name}-{role}.md` (e.g., `vera-security-engineer.md`)
-- **Command files:** `{workflow-prefix}.{phase}.md` (e.g., `cve.scan.md`)
+- **Command files:** `{workflow-prefix}.{phase}.md` (e.g., `cve.find.md`, `cve.fix.md`)
 - **Artifacts:** `artifacts/cve-fixer/{category}/{files}`
 
 ## Validation Checklist
@@ -191,11 +167,10 @@ Before using this workflow, verify:
 
 - [ ] `.ambient/ambient.json` is valid JSON (no comments, no trailing commas)
 - [ ] All required fields (name, description, systemPrompt, startupPrompt) are present
-- [ ] All agent files follow the template structure with required sections
 - [ ] All command files have unique names and follow naming convention
 - [ ] Output paths in `results` match those referenced in `systemPrompt`
 - [ ] Output paths in `results` match those in command files' ## Output sections
-- [ ] README.md accurately describes the workflow and all phases
+- [ ] README.md accurately describes the workflow and implemented commands
 - [ ] All file references use correct absolute or relative paths
 
 ## Configuration Best Practices
@@ -221,9 +196,6 @@ Before using this workflow, verify:
 **Problem:** Commands don't appear
 **Solution:** Ensure command files are in `.claude/commands/` and follow naming convention `{prefix}.{phase}.md`.
 
-**Problem:** Agent isn't being invoked
-**Solution:** Check that agent file exists in `.claude/agents/` and is referenced in workflow context.
-
 ## References
 
 - [ACP Documentation](https://ambient-code.github.io/vteam)