[Automated] Update helm CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to helm CLI options classes.

The generator scraped the latest CLI help output from the installed tool.

Changes

• Updated options classes to reflect latest CLI documentation
• Added new commands if any were detected
• Updated option types and descriptions

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[claude]

Code Review

This PR contains a single-line automated update to the file for the Helm integration, bumping the generation timestamp from 2026-03-01T03:12:22 to 2026-03-08T03:08:53.

Assessment: ✅ No Issues Found

What this change does:

• Updates the ModularPipelines.OptionsGenerator.GeneratedAt metadata timestamp to reflect the latest regeneration run
• No actual options classes or CLI mappings were changed — this means the helm CLI help output hasn't changed since the last generation

Design & Architecture observations:

• The automated PR workflow is working as intended: the generator runs on a schedule, scrapes the latest helm CLI help output, and updates the assembly metadata even if there are no option changes. This provides a clear audit trail of when the generator last ran.
• Storing the generation timestamp as AssemblyMetadata is a clean, low-overhead approach that doesn't require additional metadata files.
• The fact that only the timestamp changed (and no options classes changed) is a good signal that helm's CLI interface is stable — this is expected behavior for a well-maintained tool.

No concerns. This PR is safe to merge.

🤖 Reviewed by Claude Code

[claude]

Code Review

This PR contains a single-line automated update to the AssemblyInfo.Generated.cs file for the Helm integration, bumping the generation timestamp from 2026-03-01T03:12:22 to 2026-03-08T03:08:53.

Assessment: No Issues Found

What this change does:

• Updates the ModularPipelines.OptionsGenerator.GeneratedAt metadata timestamp to reflect the latest regeneration run
• No actual options classes or CLI mappings were changed - this means the helm CLI help output has not changed since the last generation

Design and Architecture observations:

• The automated PR workflow is working as intended: the generator runs on a schedule, scrapes the latest helm CLI help output, and updates the assembly metadata even if there are no option changes. This provides a clear audit trail of when the generator last ran.
• Storing the generation timestamp as AssemblyMetadata is a clean, low-overhead approach that does not require additional metadata files.
• The fact that only the timestamp changed (and no options classes changed) is a good signal that helm CLI interface is stable - this is expected behavior for a well-maintained tool.

No concerns. This PR is safe to merge.

Reviewed by Claude Code

[claude]

Code Review

This is a minimal automated PR — the only change is a timestamp update in AssemblyInfo.Generated.cs:

-[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-03-01T03:12:22.1755791Z")]
+[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-03-15T03:15:19.1073587Z")]

Assessment: ✅ No issues found

The change is exactly what it claims to be — a re-run of the ModularPipelines.OptionsGenerator against the helm CLI that produced no structural changes to options classes, only refreshing the GeneratedAt timestamp. This confirms the Helm CLI options are still up to date with the installed tool version.

Observations

1. Intentional design: Updating the timestamp even when no CLI options changed is a sensible approach — it provides an audit trail showing the generator was run and the options were verified to be current, without requiring a manual "no-op" indicator.

2. No options drift: The absence of any changes to actual options classes (under src/ModularPipelines.Helm/Options/) is a positive signal that the Helm CLI interface has remained stable since the last generation on 2026-03-01.

3. Minor consideration (not a blocker): If the goal is to reduce noise in git history, one could skip committing purely timestamp-only updates. However, this is a product/workflow decision, and the current approach has the benefit of proving the generator ran successfully. The existing pattern is consistent with how other automated CLI option PRs work in this repo.

This PR is safe to merge.