review-galaxy-workflow

Review one Galaxy workflow submission under the pinned upstream IWC review policy and return one advisory Markdown review. This Mold reads evidence; it does not produce or change a workflow, and it cannot approve, push, comment, label, mark ready, or merge.

Procedure

1. Establish the reviewed subject and its evidence

• Read the concrete workflow — the normalized starting-galaxy-workflow.gxwf.yml, or the galaxy-workflow.gxwf.yml a Foundry run supplied directly.
• Read summary-galaxy-workflow.json for inputs, outputs, tool ids and versions, tool state, connections, labels, annotations, and existing tests. Do not re-extract what the summary already carries.
• Read galaxy-workflow-validation-result.json and workflow-test-result.json. Record each status verbatim. Never run gxwf validate or planemo test inside this Mold, and never upgrade an unverified item to a pass on the strength of inspection.
• Inventory the optional inputs and record which ones were present. Never describe an absent artifact as inspected.

2. Select the repository profile

• IWC: the primary descriptor is the native .ga workflow; apply the upstream checklist to it.
• IWC-Lab: the primary Galaxy descriptor is the one named by the submission’s .dockstore.yml, which may be a .gxwf.yml file. Apply the same descriptor-level checks to that file.
• When no .dockstore.yml was supplied, state which profile was assumed and why.

3. Apply the pinned IWC policy

Read the bundled review command and work its checklist in order. Adapt repository terminology where the profile requires it; do not silently add, drop, or soften a policy item. For each applicable item record exactly one of pass, needs attention, not applicable, or unverified, with file and field evidence. Prefer the deterministic evidence from step 1 wherever it answers a checklist question — cite the Planemo result rather than concluding from inspection that a test passed.

4. Add Foundry context only when it was supplied

When iwc-comparison-notes, an open-requirements-ledger, or source and design handoffs are present, add a clearly labeled Foundry context section covering unresolved intent, surrendered or dropped work, and test strength. When they are absent, omit the section or state that no Foundry context was supplied. Their absence is never an IWC finding. Do not rerun compare-against-iwc-exemplar; consume its existing output.

5. Write the review

Emit galaxy-workflow-review.md with, in order:

1. reviewed repository, pull request, head SHA, workflow directory, repository profile, and prompt provenance — name the bundled prompt reference and the hash recorded for it in this cast’s provenance record, and make no claim about upstream policy newer than that pin;
2. the validation result and the Planemo test result, quoted as statuses rather than as conclusions;
3. the applicable IWC checklist, one status and its evidence per item;
4. the Foundry context section, when one was supplied;
5. required fixes, separated from optional improvements, separated from evidence that was unavailable; and
6. exactly one advisory recommendation: approve, request changes, or needs discussion.

Non-goals

• No gxwf validate or planemo test execution, and no re-derivation of the summary.
• No workflow, test, or companion-file edit, and no changeset. An accepted edit is mature-galaxy-workflow-for-iwc‘s business, routed through apply-galaxy-workflow-changeset.
• No GitHub mutation of any kind — no review, approval, comment, label, push, ready-for-review, or merge.
• No JSON report, no stable finding ids, and no freshness claim about a correctly pinned prompt.