Recompile pr-sous-chef lock workflow to resolve stale frontmatter hash

[Copilot]

The PR Sous Chef scheduled run failed before activation because .github/workflows/pr-sous-chef.lock.yml no longer matched .github/workflows/pr-sous-chef.md. This PR regenerates the compiled lock file so runtime validation accepts the workflow again.

• What changed

  • Recompiled pr-sous-chef from source markdown.
  • Updated only .github/workflows/pr-sous-chef.lock.yml (metadata hash + deterministic regenerated lock content).

• Why this resolves the failure

  • The activation guard checks lock/source consistency via frontmatter hash.
  • Regenerating the lock file brings the compiled artifact back in sync with the markdown source.

• Example of the key delta

  -# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"4bbfd40c...","strict":true,"agent_id":"copilot","agent_model":"gpt-5-mini"}
  +# gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"f1496174...","strict":true,"agent_id":"copilot","agent_model":"gpt-5-mini"}

[Copilot]

Pull request overview

This PR refreshes the generated pr-sous-chef lock workflow so its metadata hash matches the source markdown workflow again.

Changes:

• Updated the gh-aw frontmatter hash metadata.
• Regenerated deterministic heredoc delimiters and lock-file formatting.
• Preserved the workflow behavior from .github/workflows/pr-sous-chef.md.

Show a summary per file

File	Description
.github/workflows/pr-sous-chef.lock.yml	Regenerated compiled lock artifact for the PR Sous Chef workflow.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0