Repository navigation
[detection-analysis] Detection Analysis Report — Last 24h (2026-10-09) #67301
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-12T23:37:12.337Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
run.jsonwith noaw_info.json/run_summary.json— see caveat below)gh-aw-detection: false): 0 (0%)Note
No misconfigured workflows were detected in this window. No workflow in the fully-logged dataset explicitly disables
gh-aw-detection, nodetectionjob showed a failing conclusion, and no workflow alternated its detection setting across runs.Comparison Chart
Because zero runs explicitly opted out of detection in this window, the "Regular Runs" bar is empty (0 runs, 0% success rate by convention) — all activity in this window ran with detection enabled (either explicitly
trueor, more commonly, left absent/default).Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
Top workflows by run count in this window (all classified as Detection, since none set
gh-aw-detection: false):Highest single-run token usage:
PR Code Quality Reviewerrun §37996967566 at 2,219,240 tokens.Data gap caveat: 111 of 263 run directories in
/tmp/gh-aw/aw-mcp/logs/contained only a barerun.json(noaw_info.json, norun_summary.json, no job/step data), so detection status and token usage could not be determined for them. Of these, 64 concludedsuccess, 40failure, and 7 had no conclusion recorded. The largest contributors wereDaily Trajectory Grader Implementer(16),[aw] Failure Investigator (6h)(15),PR Sous Chef(14), andAI Moderator(12). This looks like an incomplete log-download for those runs rather than agh-aw-detectionmisconfiguration — theagent/detectionjobs never materialized in the downloaded data, so Rule 2 (detection job failure) could not be evaluated for them. Flagging as a log-pipeline gap, not a detection misconfiguration.View Historical Trend
14 days of history now recorded in cache-memory trending store. Detection-run volume has varied widely day to day (152–431 runs), and detection success rate has ranged from ~35% to ~94%, with no sustained trend toward regular (opt-out) usage — it has stayed near 0 on most days.
Recommendations
gh-aw-detectionfeature is effectively universal across active workflows (0 opt-outs observed), so there is no regular-vs-detection drift to correct.aw_info.json/run_summary.json. If this recurs, it limits future misconfiguration detection (rules 2 and 3 can't be evaluated withoutjob_details). Example incomplete run: §37952640103 (Avenger).Daily Formal Spec Verifier, also 0% in this window).References:
PR Code Quality Reviewer, detection-enabled exampleAll reactions