Run gxwf validation on the just-implemented Galaxy step and route failures back to step implementation.
Directory Mold with only index.md frontmatter.
target-specific fields are coherent.
eval.md declares cases and check type.
2 typed references; 0 resolver issues.
All on-demand references describe triggers.
Hypothesis references include verification.
Typed Mold references describe what casting consumes and when the generated skill should load each artifact.
Command reference. Usually cast to a sidecar and loaded only when invoked.
Background synthesis loaded by explicit progressive-disclosure metadata.
Validate the Galaxy workflow fragment after one step has been implemented. The Mold owns the inline validation loop: run gxwf validate, classify diagnostics that are local to the new step, and route failures back to implement-galaxy-tool-step or author-galaxy-tool-wrapper as appropriate.
This is separate from validate-galaxy-workflow because the harness behavior differs: step validation runs inside the per-step loop and should preserve local context about the step that just changed.