When launching a pipeline, some parameters depend on the value of other parameters (e.g., selecting a genome assembly should filter available annotation files, or selecting a project should populate available sample lists). Currently, all parameter values must be statically defined in the schema. Add support for dynamic parameter lookup — where selecting a value in one field triggers an API call or lookup to populate dependent fields — so users see only valid, context-appropriate options without manual entry.