Skip to content

[deep-report] Populate SafeItemsCount in run_summary.json so audits stop reporting 0 safe-output writes #46268

Description

@github-actions

Description

The [api-consumption] report (discussion #46226) found run_summary.json's authoritative SafeItemsCount field is unpopulated (returns 0) across every run in the current CLI version — the same gap that forced the 07-15 and 07-16 history entries to 0. Audits now fall back to summary.json -> safe_outputs.total_items. Fix the run-summary writer to populate SafeItemsCount from actuated safe-output items so downstream audits report accurate write counts directly.

Expected Impact

Restores accurate safe-output write metrics across multiple daily audits (API Consumption, Safe Output Health) without brittle fallbacks; improves historical trend fidelity.

Suggested Agent

Copilot SWE Agent (Go, gh-aw logs/reporting internals).

Estimated Effort

Medium (1-4 hours).

Data Source

DeepReport 2026-07-17 - [api-consumption] discussion #46226. Distinct from the closed token-total gap #45511; dedup-checked: no open issue covers SafeItemsCount.

Generated by 🔬 Deep Report · 208.7 AIC · ⌖ 11.4 AIC · ⊞ 10K ·

  • expires on Jul 19, 2026, 7:16 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