fix: RA2.2 README title and versions still refer to 26.1

[andrewwhitecdw]

This PR corrects the documentation in profiles/spectrum-x-ra2.2/README.md: RA2.2 README title and versions still refer to 26.1.

Changes

• profiles/spectrum-x-ra2.2/README.md: RA2.2 README title and versions still refer to 26.1.

Details

--- a/profiles/spectrum-x-ra2.2/README.md
+++ b/profiles/spectrum-x-ra2.2/README.md
@@ -1,5 +1,5 @@
-# Spectrum-X Multi-Rail Profile
+# Spectrum-X Multi-Rail Profile (RA2.2, Network Operator 26.4)

 ## Overview

@@ -1,9 +1,9 @@
 ### Prerequisites

 1. Kubernetes cluster with SR-IOV capable nodes
-2. NVIDIA Network Operator v26.1.0 or later
+2. NVIDIA Network Operator v26.4.0
 3. ConnectX-8, ConnectX-9, or BlueField-3 SuperNIC adapters
 4. Firmware compatible with Spectrum-X RA2.2

Tests

• profiles/spectrum-x-ra2.2/README.md

Add a markdown lint or grep assertion in the profile CI checks that fails if `profiles/spectrum-x-ra2.2/README.md` contains `v26.1.0` or an unqualified `Spectrum-X Multi-Rail Profile` title.

Contributor guidelines

Per this repo's CONTRIBUTING.md:

• All commits are signed off (Signed-off-by trailer, DCO).

[greptile-apps]

Greptile Summary

The PR updates the RA2.2 profile documentation from Network Operator 26.1 to the 26.4 release line.

• Qualifies the profile title and overview as RA2.2.
• Updates the prerequisite and manual Helm installation command to v26.4.0, although the tool’s release catalog resolves 26.4 to v26.4.1.

Confidence Score: 4/5

The PR is not yet safe to merge because its manual installation command deploys a different chart patch than l8k expects for release 26.4.

A user who installs v26.4.0 from the changed README and subsequently runs l8k deploy for release 26.4 encounters a chart-version conflict because the embedded catalog resolves that release to v26.4.1.

Files Needing Attention: profiles/spectrum-x-ra2.2/README.md

Important Files Changed

Filename	Overview
profiles/spectrum-x-ra2.2/README.md	Updates the documented RA and Network Operator versions, but its v26.4.0 Helm pin conflicts with the v26.4.1 chart resolved by the release catalog.

_{Reviews (2): Last reviewed commit: "fix: RA2.2 README title and versions sti..." | Re-trigger Greptile}

[greptile-apps]

Release compatibility exceeds profile bounds

When a user selects Network Operator 26.5 or later based on the new 26.4+ title or v26.4.0 or later prerequisite, the profile rejects that release because its minimum and maximum release bounds are both 26.4, preventing generation or deployment.

Knowledge Base Used:

• Spectrum-X addressing and topology
• Documentation Site (docs/)

[andrewwhitecdw]

@greptile-apps Thanks for the review. I have corrected the compatibility wording to match the profile release bounds: the title now reads Network Operator 26.4 (not 26.4+) and the prerequisite reads v26.4.0 (without or later). The commit has been amended and pushed.

[greptile-apps]

All three locations are correctly updated — the title, the prerequisite line, and the Helm install command all now consistently read 26.4 / v26.4.0 without the open-ended + or or later. The fix looks good.

[greptile-apps]

Documented chart conflicts with catalog

When a user installs Network Operator v26.4.0 with this command and later runs l8k deploy for release 26.4, the embedded catalog resolves the expected chart to v26.4.1, causing deployment to abort with a chart-version conflict and exit code 4.

Knowledge Base Used: Spectrum-X addressing and topology