[Automated] Update cargo CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to cargo 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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

This is a minimal automated PR — the only change is a timestamp update in AssemblyInfo.Generated.cs, bumping the GeneratedAt metadata from 2026-04-19T03:17:11Z to 2026-04-26T03:44:30Z.

What's Good

• Clean automation pattern: Using AssemblyMetadata to track generation timestamps is a solid audit trail approach. It makes it easy to know when any given assembly's bindings were last refreshed.
• No noise: The diff is exactly what it should be for a re-run that found no changes to the underlying cargo CLI — just the timestamp.
• Auto-merge with squash is the right strategy for this kind of automated maintenance PR; it keeps history clean.

Observation

The diff only shows the timestamp update, which implies the cargo CLI options themselves haven't changed since the last generation run (2026-04-19). This is expected behavior from the generator — if no new flags/commands were detected, only the metadata gets bumped.

If you ever want more confidence during review, it could be useful to have the generator emit a summary line like // No option changes detected or log a diff count in the PR description (e.g. "0 options added, 0 removed, 0 modified") so reviewers can confirm the no-op nature at a glance rather than having to diff the full generated file mentally.

Verdict

The change is correct and safe. ✓ Approving.