1. Proposed title of this feature request
 oc-mirror v2: Handle helm chart version format variations (v4.9.0 vs 4.9.0)
2. What is the nature and description of the request?
oc-mirror v2 fails during the upload phase when attempting to locate Helm chart files that were successfully downloaded. The tool expects a chart file with a specific filename (e.g., csi-driver-nfs-4.9.0.tgz) but the actual file has a different name (e.g., csi-driver-nfs-v4.9.0.tgz), causing the upload operation to fail with a "file not found" error.
3. Why does the customer need this? (List the business requirements here)
Reliable Mirror Operations: The upload phase should complete successfully after a successful download. Version format mismatches should not cause unpredictable failures. Reduced User Friction: Either through early validation guidance or automatic correction, users should not be blocked by filename inconsistencies caused by Helm version format variations beyond their control. Enterprise Automation: End-to-end mirror workflows must be reliable for automated and scripted deployments without manual intervention or file renaming.
4. List any affected packages or components.
oc-mirror v2