[Automated] Update kind CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to kind 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] Update kind CLI Options

This is an automated PR generated by ModularPipelines.OptionsGenerator to keep the kind CLI options classes in sync with the latest installed tool version.

Changes Summary

The PR contains two minimal, focused changes:

1. AssemblyInfo.Generated.cs: Timestamp update from 2026-02-15 to 2026-03-01, reflecting when the options were regenerated.

2. KindBuildNodeImageOptions.Generated.cs: Updated the default base image tag in the BaseImage XML doc comment from docker.io/kindest/base:v20260131-d56c8839 to docker.io/kindest/base:v20260214-ea8e5717.

Review

No issues found. This is exactly the kind of minimal, targeted update expected from an automated options sync process.

A few observations worth noting for the generator pipeline design:

• The change correctly updates only the doc comment (which documents the CLI tool's default), not any hardcoded default value in code — this is the right approach since the default lives in the kind binary itself.
• The generated files are correctly marked with [ExcludeFromCodeCoverage] (as per project conventions), so this change carries no test coverage implications.
• The timestamp-based metadata in AssemblyInfo.Generated.cs provides a useful audit trail for tracking when options were last synced — a good practice for generated code.

Verdict: LGTM - The automated tooling is working as intended, keeping downstream consumers up to date with the latest kind base image defaults.