Regenerate placeholder documentation across CLI integrations

[thomhurst]

PR #4468 updates the shared usage-synopsis parser to preserve canonical CLI placeholder notation, but its acceptance criteria and checked-in regeneration are scoped to Chocolatey. Other generated integrations therefore remain stale until regenerated; for example, pnpm add <name> now models The <name> operand. while PnpmAddOptions.Generated.cs still contains The name operand..

A local 20-way regeneration already exceeded the mandated 2 GB agent guard, so complete this as a serialized/per-tool fast-follow after #4468 merges.

Acceptance criteria:

• Identify every tracked integration whose generated operand documentation changes under the placeholder-preserving parser.
• Regenerate those integrations from current tool output; do not hand-edit generated files.
• Commit all affected generated options/services/docs atomically or in clearly linked per-tool PRs.
• Verify deterministic regeneration and each affected tool solution within agent limits; leave exhaustive validation to CI where necessary.
• Confirm no unrelated command-surface drift is approved as part of the documentation refresh.

Follow-up from #4452 / #4468 and review discussion r3902977469.

[thomhurst]

Started the placeholder-documentation regeneration from exact main head 68c249cde1 on coordination branch issue-4474-placeholder-docs.

Authoritative workflow run: https://github.com/thomhurst/ModularPipelines/actions/runs/33507680640

The run covers all 46 non-AWS tools currently included in the generation matrix, with command-coverage shrinkage approval disabled and auto-merge disabled. Changed integrations will open linked per-tool PRs against the coordination branch; unchanged integrations will produce no PR. AWS is temporarily excluded because #4367 already has an exact-head AWS generation run using the shared automated AWS branch. After that run releases the branch, AWS will be generated into this coordination branch before the final PR to main.

Local multi-tool generation is intentionally not retried because the issue and repository guard record that it exceeds the mandated 2 GB limit.

[thomhurst]

Recovered coordination branch onto current main at exact head d6aa99ab55f3b3aba020f53fcb905d919e89da62.

• Obsolete Cargo documentation delta was already present on current main, so it was dropped during rebase rather than overwriting newer generated API.
• Flux, Pip, and Pnpm generated commits remain.
• Rerunning only the 13 failed matrix entries from the original audit, with command-coverage shrinkage approval disabled and auto-merge disabled: https://github.com/thomhurst/ModularPipelines/actions/runs/33696674158
• AWS remains serialized behind the active exact-head AWS run for test(aws): cover required options and CLI value rendering #4367 to avoid racing automated/update-cli-options-aws.

[thomhurst]

Recovered the coordination branch and merged current main conflict-free at 4cd2022. Existing linked child regenerations retained: Flux, Pip, Pnpm, Terraform, Kind. Local validation: Python build 0/0 + tests 1/1; Node build 0 errors (2 existing warnings) + tests 16/16; Terraform build 0/0 + tests 1/1; Kind build 0/0 + tests 1/1. Flux solution hit the mandated 2 GB guard (exit 137), so not retried; CI must validate it. The 12-entry rerun 33696674158 remains blocked in exact staging (for example, Kind deletes case-old KindExportKubeconfigOptions.Generated.cs, but Stage-GeneratedChanges rejects that generator-owned deletion). Issue remains open until failed integrations and serialized AWS regeneration land.

[thomhurst]

Acceptance audit at main 48df67cb325a6530e95b671df2f408bf601ec0f9:

The repository contains 47 tracked generation manifests. All 47 descend from the placeholder source fix #4468. The 46 non-Google integrations were refreshed in merged PRs on September 20–21, and each has a successful generated integration (...) CI check. This supersedes the old coordination-branch progress above; AWS and Flux are no longer waiting for that earlier validation.

Tool	Merged refresh
ansible	#5288
argocd	#5287
aws	#5317
az	#5329
brew	#5292
buildah	#5271
cargo	#5322
choco	#5311
cosign	#5304
docker	#5275
dotnet	#5309
eksctl	#5323
flux	#5319
flyway	#5290
gh	#5284
git	#5291
go	#5308
gradle	#5306
grype	#5270
hadolint	#5320
helm	#5296
jq	#5269
kind	#5274
kubectl	#5278
kustomize	#5294
liquibase	#5289
minikube	#5268
mvn	#5327
nbgv	#5301
newman	#5297
packer	#5285
pip	#5280
pnpm	#5293
podman	#5295
pulumi	#5326
shellcheck	#5267
skopeo	#5273
snyk	#5325
sonar-scanner	#5302
syft	#5321
terraform	#5324
trivy	#5276
vault	#5286
winget	#5299
yarn	#5277
yq	#5298

The original pnpm example is now documented as The <PACKAGE_NAMES> operand. (XML-escaped in generated C#). #5314 supplies the repeatability regression covering both canonical placeholders and generated Markdown.

Google remains outstanding: checked-in output is SDK 584, while the SDK 585 replacements have been closed for generator defects. The latest source correction is #5350, linked to #5180; its CI/reviews are running. Keep #4474 open until a fresh latest-main Google artifact passes actual integration tests, coverage/provenance checks, and review. The separate Snyk shared-factory follow-up remains tracked by #5009 after source PR #5330.

This audit verifies existing manifest lineage and integration checks. It does not claim that every historical review check passed or rerun local builds. No generated files or API baselines were edited.

[thomhurst]

Current-main audit: all 47 tracked integrations have generation provenance. The 46 non-Google integrations have accepted workflow refreshes dated September 20-21; Google remains on its older snapshot and is the final outstanding generated-output acceptance.

Examples covering the original recovery chain: Flux #5319, Pip #5280, Pnpm #5293, Terraform #5324, Kind #5274, Cargo #5322, AWS #5317, Azure #5329. The old staging failures and recovery-branch documentation deltas have been superseded by those merged authoritative refreshes.

I will keep this issue open until the fresh Google snapshot and its documentation/runtime checks pass after source fix #5350. The separate Snyk follow-up #5009 is also being regenerated after #5330; no generated options or API baselines are being patched by hand.