Skip to content

[deep-report] safe_items_count missing from run_summary.json, zeroing out Safe-Output Writes in API Consumption Report #49367

Description

@github-actions

Description

The GitHub API Consumption Report (2026-07-31, discussion #49325) reported Safe-Output Writes as 0 for the day, explicitly noting no safe_items_count was recorded in any of the day's run_summary.json files. Given 144 total runs and 140 with a safe_outputs job (per the Safe Output Health Monitor, discussion #49272), the true count is almost certainly nonzero — the metric is silently dropped rather than genuinely zero.

Expected Impact

Restores a real, trustworthy Safe-Output Writes metric in the daily API Consumption Report instead of a silently-wrong zero, and unblocks any future report that wants to correlate safe-output volume with API/quota consumption.

Suggested Agent

New Agent or whoever owns run_summary.json generation in the safe-outputs actuation step — verify safe_items_count is populated and persisted at job completion.

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport Intelligence Briefing analysis, 2026-07-31 — cross-referenced from GitHub API Consumption Report discussion #49325.

Generated by 🔬 Deep Report · agent · 104.4 AIC · ⌖ 7.71 AIC · ⊞ 10.8K ·

  • expires on Aug 2, 2026, 7:37 AM UTC-08:00

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions