chore(workflows): recompile safe-output fixtures with ado-aw v0.44.1

[github-actions]

Recompile tests/safe-outputs/ against ado-aw v0.44.1

Bumps the version field in every tests/safe-outputs/*.lock.yml metadata marker from 0.44.0 to 0.44.1, picking up any compile-output changes shipped in ado-aw v0.44.1.

Pre-flight integrity check

Before recompiling, ado-aw check was run against every existing lock file using the released v0.44.1 binary:

• Integrity failures: 5 of 5 files

tests/safe-outputs/azure-cli.lock.yml
tests/safe-outputs/canary.lock.yml
tests/safe-outputs/janitor.lock.yml
tests/safe-outputs/noop-target.lock.yml
tests/safe-outputs/smoke-failure-reporter.lock.yml

Files updated

tests/safe-outputs/azure-cli.lock.yml
tests/safe-outputs/canary.lock.yml
tests/safe-outputs/janitor.lock.yml
tests/safe-outputs/noop-target.lock.yml
tests/safe-outputs/smoke-failure-reporter.lock.yml

How this was produced

• Downloaded ado-aw-linux-x64 from the v0.44.1 release and verified its SHA256 against checksums.txt.
• Ran ado-aw check tests/safe-outputs/*.lock.yml against the released binary to detect drift (5 failures).
• Ran ado-aw compile per-file for each pipeline fixture from the repo root.
• Re-ran ado-aw check against every regenerated lock file; all passed.
• The allowed-files glob in this workflow restricts the diff to tests/safe-outputs/**/*.lock.yml.

Reviewer checklist

• Diff is limited to metadata markers (and any genuinely new compile output for v0.44.1).
• No source .md fixture changes leaked in.
• Daily smoke pipelines in the AgentPlayground sandbox stay green after merge.

---

This PR was opened automatically by the recompile-safe-output-fixtures workflow.

Generated by Recompile safe-output fixtures · 47.8 AIC · ⌖ 12.5 AIC · ⊞ 10.1K · ◷