[deep-report] Add gh-aw-detection: true to Q and ESLint Monster workflows

[github-actions]

Today's Detection Analysis Report (2026-08-09→10, discussion #51652) flagged 2 workflows as misconfigured under Rule 1 (no gh-aw-detection feature configured at all despite running frequently):

Workflow	Runs (7d)	File
Q	5	.github/workflows/q.md
ESLint Monster	7	.github/workflows/eslint-monster.md

Fix

Add to each workflow's frontmatter:

features:
  gh-aw-detection: true

then recompile (gh aw compile) to regenerate the .lock.yml files.

Why it matters

gh-aw-detection is the fleet's prompt-injection/threat-detection layer. Detection-enabled runs in this same report showed a 90.9% success rate vs. 25.0% for non-detection runs (though that gap is mostly explained by action_required gate blocks, not detection itself) — the broader pattern across the fleet is that workflows named/behaving like analyzers, reviewers, or monitors are expected to have this enabled, and these two are the only 2 exceptions found in the sampled window.

Data source

Detection Analysis Report, discussion #51652, 2026-08-10.

Suggested Agent: New Agent or general code-quality agent
Estimated Effort: Fast (< 30 min)

Generated by 🔬 Deep Report · agent · 237.7 AIC · ⌖ 55.3 AIC · ⊞ 11.3K · ◷

• expires on Aug 12, 2026, 7:12 AM UTC-08:00