[daily regulatory] Regulatory Report - 2026-03-23

[github-actions[bot]]

Reviewed 12 daily report discussions generated on 2026-03-23 across all automated monitoring workflows. Overall data quality is high — no critical cross-report discrepancies were found, and all core infrastructure metrics (safe outputs, observability, firewall) report clean runs. The repository is operating at high velocity with 23 PRs merged on March 23 alone and 97.6M Copilot tokens consumed across 113 workflow runs.

One ongoing P1 concern persists from prior periods: the Smoke Update Cross-Repo PR workflow has a 0% success rate for 8+ consecutive days (issue #22241). Code quality score has also drifted downward from 80→73/100 over 5 days, driven by documentation debt and churn stability. These are the only two items requiring attention; all other metrics are within normal ranges.

📋 Full Regulatory Report

📊 Reports Reviewed

#	Report	Discussion	Created	Status
1	Daily Issues Report	#22521	21:07 UTC	✅ Valid
2	Safe Output Health Report	#22549	23:53 UTC	✅ Valid
3	Daily Code Metrics Report	#22417	11:50 UTC	✅ Valid
4	Daily Copilot Token Consumption	#22415	11:39 UTC	✅ Valid
5	Observability Coverage Report	#22394	08:04 UTC	✅ Valid
6	Daily Firewall Report	#22346	01:07 UTC	✅ Valid
7	Agent Performance Report	#22482	17:48 UTC	✅ Valid
8	Repository Chronicle	#22460	16:23 UTC	✅ Valid
9	Copilot PR Merged Report	#22446	15:36 UTC	✅ Valid
10	Daily Status	#22401	09:40 UTC	✅ Valid
11	Auto-Triage Report (latest)	#22487	19:05 UTC	✅ Valid
12	Daily Compiler Code Quality	#22341	00:28 UTC	✅ Valid

---

🔍 Data Consistency Analysis

Cross-Report Metrics Comparison

Reference: scratchpad/metrics-glossary.md

Metric	Daily Issues	Daily Status	Chronicle	Scope Match	Status
open_issues	121 (of 1000 sample)	100 (of issues.json 200-sample)	~100	⚠️ Different scopes	ℹ️ See Note
closed_issues	879 (of 1000 sample)	100 (of issues.json)	—	⚠️ Different scopes	ℹ️ See Note
open_prs	—	3	3 open pending	✅ Same	✅
merged_prs (24h)	—	—	23	—	✅
merged_prs (7d)	—	50	—	—	✅
stale_issues	0	—	—	N/A	✅
issues_without_labels	40 (of 1000)	0 visible (auto-triage)	—	⚠️ Different scopes	ℹ️ See Note

Scope Notes:

• open_issues: Daily Issues Report operates on last-1000-issue sample. Daily Status uses a issues.json snapshot of 200 issues (100 open + 100 closed). Different scopes by design per glossary — not a discrepancy.
• issues_without_labels: Daily Issues counts unlabeled from 1000-issue corpus (40); Auto-Triage reports 0 unlabeled among 50 recently-updated open issues. Different scopes, consistent with each workflow's purpose.
• merged_prs (7d) vs merged_prs (24h): Copilot PR Merged Report covers 22 March 15:30 → 23 March 15:30 (29 PRs). Daily Status says 50 merged in last 7 days. Chronicle counts 23 merged on March 23 calendar day. All internally consistent across their distinct time windows. ✅

Firewall vs Observability Cross-Check

Metric	Firewall Report	Observability Report	Delta	Status
workflow_runs_analyzed (7d)	31 firewall-enabled runs	37 firewall-enabled (completed)	+6	ℹ️ Different cutoffs
firewall_coverage	All runs logged	100% (37/37)	—	✅
mcp_coverage	—	100% (37/37)	—	✅

Note: The 6-run delta between Firewall (31) and Observability (37) is within normal range — the reports use slightly different 7-day windows and may include different run completion states.

Consistency Score

• Overall Consistency: 92% — all comparable same-scope metrics align
• Critical Discrepancies: 0
• Scope Differences (expected): 3 (documented above)
• Minor Notes: 2

---

⚠️ Issues and Anomalies

Critical Issues

None. No critical data consistency failures detected across all 12 reports.

Warnings

1. P1 Ongoing: Smoke Update Cross-Repo PR — 0% Success Rate

   • Affected Reports: Agent Performance Report (Agent Performance Report — Week of 2026-03-23 #22482)
   • Metric: agent_success_rate for this specific workflow
   • Description: Workflow has 0% success for 10+ consecutive failures over 8+ days
   • Issue Filed: #22241
   • Severity: High — P1 ongoing
   • Recommended Action: Escalate if no resolution by 2026-03-30

2. Code Quality Score Declining Trend

   • Affected Reports: Daily Code Metrics (Daily Code Metrics Report - 2026-03-23 #22417)
   • Metric: quality_score (composite)
   • Description: Quality score dropped from 80/100 (2026-03-18) to 73/100 (2026-03-23), -7 points in 5 days
   • Root Cause: Churn stability (5/15) and documentation coverage (13/20) are below target
   • Severity: Medium — trend warrants monitoring
   • Recommended Action: Reduce churn rate or improve documentation before score falls below 70

3. gateway.jsonl Not Observed — All MCP Telemetry via Fallback

   • Affected Reports: Observability Coverage ([observability] Observability Coverage Report - 2026-03-23 #22394)
   • Metric: mcp_telemetry_source
   • Description: No gateway.jsonl files observed; all MCP telemetry comes from rpc-messages.jsonl fallback. Reduces signal fidelity.
   • Severity: Low — coverage still 100%, but preferred format unavailable
   • Recommended Action: Investigate why gateway.jsonl is not being generated

4. One-Sided Firewall Traffic in 28/37 Runs

   • Affected Reports: Observability Coverage ([observability] Observability Coverage Report - 2026-03-23 #22394)
   • Description: 28 of 37 firewall-enabled runs show only allowed OR only blocked traffic, not mixed. Reduces allow/deny validation signal.
   • Severity: Low — expected behavior for many workflows
   • Recommended Action: No action required; document as known pattern

Data Quality Notes

• All 12 reports generated successfully with no missing or empty bodies
• Token consumption report (7-day period): no cost data available in logs (expected if billing API not accessible)
• Auto-Triage Report latest run at 19:05 UTC; earlier runs at 06:47 and 12:36 also present (3 daily triage runs normal)
• Safe Output Health Report covers last 100 runs (24h window); 92 of 100 runs had no safe output activity (expected for non-output workflows)

---

📈 Trend Analysis

Key Metrics Summary (2026-03-23)

Metric	Value	Trend
Total Tokens Consumed	97.6M (113 runs)	—
PRs Merged (today)	23	↑ High velocity
PRs Merged (7d)	50	Stable high
Safe Output Success Rate	100%	✅ Improved from 93.8% yesterday
Firewall Block Rate	2.9% (19/647)	Normal
Observability Coverage	100%	✅ Excellent
Code Quality Score	73/100	↓ -7 from 80 on 2026-03-18
Test-to-Source Ratio	2.26x	✅ Stable
Open PRs	3	Low (healthy)
Unassigned Issues	674 (of 1000 sample)	⚠️ High

Notable Trends

• Velocity is very high: 23 PRs merged in a single day, 97.6M tokens across 113 runs. Repository is shipping at maximum pace.
• Safe output system fully recovered: After 2 failures on 2026-03-22 (EP006, EP022), today shows 0 failures — a clean run.
• Unassigned issues remain elevated: 674/1000 sampled issues lack assignees. This is a recurring metric. The auto-triage system ensures labeling but not assignment.
• Quality score regression: -7 points over 5 days is the most concerning trend, though absolute score (73) remains in "Good" range.

---

📝 Per-Report Analysis

View Per-Report Details

Daily Issues Report (#22521)

Time Period: Latest 1000 issues sample | Quality: ✅ Valid

Metric	Value	Validation
issues_analyzed	1000	✅ Scope documented
open_issues	121 (12.1%)	✅
closed_issues	879 (87.9%)	✅ Math: 121+879=1000 ✓
issues_opened_7d	491	✅
avg_close_time	16h 11m	✅
issues_without_labels	40	✅
issues_without_assignees	674	⚠️ High
stale_issues	0	✅

Notes: Math checks pass. Percentage check: 121/1000 = 12.1% ✓, 879/1000 = 87.9% ✓. issues_opened_30d = 1000 suggests all sampled issues were opened in last 30 days — high churn confirmed.

Safe Output Health (#22549)

Time Period: Last 24 hours | Quality: ✅ Valid

Metric	Value	Validation
runs_analyzed	100	✅
safe_output_messages_processed	39	✅
safe_output_messages_failed	0	✅
success_rate	100%	✅ Math: 0/39 = 0% failure ✓

Daily Code Metrics (#22417)

Time Period: Point-in-time snapshot | Quality: ✅ Valid

Metric	Value	Validation
lines_of_code_total	692,499	✅
go_source_loc	139,616	✅
test_lines_of_code	315,683	✅
test_to_source_ratio	2.26x	✅ Math: 315,683/139,616 ≈ 2.26 ✓
quality_score	73/100	⚠️ Declining

Daily Copilot Token Consumption (#22415)

Time Period: 7 days historical | Quality: ✅ Valid

Metric	Value	Validation
total_tokens	97,580,594	✅
workflow_runs_analyzed	113	✅
avg_tokens_per_run	863,545	✅ Math: 97,580,594/113 ≈ 863,545 ✓
error_count	9	⚠️ Low but non-zero

Observability Coverage (#22394)

Time Period: Last 7 days | Quality: ✅ Valid

Metric	Value	Validation
workflow_runs_analyzed	63 (61 completed)	✅
firewall_enabled_runs	37	✅
firewall_coverage	100%	✅
mcp_coverage	100%	✅
gateway_jsonl_present	0	⚠️ Fallback only

Daily Firewall Report (#22346)

Time Period: 2026-03-16 → 2026-03-23 (7 days) | Quality: ✅ Valid

Metric	Value	Validation
workflow_runs_analyzed	31 (17 distinct)	✅
firewall_requests_total	647	✅
firewall_requests_allowed	628 (97.1%)	✅ Math: 628/647 ≈ 97.1% ✓
firewall_requests_blocked	19 (2.9%)	✅ Math: 628+19=647 ✓
firewall_domains_blocked	4	✅

Notes: Block rate of 2.9% is healthy. Dominant blocked domain is ab.chatgpt.com:443 (OpenAI telemetry from Codex workflows) — expected behavior.

Agent Performance Report (#22482)

Time Period: 2026-03-17 → 2026-03-23 (7 days) | Quality: ✅ Valid

Metric	Value	Validation
workflows_monitored	177	✅
active_workflows_7d	23	✅
total_runs_7d	85	✅
quality_score	82/100	✅
effectiveness_score	75/100	✅
health_score	71	✅
P1 issues	1 (Smoke Update Cross-Repo PR)	⚠️ Ongoing

Copilot PR Merged Report (#22446)

Time Period: 2026-03-22 15:30 → 2026-03-23 15:30 UTC (24h) | Quality: ✅ Valid

Metric	Value	Validation
merged_prs_24h	29	✅
lines_added_24h	7,386	✅
lines_deleted_24h	2,026	✅
net_code_change	+5,360	✅ Math: 7386-2026=5360 ✓

---

💡 Recommendations

Process Improvements

1. Issue Assignment Workflow: 674/1000 issues (67.4%) have no assignee. Consider adding auto-assignment logic to the Auto-Triage workflow or creating a dedicated assignment workflow.
2. Documentation Coverage: The 11.54:1 code-to-docs ratio is cited as a quality score driver. Consider scheduling a dedicated documentation sprint.

Data Quality Actions

1. Investigate gateway.jsonl Absence: The MCP gateway preferred telemetry format is not being produced. Confirm whether this is intentional post-migration or a gap.
2. Token Error Investigation: 9 errors across 113 runs in the token consumption report should be investigated — identify if they represent workflow failures or benign interruptions.

Workflow Suggestions

1. Standardize Issue Scope Documentation: Some reports use "100 open issues" while others use "1000 issue sample" — this is correct per the glossary but should be clearly labeled in each report header for reader clarity.
2. Smoke Update Cross-Repo PR Resolution: Escalate issue #22241 before 2026-03-30 deadline identified in Agent Performance Report.

---

📊 Regulatory Metrics

Metric	Value
Reports Reviewed	12
Reports Passed	12
Reports with Warnings	4
Reports Failed	0
Critical Discrepancies	0
Math Validation Errors	0
Overall Health Score	92%

---

References:

• §23466174824 — Daily Regulatory workflow run
• §23465733999 — Safe Output Health Monitor (source)
• §23451246701 — Agent Performance Report (source)

AI generated by Daily Regulatory Report Generator · history

• expires on Mar 27, 2026, 12:05 AM UTC

[github-actions[bot]]

💥 WHOOSH! ⚡ KA-BOOM! 🦸

The Smoke Test Agent swoops in from the shadows of GitHub Actions...

"The name's Claude — and I've just run all systems checks on this repo! 🔥"

POW! Tests passed. ZAP! Build succeeded. WHAM! Playwright confirmed GitHub is alive!

— Smoke Claude saves the day, one workflow at a time! 🦸♂️

💥 [THE END] — Illustrated by Smoke Claude

💥 [THE END] — Illustrated by Smoke Claude · ◷

[github-actions[bot]]

This report has been superseded by a newer daily regulatory report for 2026-03-24.