[Automated] Update nbgv CLI Options

[thomhurst]

Summary

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

• nbgv (3.10.91+e05abbcae4): 7 commands, tree 7a9c8d889f1ee1248bbdd066caabfaaf53477dea0c81e97ea9f405b33bda6b63
  • Baseline comparison: 7 commands at 3.10.91+e05abbcae4 -> 7 commands at 3.10.91+e05abbcae4

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 93131c9b-e726-42fc-8b7a-b58867c211a5

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.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-14T03:54:40.542719Z	b957bb6	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[greptile-apps]

Greptile Summary

This PR refreshes the nbgv generation provenance after generator-source changes.

• Updates only generatorSourceSha256.
• Leaves the tool version and command-tree fingerprint unchanged.
• Does not alter generated command options or public APIs.

Confidence Score: 5/5

The PR appears safe to merge because the metadata-only checksum update matches the repository’s generation-provenance design.

The source fingerprint is intentionally independent of generated output and the command-tree checksum, and no actionable failures or rule violations remain.

Important Files Changed

Filename	Overview
src/ModularPipelines.NerdbankGitVersioning/Generated/Nbgv.Generation.json	Updates the generator-source provenance checksum consistently with changes to fingerprinted generator sources.

_{Reviews (1): Last reviewed commit: "chore: Update nbgv CLI options" | Re-trigger Greptile}

[github-actions]

Review: [Automated] Update nbgv CLI Options (#4923)

This is a bot-generated provenance refresh, not a hand-written change. The diff touches a single file and a single field:

```diff

• "generatorSourceSha256": "baaf09c947b655eca7003d9a905d7255e52dcfe8be5dc849bfb13af636805a4e"

• "generatorSourceSha256": "0e7b8148ac358e31f6466ef6ad8bc639988519d3411edfb27a394b2bda1bdc16"
  ```

Verification performed:

• Confirmed generatorSourceSha256 is written by scripts/Write-GeneratedOptionsProvenance.ps1 via Get-GeneratedOptionsSourceFingerprint, and is a hash over the generator's own source, independent of toolVersion/commandTreeSha256. Since the base branch (issue-4655-repeatable-continuation) recently modified the generator's help-timeout handling (Report exhausted help timeouts instead of phantom removed commands #4688), a fingerprint bump with no commandTreeSha256 or command-option changes is exactly the expected output — not a hand-edit and not a sign of drift.
• toolVersion and commandTreeSha256 are unchanged, and no generated .cs option classes changed, consistent with the PR description's "No active public API changes were detected."
• Per CLAUDE.md, generated options/provenance files must come from the generator, never hand-edited — this file is fully machine-written and requires no manual reconciliation.

No functional, design, or architectural concerns — there's no hand-written logic in this diff to critique. Safe to merge as-is.