[Automated] Update dotnet CLI Options

[thomhurst]

Summary

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

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• dotnet (10.0.400): 97 commands, tree 5a6ae5c35827884fff645cc37ecfe24e941dde2425778fae8feb055e1a0e1155
  • Baseline comparison: 97 commands at 10.0.400 -> 97 commands at 10.0.400

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• src/ModularPipelines.DotNet/Generated/DotNet.Generation.json is excluded by !**/generated/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 64c49bf5-6891-41a8-a06b-ead2198dbcc9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Review

This PR is a fully automated, bot-generated update from ModularPipelines.OptionsGenerator for the dotnet tool. The actual diff is a single line in src/ModularPipelines.DotNet/Generated/DotNet.Generation.json, bumping generatorSourceSha256 from 773b4f94...a63497 to bdf2981a...5e620.

• No generated option classes, command surfaces, or public API changed — command coverage stayed at 97/97 commands for dotnet 10.0.400.
• The hash change reflects the generator's own source-input fingerprint being refreshed against origin/main, which is expected and correct behavior per scripts/Write-GeneratedOptionsProvenance.ps1 / scripts/Assert-GeneratedOptionsFreshness.ps1 — each tool's provenance file is refreshed independently, so only the dotnet Generation.json changing here is not an inconsistency.
• Both hash values are well-formed 64-hex-char SHA-256 strings.
• Per CLAUDE.md, generated files under Generated/ should never be hand-edited, and this PR doesn't touch any hand-written code — it's exactly the kind of change that should flow through the generator/provenance pipeline untouched.
• CodeRabbit's automated review skipped this file entirely (path-filtered as generated output), and there are no unresolved prior review comments to reconcile.

No behavior, API, or logic changes to review — nothing actionable found.

[github-actions]

Review

This PR is a fully automated, bot-generated update from ModularPipelines.OptionsGenerator for the dotnet tool. The only change is a single line in src/ModularPipelines.DotNet/Generated/DotNet.Generation.json, bumping generatorSourceSha256 from 773b4f94...a63497 to 4f583590...339444.

• No generated option classes, command surfaces, or public API changed — command coverage stays at 97/97 commands for dotnet 10.0.400, and the command tree SHA (5a6ae5c3...) is unchanged.
• The hash change reflects the generator's own source-input fingerprint being refreshed, which is expected: per CLAUDE.md, current tool output is authoritative and generated files should never be hand-edited, and this PR doesn't touch any hand-written code.
• A prior automated review already cleared an earlier revision of this same commit (a different generatorSourceSha256 value); the commit was subsequently updated/re-signed and now carries a new hash, but the nature of the change is identical — no logic or API impact.
• Both hash values are well-formed 64-hex-char SHA-256 strings.

No behavior, API, or logic changes to review — nothing actionable found.