[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: [Automated] Update cargo CLI Options

Summary: This is a fully automated PR that updates only the AssemblyMetadata timestamp for ModularPipelines.OptionsGenerator.GeneratedAt in AssemblyInfo.Generated.cs — no options classes or logic were changed.

Change Analysis

-[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-04-26T03:44:30.6701984Z")]
+[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-05-03T03:37:35.5209964Z")]

This is a weekly re-run of the options generator against the installed cargo CLI. The only recorded change is that the generator ran again on 2026-05-03, and the cargo CLI options appear unchanged from the previous generation (no additions, removals, or description updates in the options classes themselves).

Assessment

No issues found. This is exactly the expected output for an automated options generator PR when the upstream cargo CLI has not added or changed any commands or flags since the last run. The timestamp bump serves as a useful audit trail confirming the tool was scraped and was consistent.

One minor observation worth considering at the generator/pipeline level (not a blocker for this PR): if cargo's CLI output is identical to the previous run, emitting a PR that only bumps a timestamp adds some noise. A future improvement to the generator could skip creating a PR when there are no meaningful diffs in the options classes themselves, or label such PRs as "no-op" to make triage faster. That said, the current approach is safe and traceable.

✅ Approve as-is — the automated change is correct and harmless.