A PowerShell runner was authored to seed data, alternate baseline and candidate runs, invoke Crank, and drive comparison, but the runtime was unavailable locally for parser or execution validation.
- What worked
- The scripting model fit Azure Pipelines variables and cross-step orchestration clearly.
- What got in the way
- No local PowerShell executable was available, so actual script behavior was not observed in this task.