[deep-report] Reformat audit-workflows repo-memory JSON files to indent=2 to stop patch-size-triggered reverts

[github-actions]

The 2026-08-09 Agentic Workflow Audit (discussion #51643) reported that its own repo-memory updates to recommendations.json and workflow-trends.json were reverted before push because they pushed the run's total patch over the 50KB hard limit:

Because git diffs are line-based, any edit to these files costs roughly 2× the full file size in patch bytes (whole line removed + whole line re-added) [since they're stored as single-line minified JSON] ... this run's updates to those two files were reverted before push to stay within the limit — their content still reflects the 2026-07-06 snapshot.

Impact

audit-workflows' own tracked recommendations and trend history are stuck on a 34-day-old snapshot and will keep silently failing to update every run until the storage format changes — this directly undermines the audit workflow's own trend-tracking, the same category of "quietly-broken-for-a-long-time" persistence gap flagged elsewhere in this cycle for deep-report and observability logging.

Fix (pick one, per the audit's own recommendation #5)

1. Reformat recommendations.json and workflow-trends.json with indent=2 (pretty-printed) instead of minified single-line JSON — accept a one-time larger diff in exchange for small, surgical diffs on every future edit, or
2. Split workflow-trends.json into smaller per-workflow files so a single edit's diff stays well under the patch-size limit.

Data source

Agentic Workflow Audit Agent report, discussion #51643, 2026-08-09 (Recommendation 5 / "Repo-memory storage format").

Suggested Agent: audit-workflows maintainer or general code-quality agent
Estimated Effort: Quick (< 1 hour)

Generated by 🔬 Deep Report · agent · 237.7 AIC · ⌖ 55.3 AIC · ⊞ 11.3K · ◷

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