Description
.github/workflows/smoke-aider.md and .github/workflows/smoke-goose.md both explicitly set features: { gh-aw-detection: false }, yet the Detection Analysis Report #50421 flagged both as detection-disabled-high-frequency misconfigurations: Smoke Aider had 5 runs and Smoke Goose had 4 runs in a single 24h window, exceeding the ">3 runs" threshold that should trigger detection per repo convention.
Threat detection (prompt injection / secret leak / malicious-patch scanning) is disabled on both workflows despite them running frequently and exercising live engine/tool integrations, leaving a monitoring gap on two of the most active smoke-test workflows.
Suggested Changes
- In
.github/workflows/smoke-aider.md, change features: { gh-aw-detection: false } to gh-aw-detection: true (or remove the override if true is the default)
- In
.github/workflows/smoke-goose.md, make the same change
- Run
make recompile to regenerate smoke-aider.lock.yml and smoke-goose.lock.yml
- Verify the workflows still run successfully with detection enabled (existing failure clusters for these two engines, e.g. Goose auth errors, are unrelated bugs and out of scope here)
Files Affected
.github/workflows/smoke-aider.md
.github/workflows/smoke-goose.md
.github/workflows/smoke-aider.lock.yml (regenerated)
.github/workflows/smoke-goose.lock.yml (regenerated)
Success Criteria
- Both workflows have
gh-aw-detection: true in their compiled lock files
- Future Detection Analysis Report runs no longer flag these two workflows as
detection-disabled-high-frequency
Source
Extracted from Detection Analysis Report — 2026-08-04 (#50421)
Priority
Medium - Closes a monitoring gap on two frequently-run workflows; low implementation risk (frontmatter-only change).
🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · auto · 85.3 AIC · ⌖ 4.64 AIC · ⊞ 10.3K · ◷
Description
.github/workflows/smoke-aider.mdand.github/workflows/smoke-goose.mdboth explicitly setfeatures: { gh-aw-detection: false }, yet the Detection Analysis Report #50421 flagged both asdetection-disabled-high-frequencymisconfigurations: Smoke Aider had 5 runs and Smoke Goose had 4 runs in a single 24h window, exceeding the ">3 runs" threshold that should trigger detection per repo convention.Threat detection (prompt injection / secret leak / malicious-patch scanning) is disabled on both workflows despite them running frequently and exercising live engine/tool integrations, leaving a monitoring gap on two of the most active smoke-test workflows.
Suggested Changes
.github/workflows/smoke-aider.md, changefeatures: { gh-aw-detection: false }togh-aw-detection: true(or remove the override iftrueis the default).github/workflows/smoke-goose.md, make the same changemake recompileto regeneratesmoke-aider.lock.ymlandsmoke-goose.lock.ymlFiles Affected
.github/workflows/smoke-aider.md.github/workflows/smoke-goose.md.github/workflows/smoke-aider.lock.yml(regenerated).github/workflows/smoke-goose.lock.yml(regenerated)Success Criteria
gh-aw-detection: truein their compiled lock filesdetection-disabled-high-frequencySource
Extracted from Detection Analysis Report — 2026-08-04 (#50421)
Priority
Medium - Closes a monitoring gap on two frequently-run workflows; low implementation risk (frontmatter-only change).