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

[github-actions]

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

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

Pre-flight integrity check

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

• Integrity failures: 27 of 27 files

Failing files

tests/safe-outputs/add-build-tag.lock.yml
tests/safe-outputs/add-pr-comment.lock.yml
tests/safe-outputs/azure-cli.lock.yml
tests/safe-outputs/comment-on-work-item.lock.yml
tests/safe-outputs/create-branch.lock.yml
tests/safe-outputs/create-git-tag.lock.yml
tests/safe-outputs/create-pull-request.lock.yml
tests/safe-outputs/create-wiki-page.lock.yml
tests/safe-outputs/create-work-item.lock.yml
tests/safe-outputs/janitor.lock.yml
tests/safe-outputs/link-work-items.lock.yml
tests/safe-outputs/missing-data.lock.yml
tests/safe-outputs/missing-tool.lock.yml
tests/safe-outputs/noop-target.lock.yml
tests/safe-outputs/noop.lock.yml
tests/safe-outputs/queue-build.lock.yml
tests/safe-outputs/reply-to-pr-comment.lock.yml
tests/safe-outputs/report-incomplete.lock.yml
tests/safe-outputs/resolve-pr-thread.lock.yml
tests/safe-outputs/smoke-failure-reporter.lock.yml
tests/safe-outputs/submit-pr-review.lock.yml
tests/safe-outputs/update-pr.lock.yml
tests/safe-outputs/update-wiki-page.lock.yml
tests/safe-outputs/update-work-item.lock.yml
tests/safe-outputs/upload-build-attachment.lock.yml
tests/safe-outputs/upload-pipeline-artifact.lock.yml
tests/safe-outputs/upload-workitem-attachment.lock.yml

Files updated

tests/safe-outputs/add-build-tag.lock.yml
tests/safe-outputs/add-pr-comment.lock.yml
tests/safe-outputs/azure-cli.lock.yml
tests/safe-outputs/comment-on-work-item.lock.yml
tests/safe-outputs/create-branch.lock.yml
tests/safe-outputs/create-git-tag.lock.yml
tests/safe-outputs/create-pull-request.lock.yml
tests/safe-outputs/create-wiki-page.lock.yml
tests/safe-outputs/create-work-item.lock.yml
tests/safe-outputs/janitor.lock.yml
tests/safe-outputs/link-work-items.lock.yml
tests/safe-outputs/missing-data.lock.yml
tests/safe-outputs/missing-tool.lock.yml
tests/safe-outputs/noop-target.lock.yml
tests/safe-outputs/noop.lock.yml
tests/safe-outputs/queue-build.lock.yml
tests/safe-outputs/reply-to-pr-comment.lock.yml
tests/safe-outputs/report-incomplete.lock.yml
tests/safe-outputs/resolve-pr-thread.lock.yml
tests/safe-outputs/smoke-failure-reporter.lock.yml
tests/safe-outputs/submit-pr-review.lock.yml
tests/safe-outputs/update-pr.lock.yml
tests/safe-outputs/update-wiki-page.lock.yml
tests/safe-outputs/update-work-item.lock.yml
tests/safe-outputs/upload-build-attachment.lock.yml
tests/safe-outputs/upload-pipeline-artifact.lock.yml
tests/safe-outputs/upload-workitem-attachment.lock.yml

How this was produced

• Downloaded ado-aw-linux-x64 from the v0.44.0 release and verified its SHA256 against checksums.txt.
• Ran ado-aw check tests/safe-outputs/*.lock.yml against the released binary to detect drift (27/27 files drifted).
• Ran ado-aw compile on each tests/safe-outputs/*.md 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.0).
• 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.2 AIC · ⌖ 12.7 AIC · ⊞ 10.1K · ◷