Resolve a Nextflow pipeline's own declared test fixtures into Galaxy workflow test-data refs.
Every file beside index.md is one the mold kind declares.
source-specific fields are coherent.
Abstract oracle: the properties any cast of this Mold must satisfy.
eval.md not written yet.
Concrete cases bound to fixtures, run against the eval properties.
scenarios.md not written yet.
5 typed references; 0 resolver issues.
All on-demand references describe triggers.
Hypothesis references include verification.
Typed references describe what casting consumes, and when the generated skill should load each artifact.
Structured contract copied for validation or lookup.
Structured contract copied for validation or lookup.
Background synthesis loaded by explicit progressive-disclosure metadata.
Background synthesis loaded by explicit progressive-disclosure metadata.
Background synthesis loaded by explicit progressive-disclosure metadata.
Test data resolved from the pipeline's declared fixtures, expressed as URLs/paths plus expected shapes for downstream test authoring. Shared id with [[find-test-data]] — the branch's search fallback fills only the inputs this Mold leaves unresolved.
Structured Nextflow summary from [[summarize-nextflow]]; carries the enumerated `test_candidates[]` and explicit `test_selection`, with each candidate input represented by a role plus url/path, sha1, and filetype.
Galaxy interface brief from [[nextflow-summary-to-galaxy-interface]] pinning the workflow input labels, collection shapes, and datatypes each resolved fixture must map onto.
Resolve the Nextflow pipeline’s own declared test fixtures into Galaxy test-data-refs. The Nextflow summary carries every statically visible whole-pipeline case in test_candidates[] and records the default decision in test_selection. Each candidate owns its effective profiles, parameter delta, inputs, outputs, execution mode, scope, and assertions. Map the selected candidate’s inputs onto the Galaxy workflow and emit one ref per input, ready for implement-galaxy-workflow-test to stage. If selection is unresolved, surface that scope decision before resolving data rather than silently choosing by profile name.
This Mold is the source-specific first leg of the harness’s test-data-resolution branch. It resolves what the pipeline itself declares; any input it cannot resolve from a declared fixture stays a reported gap and the harness falls through to find-test-data (search), then to user-supplied. Deciding to fall through is a harness concern, not this Mold’s — its job is an honest map of the pipeline’s own fixtures.
test_selection. If it names a candidate, collect that candidate’s declared inputs: role, url/path, sha1, filetype, and description. If it reports needs-scope-choice, compare the candidates’ scope, execution mode, and input coverage and record the caller’s choice; do not infer scale or representativeness from a profile name alone.test-data-refs.json entry per resolved input: prefer the declared remote url + sha1 (remote-URL-first, iwc-test-data-conventions); fall back to the in-tree path plus provenance only when no URL is published. Carry datatype, collection element identifiers, and any subset/split prep. Each entry maps to an addressable workflow input label. Shape each entry per test-data-refs with resolved_by: nextflow-to-test-data, and validate the file with foundry validate-test-data-refs before returning.resolved: false with a reason and storage: unresolved — this is what the harness hands to find-test-data. Do not search public sources here; searching is find-test-data’s job, not this Mold’s.Never invent a URL, accession, or path, and never emit a placeholder for an input you could not resolve from a declared fixture. A declared fixture with no published URL is recorded by its in-tree path plus provenance, not papered over with a guessed URL. Every emitted ref points at data the pipeline actually declares; everything else is an honest gap for the next leg of the branch.