[Automated] Update jq CLI Options

[thomhurst]

Summary

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

• jq (jq-1.8.2): 1 commands, tree c84d384f2a25cca2a8fde5eb61b0f81f728e5f778a232211b176ea80143877bc
  • Baseline comparison: 1 commands at jq-1.8.2 -> 1 commands at jq-1.8.2

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[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-13T23:18:33.319817Z	01404c5	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.

[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: 220e7459-bb46-455b-9762-63814c25e6d5

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

[greptile-apps]

Greptile Summary

This automated regeneration updates jq provenance metadata and brings its generated execution method in line with the repository's asynchronous library convention.

• Updates the recorded generator-source fingerprint without changing jq command coverage.
• Adds ConfigureAwait(false) to the generated jq command execution await.

Confidence Score: 5/5

The PR appears safe to merge because the generated-code adjustment matches repository conventions and no actionable regression was identified.

The only behavioral change suppresses synchronization-context capture in a pass-through async method with no post-await work or thread-affinity contract, while the metadata change presents no demonstrated inconsistency.

Important Files Changed

Filename	Overview
src/ModularPipelines.Jq/Generated/Jq.Generation.json	Updates the generated jq snapshot's source fingerprint while retaining the same tool version and command-tree fingerprint.
src/ModularPipelines.Jq/Services/Jq.Generated.cs	Adds the required ConfigureAwait(false) behavior to the generated command execution method.

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

[github-actions]

Review: [Automated] Update jq CLI Options

This is a minimal, auto-generated regeneration of the jq tool options, consistent with the scraper/generator workflow described in CLAUDE.md.

Changes:

• Jq.Generation.json: generatorSourceSha256 bump only — expected when the generator source changes, no CLI surface drift (tree hash for jq-1.8.2 is unchanged).
• Jq.Generated.cs: the sole await in the file now has .ConfigureAwait(false) appended.

Verification:

• This aligns with the immediately-preceding commit on main, fix(generator): emit context-independent service awaits (fix(generator): emit context-independent service awaits #4872), which taught the generator to emit ConfigureAwait(false) for generated service code — this PR is the regenerated output reflecting that fix, exactly as expected (src/ library code must use ConfigureAwait(false) per repo guidance).
• No hand-editing of generated output — the change is scoped entirely to the two generated files for this tool.
• No PublicAPI.Shipped.txt / PublicAPI.Unshipped.txt changes for ModularPipelines.Jq, matching the PR description's "No active public API changes were detected."
• The edited method signature and behavior are otherwise unchanged; this is a non-breaking internal await-configuration fix.

No actionable findings. This looks correct and safe to merge.

[thomhurst]

The generator workflow completed jq regeneration, public API synchronization, and the final integration build successfully: https://github.com/thomhurst/ModularPipelines/actions/runs/34788997774. This feature-target PR predates the main-branch trigger fix, so I dispatched .NET validation on its exact head 01404c5. That run must finish before this output is incorporated into #4644.

[thomhurst]

The exact-head .NET run 34789933624 has completed successfully, including Linux, Windows, macOS, analyzers, and trim/Native AOT. The final diff remains only jq provenance plus the generated ConfigureAwait(false) call; reviews are clear and there are no review threads. Incorporating this output into #4644.