[Automated] Update winget CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to winget 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 is a minimal automated PR with a single-line change: updating the ModularPipelines.OptionsGenerator.GeneratedAt timestamp in AssemblyInfo.Generated.cs from 2026-03-29T03:15:26.3027413Z to 2026-04-05T03:15:33.1227722Z.

Summary

The change is exactly what it claims to be — a routine timestamp refresh produced by the ModularPipelines.OptionsGenerator tool. No options classes, service interfaces, or generated command bindings were modified, which means the generator ran but detected no structural changes to the winget CLI since the last generation cycle.

Observations

No functional impact. The AssemblyMetadata attribute carrying the generation timestamp is purely informational. It does not affect runtime behaviour, serialisation, or any API surface.

The auto-merge + squash configuration is appropriate. For automated housekeeping PRs of this kind, having auto-merge enabled is the right default so they don't accumulate.

Potential noise concern. If the generator is scheduled to run on a fixed cadence (e.g. weekly), it will produce a PR every cycle even when there are no actual CLI changes — resulting in one-line timestamp-only PRs like this one. Consider whether the generator workflow should suppress a PR (or amend the existing open one) when the only diff is the timestamp itself. This would reduce noise in the PR history without losing auditability.

No issues found. The generated file is correctly marked // <auto-generated>, the assembly metadata keys are consistent with other tool packages in the repo, and the UTC timestamp format is correct.

Overall this PR is clean and safe to merge.

[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

_{TIP This summary will be updated as you push new changes. Give us feedback}