[Code Quality] Fix gh-aw-detection frontmatter/lock.yml drift causing inconsistent settings within same 24h window #49242

Description

The Detection Analysis Report — 2026-07-30 found that 6 workflows had gh-aw-detection alternating between enabled/disabled across runs within the same 24h window, indicating a .lock.yml recompilation drift (frontmatter edited mid-day, some runs picking up old compiled lockfile) rather than an intentional partial rollout.

Affected Workflows

Suggested Changes

• Recompile each affected workflow once from its current markdown source (gh aw compile) and commit the resulting .lock.yml.
• Confirm subsequent scheduled/dispatched runs consistently pick up the same gh-aw-detection value.
• Consider adding a CI check (or extending the existing lockfile drift check) that fails if a workflow's compiled .lock.yml is stale relative to its markdown source, to prevent recurrence.

Success Criteria

• All 6 workflows show a single consistent gh-aw-detection value across runs in subsequent 24h windows.
• No stale .lock.yml drift detected for these workflows going forward.

Source

Extracted from Detection Analysis Report — 2026-07-30 (discussion #49221)

Priority

Medium - configuration/tooling consistency issue, not blocking but causes noisy audit signal.

🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · auto · 49.2 AIC · ⌖ 7.51 AIC · ⊞ 10.2K · ◷

• expires on Jul 31, 2026, 5:21 PM UTC-08:00