[Code Quality] Enable gh-aw-detection on 7 high-frequency workflows lacking anomaly/prompt-injection detection

[github-actions]

Description

The Detection Analysis Report - 2026-07-29 flagged 7 high-frequency workflows (>10 runs in the sampled 24h window, proxy for the 7-day rule) that do not have gh-aw-detection: true set in their frontmatter, leaving them without anomaly/prompt-injection detection coverage.

Affected Workflows

Workflow	Run Count (24h)
PR Sous Chef	21
Matt Pocock Skills Reviewer	20
Impeccable Skills Reviewer	18
PR Code Quality Reviewer	17
Design Decision Gate	17
Issue Monster	11
PR Description Updater	6

Suggested Changes

• Add gh-aw-detection: true to the frontmatter of each workflow's markdown source under .github/workflows/
• Recompile with gh aw compile to regenerate the corresponding .lock.yml files
• Verify the workflows still pass make recompile / actionlint checks after the change

Success Criteria

• All 7 listed workflows have gh-aw-detection: true in frontmatter
• Corresponding .lock.yml files are regenerated and committed
• No regressions in workflow validation (make recompile, actionlint)

Source

Extracted from Detection Analysis Report — 2026-07-29 (discussion #49009)

Priority

Medium - Improves security observability coverage across high-traffic automation workflows, not blocking.

🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · aut00 · 53.4 AIC · ⌖ 7.34 AIC · ⊞ 10.2K · ◷

• expires on Jul 30, 2026, 5:15 PM UTC-08:00