[detection-analysis] Detection Analysis Report — 2026-11-03

[github-actions[bot]]

Summary

• Window evaluated: last 24 full hours ending at workflow start (UTC) — 2026-11-02T23:11:33Z to 2026-11-03T23:11:33Z
• Coverage achieved: 2026-11-03T03:15:50Z to 2026-11-03T23:11:33Z (~20h of the 24h window). Collection hit the 1 GB storage budget while paging further back; the earliest ~4 hours of the window (2026-11-02T23:11:33Z–2026-11-03T03:15:50Z) were not collected. All figures below reflect the 656 runs that were analyzed, not the full 24h.
• Total runs analyzed: 656
• Detection-enabled runs: 655 (99.8%)
• Regular runs (gh-aw-detection: false): 1 (0.2%)
• Misconfigured workflows found: 0

Note

No misconfigured workflows were detected in the analyzed window. gh-aw-detection is disabled on only a single run (one workflow, one occurrence), below the >3-run threshold for flagging, and the detection job itself never failed in any of the 631 runs where it executed.

Comparison Chart

Metric	Regular (n=1)	Detection (n=655)
Success rate	100.0%	81.4%
Failure count	0	121
Avg tokens/run	9,673	296,183

Misconfigured Workflows

No misconfigured workflows detected in this window.

View All Run Metrics

148 distinct workflows observed. Top 25 by run count (Total / Detection-enabled / Regular / Success rate / Avg tokens):

Workflow	Total	Detection	Regular	Success %	Avg Tokens
PR Finisher	117	117	0	72.2	15,359
PR Sous Chef	97	97	0	70.8	5,005
Design Decision Gate 🏗️	45	45	0	97.8	30,865
Test Quality Sentinel	45	45	0	97.8	14,844
Ponytail Reviewer	44	44	0	97.7	530,532
Matt Pocock Skills Reviewer	43	43	0	88.4	69,980
PR Code Quality Reviewer	41	41	0	92.7	16,331
Issue Monster	23	23	0	95.7	95,694
AI Moderator	15	15	0	100.0	1,020
Daily Go Test Parallelizer	11	11	0	63.6	8,227,393
Avenger	7	7	0	85.7	2,186,810
Visual Regression Checker	7	7	0	0.0	20,034
Smoke Claude Dynamic Workflow	5	5	0	40.0	1,871
Contribution Check	5	5	0	80.0	27,573
[aw] Failure Investigator (6h)	4	4	0	100.0	434
Auto-Triage Issues	4	4	0	100.0	329,832
Code Scanning Fixer	3	3	0	0.0	18,296
GitHub MCP Structural Analysis	2	2	0	100.0	25,474
Daily Safe Outputs Conformance Checker	2	2	0	50.0	45,167
Agent Persona Explorer	2	2	0	100.0	42,516
PR Triage Agent	2	2	0	100.0	73,318
Constraint Solving — Problem of the Day	2	2	0	100.0	138,418
Typist - Go Type Analysis	2	2	0	100.0	77,688
Daily Safe Output Tool Optimizer	2	2	0	100.0	53,702
Go Logger Enhancement	2	2	0	100.0	19,092

The remaining 123 workflows each had 1 run in the analyzed window, including the single regular run: Daily GitHub Docs SEO Optimizer (gh-aw-detection: false, 1 run, success).

Notable non-detection failure clusters worth separate follow-up (not detection misconfigurations — the detection job was not implicated in any of them): PR Finisher (driver-exit failures, ~72% success), Visual Regression Checker (0% success, 7 runs), Daily BYOK Ollama Test, Code Scanning Fixer, and Daily Work Queue Formal Verification.

View Historical Trend

Trending history now holds 35 records across 34 distinct UTC days (2026-08-25 to 2026-11-03); 90-day retention dropped nothing this run.

Recommendations

1. No detection misconfigurations to fix right now. The gh-aw-detection feature is enabled (explicitly or by default) on 99.8% of observed runs, and its detection job has a clean track record (0 failures across 631 executions) — the feature itself is not contributing to the ~18.6% overall failure rate seen on detection-enabled runs.
2. Re-run this analysis for the missed ~4h window (2026-11-02T23:11:33Z–2026-11-03T03:15:50Z) once storage budget allows, to confirm no misconfigurations were missed outside the collected ~20h.
3. Investigate non-detection failure clusters separately — PR Finisher's recurring driver_exit failures and Visual Regression Checker's 0% success rate are the two biggest reliability gaps in this window and warrant their own triage (outside this report's detection-specific scope).
4. Confirm intent behind the single gh-aw-detection: false run on Daily GitHub Docs SEO Optimizer — if this was a one-off manual override rather than a persistent setting, no action is needed; if it's meant to be permanent, document the rationale in the workflow's frontmatter comments.

References:

• §41735653285 — PR Finisher, example driver-exit failure cluster
• §41671278128 — Visual Regression Checker, example failing run
• §41579970257 — Daily GitHub Docs SEO Optimizer, the one gh-aw-detection: false run observed

Generated by 🔎 Detection Analysis Report · claude · agent · ~98 AIC · ⌖ ~1 AIC · ⊞ 4.5K · ◷

• expires on Nov 6, 2026, 3:33 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Detection Analysis Report.

A newer discussion is available at Discussion #74989.

[github-actions[bot]]

Caveman smoke test here. Fire good. Me run, me happy. 🦴🔥

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

• host.docker.internal
• update.googleapis.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "host.docker.internal"
    - "update.googleapis.com"

See Network Configuration for more information.

📰 BREAKING: Report filed by Smoke Copilot · copilot · auto · ~34 AIC · ⌖ ~1 AIC · ⊞ 8.2K · ◷
_{Comment /smoke-copilot to run again
Add label smoke to run again}