Pin @galaxy-tool-util/cli (gxwf) to 1.7.2 + capability-probe availability check

[jmchilton]

Authored by Claude (AI assistant) on behalf of @jmchilton.

Why

A pipeline test-drive surfaced that content/cli/gxwf/index.md and content/cli/galaxy-tool-cache/index.md reference @galaxy-tool-util/cli unpinned. A cast consumer without the repo lockfile can resolve a gxwf lacking the draft-tier subcommands (draft-validate / draft-next-step / draft-extract) that the per-step authoring loop and the template/loop eval gates depend on.

Changes

• Pin to 1.7.2 in both cli-tool notes: add package_version: "1.7.2" and pin invoke_fallback to npx --yes --package @galaxy-tool-util/cli@1.7.2 …. Mirrors the existing planemo pinning pattern. The caster auto-versions the npm install -g line from package_version but copies invoke_fallback verbatim, so both fields are set.
• Capability-probe availability_check (replaces gxwf --version): gxwf --help | grep -q draft-validate (and … grep -q summarize for galaxy-tool-cache). Empirically, @galaxy-tool-util/cli@1.7.2's gxwf --version reports a hardcoded 1.0.0 regardless of the published package version — a version-number gate would reject the correct CLI. The probe asserts the actual subcommand instead.
• Regenerated all affected Mold casts + pipeline harnesses. This also folds in pending bundle drift those casts already carried: the $comment jmchilton/foundry → galaxyproject/foundry rename in galaxy-tool-summary.schema.json, a galaxy-workflow-draft-format.md ref refresh, and open-requirements-ledger.md now bundled into the draft-tier Mold casts.

Also includes the pre-existing "Remove emulated run" cleanup commit that was one ahead of main.

Verification

• npm run validate → 0 errors
• make check-assemble-pipelines → clean
• npm run cast -- … --check → clean on the formerly-erroring freeform-summary-to-galaxy-template + advance-galaxy-draft-step
• npm run test → 134/134

Note: the galaxyWorkflowDraftJsonSchema "missing export" error seen during the run was a stale local node_modules (lagging the ^1.7.2 lockfile pin), not a code bug — fixed by pnpm install --frozen-lockfile, no source change. Not part of this diff.

🤖 Generated with Claude Code