fn validate_instructions_by_provider(
bundle: &Bundle,
issues: &mut Vec<ValidationIssue>,
)Expand description
Every key must resolve to a known harness provider (providers::get_provider
handles both canonical ids and aliases). Unlike context_files’
arbitrary user-supplied paths, provider keys are always exact matches
against providers.rs’s hardcoded registry/alias strings — none of
which contain / or . — so a path-normalization collision between two
valid keys structurally cannot happen here; no collision check needed.