feat: drive azure-validate steps via workflow.ps1 script

[Tom Meschter (tmeschter)]

Summary

Fixes #2972.

Replaces the inline nine-step ## Steps table in the azure-validate SKILL.md with a workflow driver script that walks the agent through each validation step one at a time. This puts the workflow "on rails" — leaving less room for the agent to skip or deviate from steps — and sets up incrementally making each step script-based for a more deterministic skill.

Changes

• New references/scripts/workflow.ps1 — a step-driver script. The agent starts the workflow by calling it with -WorkspacePath (no -CompletedStep). Each response prints the next action plus the value to pass as -CompletedStep on the next call. The script records progress in .azure/validate-status.json itself, eliminating a per-step file-edit tool call by the agent.
• New references/scripts/workflow.sh — a bash equivalent for macOS/Linux, producing byte-for-byte identical agent-facing output to the PowerShell version.
• SKILL.md — the Steps section now instructs the agent to run the script (linking both the .ps1 and .sh variants) and follow its instructions until it reports the workflow is complete.

Review feedback addressed

• Validate that -WorkspacePath / --workspace-path exists and is a directory, failing early with a clear message instead of a later, more confusing error.
• Emit intended Markdown backticks in agent-facing output (they were previously consumed as PowerShell escapes); both scripts kept in sync.
• Write .azure/validate-status.json as UTF-8 without a BOM so non-PowerShell JSON consumers can parse it (Windows PowerShell 5.1 defaulted to UTF-16LE).

Validation

• npm run build succeeds (version stamping OK).
• npm run references passes (both scripts linked from SKILL.md; no orphaned files).
• Both scripts verified across all nine steps plus the start / invalid-step / missing-arg / bad-path cases; output is identical between the two.
• azure-validate vally evals: routing 100%. E2E stimuli that reach azure-validate exercise the -CompletedStep flow cleanly with zero script errors. The remaining e2e variance is unrelated top-level routing (azure-app-onboard vs azure-prepare → azure-validate) where azure-validate is never entered.

[Copilot]

Pull request overview

This PR updates the azure-validate skill to drive its validation process via a PowerShell step-driver script (workflow.ps1) instead of an inline multi-step table in SKILL.md, so an agent can advance through the workflow one step at a time while progress is persisted in the workspace.

Changes:

• Replaced the inline “Steps” table in azure-validate/SKILL.md with instructions to run a workflow driver script repeatedly, passing -CompletedStep.
• Added references/scripts/workflow.ps1 to emit the next action to perform and persist the last completed step to .azure/validate-status.json.

Show a summary per file

File	Description
plugin/skills/azure-validate/SKILL.md	Replaces the inline steps table with guidance to run workflow.ps1 iteratively using -CompletedStep.
plugin/skills/azure-validate/references/scripts/workflow.ps1	New PowerShell step-driver script that prints the next workflow action and writes .azure/validate-status.json.

Review details

Comments suppressed due to low confidence (2)

plugin/skills/azure-validate/references/scripts/workflow.ps1:67

• Same PowerShell escaping issue here: backticks in double-quoted strings won’t be printed as intended. Switching to single quotes also requires escaping the apostrophe in "recipe's".

    Write-Output "Action: Copy the recipe's `Validation Steps` into `.azure/deployment-plan.md` as children of `All validation checks pass`."
    Write-Output "Next: re-run workflow.ps1 with -CompletedStep AddValidationSteps after completing the action."
    Write-Output "Reference: references/recipes/README.md, `.azure/deployment-plan.md"

plugin/skills/azure-validate/references/scripts/workflow.ps1:115

• Backticks in these double-quoted strings are treated as PowerShell escapes, so inline-code formatting (and even the literal backticks) won’t appear in the output as written. Use single-quoted strings (or escape the backticks) for the intended output.

    Write-Output "Action: Only after ALL checks pass, set the plan status to `Validated`."
    Write-Output "Next: re-run workflow.ps1 with -CompletedStep UpdateStatus after completing the action."
    Write-Output "Reference: `.azure/deployment-plan.md"

• Files reviewed: 2/2 changed files
• Comments generated: 3
• Review effort level: Low