Resolve a CWL workflow's own declared test cases 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 CWL source's declared test cases, 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 CWL summary from [[summarize-cwl]]; carries the source's test cases (`tests[]`) — each a `job_path` (a CWL job file naming the test inputs) plus `expected_outputs`.
Galaxy interface brief from [[cwl-summary-to-galaxy-interface]] pinning the workflow input labels, collection shapes, and datatypes each resolved fixture must map onto.
Resolve the CWL workflow’s own declared test cases into Galaxy test-data-refs. The CWL summary carries the source’s test cases (tests[]) — each a job_path (a CWL job file naming the test inputs) plus expected_outputs. Read the declared inputs and map them onto the Galaxy workflow’s inputs, emitting one ref per input, ready for implement-galaxy-workflow-test to stage.
This Mold is the source-specific first leg of the harness’s test-data-resolution branch. It resolves what the CWL source itself declares; any input it cannot resolve from a declared test case 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 source’s own test cases.
tests[], read each case’s job_path inputs — File/Directory objects with their location/path, secondaryFiles, arrays, and inline literals — plus expected_outputs. Prefer the case whose inputs best cover the workflow’s inputs.secondaryFiles may map to a record or composite datatype — record element identifiers and any prep needed to reach the Galaxy collection shape (galaxy-workflow-testability-design).test-data-refs.json entry per resolved input: prefer a remote location URL when the job references one (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: cwl-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 test case. A declared input 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 source actually declares; everything else is an honest gap for the next leg of the branch.