Regenerate stale msbuild-quality-review.lock.yml

[YuliiaKovalova]

Summary

Regenerates the stale msbuild-quality-review.lock.yml file that was causing the scheduled MSBuild Quality Review workflow to fail.

Error

ERR_CONFIG: Lock file '.github/workflows/msbuild-quality-review.lock.yml' is outdated!
The workflow file '.github/workflows/msbuild-quality-review.md' frontmatter has changed.
Run 'gh aw compile' to regenerate the lock file.

Failed run: https://github.com/microsoft/testfx/actions/runs/26204946075

Fix

gh aw compile msbuild-quality-review --strict

[Copilot]

Pull request overview

This pull request updates the generated agentic workflow lock file for MSBuild Quality Review to bring it back in sync with the corresponding .md source, resolving failures caused by a stale lock file during scheduled runs.

Changes:

• Regenerated .github/workflows/msbuild-quality-review.lock.yml (via gh aw compile msbuild-quality-review --strict) so the lock file metadata and resolved manifest match the current workflow sources/imports.

[Evangelink]

✅ 21/21 dimensions clean — no findings.

This PR regenerates the auto-generated msbuild-quality-review.lock.yml file via gh aw compile msbuild-quality-review --strict. The file is explicitly marked DO NOT EDIT and is managed by the gh-aw toolchain.

Notable changes compiled from the updated .md source:

• Updated frontmatter hash to match the changed workflow frontmatter
• Import reference updated: shared/reporting.md → shared/msbuild-review-shared.md (more specific shared module)
• Removed GH_AW_GITHUB_SERVER_URL env var propagation (consolidated by the compiler)
• GitHub MCP toolsets narrowed from context,repos,issues,pull_requests → issues,repos (principle of least privilege — appropriate for a scheduled scan that only needs to read/create issues)
• HEREDOC sentinel tokens updated (hash-based, auto-generated from content hashes)
• Updated workflow description text

All changes are consistent with a compiler regeneration. No manual edits, no behavioral regressions, no security concerns. The toolset reduction is a positive change (least privilege).

Generated by Expert Code Review (on open) for issue #8455 · ● 3.6M