[Automated] Update kustomize CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to kustomize 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: Automated kustomize CLI Options Update

This is a clean automated PR with a single, minimal change.

What Changed

The only change is the GeneratedAt timestamp in AssemblyInfo.Generated.cs:

• From: 2026-02-15T03:11:57.0151177Z
• To: 2026-03-01T03:12:17.9393190Z

Assessment

No actual CLI option classes were modified — only the generation timestamp was bumped. This means the kustomize tool's help output/CLI interface has not changed since the last generation run on February 15th. The generator ran, scraped the CLI output, found no differences in commands/options/types, and correctly produced only a timestamp update.

This is the expected and correct behavior for this automation: the generator should always update the timestamp to reflect when it last verified the options, even if nothing substantive changed.

Verdict

✅ Approved — the change is correct, minimal, and well-scoped. Auto-merge is appropriate here.

[claude]

Code Review: Automated kustomize CLI Options Update

This is a clean automated PR with a single, minimal change.

What Changed

The only change is the GeneratedAt timestamp in AssemblyInfo.Generated.cs:

• From: 2026-02-15T03:11:57.0151177Z
• To: 2026-03-01T03:12:17.9393190Z

Assessment

No actual CLI option classes were modified - only the generation timestamp was bumped. This means the kustomize tool's CLI interface has not changed since the last generation run on February 15th. The generator ran, scraped the CLI output, found no differences in commands/options/types, and correctly produced only a timestamp update.

This is the expected and correct behavior for this automation: the generator should always update the timestamp to reflect when it last verified the options, even if nothing substantive changed.

Verdict

Approved - the change is correct, minimal, and well-scoped. Auto-merge is appropriate here.