[daily regulatory] Regulatory Report - 2026-03-22 #22317
Closed
Replies: 1 comment
-
|
This report has been superseded by a newer daily regulatory report. |
Beta Was this translation helpful? Give feedback.
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.
-
19 daily reports from 2026-03-22 were reviewed. Overall data quality is high — all key metrics are consistent across reports, with no critical discrepancies. The 177-workflow count is confirmed across 4 independent reports. Two recurring operational issues remain unresolved (EP006 add_comment context mismatch, Day 8 static analysis poutine finding), and one new smoke-test failure (EP022) was introduced today. No secrets exposure, 100% permission coverage, and strong test ratios indicate a healthy codebase posture.
The most actionable finding is the Smoke Update Cross-Repo PR persistent 0% success rate (7+ days), which warrants immediate attention. The 20 stale lock files (needs
make recompile) represent a minor health gap that is easy to resolve. Firewall block-rate differences between the Firewall Report (0.25%) and Observability Report (4.13%) reflect different time windows and workflow scopes — not a data quality issue.📋 Full Regulatory Report
📊 Reports Reviewed
🔍 Data Consistency Analysis
Cross-Report Metrics Comparison
Reference
scratchpad/metrics-glossary.mdfor metric definitions and scopes.open_issues(snapshot)closed_issues(sampled 1000)Scope Notes:
open_issues: Daily Issues collected at 02:08 UTC (98 open), Performance at 19:42 UTC (120 open). With ~70 issues/day activity, a ~22 issue delta over 17 hours is plausible. Not a discrepancy.closed_issues(902 vs 880): Same 22-issue delta explains the difference — consistent.COPILOT_GITHUB_TOKEN; Agent Performance counts workflows configured withengine: copilot. Many Copilot workflows useGITHUB_TOKENinstead ofCOPILOT_GITHUB_TOKEN. Different scopes, not a discrepancy.Consistency Score
Critical Issues
Smoke Update Cross-Repo PR: 0% success, 7+ consecutive days
agent_success_ratefor Smoke Update Cross-Repo PRpr-branchno longer exists ongithubnext/gh-aw-side-repo).pr-branchin the side-repo or update the smoke test to dynamically reset the branch before each run.EP006 Recurring Safe Output Failure: 8th+ occurrence since 2026-02-25
add_commentwithtarget=triggeringfails when triggered byworkflow_dispatch/schedule(no issue/PR context). Recurs in Smoke Multi PR and Agent Container Smoke Test. 8+ occurrences with no fix applied.Warnings
Poutine
untrusted_checkout_exec— Day 8 Unresolvedsmoke-workflow-callandsmoke-workflow-call-with-inputs. First detected 2026-03-15, briefly resolved 2026-03-18, re-emerged 2026-03-19. Now at day 8.20 Stale Lock Files (Needs
make recompile).lock.ymlfiles appeared 2026-03-21 to 2026-03-22, reducing ecosystem health score from 74 to 69/100..mdfiles.EP022: New
push_to_pull_request_branchfailurepr-branchmissing at git fetch phase. 1 occurrence today. Cascaded into 1 cancelledadd_comment.Auto-Triage Blocked: 6 issues inaccessible due to integrity policy
Daily Audit:
push_repo_memoryfalse-positive size error (recurring)Code Quality Score Dip: 73/100 (was 79/100 yesterday)
Data Quality Notes
.ymlfiles); other reports consistently use 177 (.mdagentic workflows only). This is expected.📈 Trend Analysis
Key Trends Observed
Notable Trends
make recompile.📝 Per-Report Analysis
View Per-Report Breakdown
[daily issues] Daily Issues Report — #22225
Source: #22225
Time Period: Snapshot at ~02:08 UTC, last 1000 issues
Quality: ✅ Valid
issues_analyzedopen_issuesclosed_issuesissues_opened_7dissues_without_labelsissues_without_assigneesstale_issuesNotes: High unassigned rate (676/1000) is expected for an AI-driven repo. Average close time of 17.28 hours is excellent.
[daily performance] Daily Performance Summary — #22314
Source: #22314
Time Period: Sample of 100 PRs, 1000 issues, 100 discussions
Quality: ✅ Valid
merged_prsopen_prsDaily Firewall Report — #22216
Source: #22216
Time Period: 7 days (2026-03-15 to 2026-03-22), 20 runs, 12 workflows
Quality: ✅ Valid
workflow_runs_analyzedfirewall_requests_totalfirewall_requests_allowedfirewall_requests_blockedfirewall_domains_blocked[observability] Observability Coverage — #22243
Source: #22243⚠️ 1 firewall telemetry gap)
Time Period: Recent 60 active agent runs (from 398 downloaded)
Quality: ✅ Valid (
firewall_enabled_workflowsSafe Output Health Report — #22230
Source: #22230⚠️ 2 failures
Time Period: Last 24 hours (110 runs downloaded)
Quality:
Daily Audit Report — #22237
Source: #22237⚠️ 5 failures
Time Period: ~24 hours, 39 runs
Quality:
Static Analysis Report — #22240
Source: #22240⚠️ Day 8 critical finding
Time Period: 2026-03-22 snapshot, 177 workflows
Quality:
[daily secrets] Daily Secrets Analysis — #22316
Source: #22316
Time Period: Snapshot, 177 workflow files
Quality: ✅ Valid (first run baseline)
💡 Recommendations
Process Improvements
Resolve Smoke Update Cross-Repo PR (P1): Re-create
pr-branchingithubnext/gh-aw-side-repoor refactor the smoke test to dynamically create/reset the branch. 7+ days of 0% success is a significant coverage gap.Fix EP006 permanently: Add context detection logic to agent prompts for
workflow_dispatch/scheduletriggers to avoid producingadd_commentwithtarget=triggeringwhen no PR/issue context exists.Run
make recompile: 20 stale lock files are degrading the ecosystem health score. This is a simple one-command fix.Unblock Auto-Triage integrity policy: 6 community issues are being blocked from labeling. Review and adjust the integrity policy scope or add a manual fallback triage step.
Data Quality Actions
Fix
push_repo_memorysize measurement bug: The tool is reporting incorrect file sizes (~560 bytes reported as 29 KB). This is a systemic false-positive in the Daily Audit.Investigate Smoke Gemini firewall telemetry gap: Run §23392520645 is missing
access.log. Check if Gemini runs have a different container configuration that omits firewall telemetry.Add
CONTEXT7_API_KEYto redaction list: The secrets report noted this key was partially masked due to the numeric character. Explicitly add it toredact_secrets.cjs.Workflow Suggestions
Poutine
untrusted_checkout_exec: Escalate to a tracked issue with a deadline. Day 8 of an unresolved supply-chain security finding warrants explicit ownership.Code quality score: The 6-point dip (79→73) warrants a one-time docs refresh pass. If the trend continues for 3+ days, investigate what is driving the documentation LOC reduction.
📊 Regulatory Metrics
Report generated automatically by the Daily Regulatory workflow
Run: §23411350181
Data sources: 19 daily report discussions from github/gh-aw (2026-03-22)
Metric definitions: scratchpad/metrics-glossary.md
Previous reports closed: #22190, #22024
Beta Was this translation helpful? Give feedback.
All reactions