[cache-strategy] Cache Strategy Analysis - 2026-08-28

[github-actions[bot]]

Cache Strategy Analysis Report

Date: 2026-08-28
Runs Analyzed: 86
Workflows with cache-memory: 70

---

Executive Summary

The last 24 hours contained 86 agentic workflow runs that declared cache-memory, spanning 70 distinct workflows. Four workflows stood out as repeat cache failures with 100% miss rates over the currently retained 14-day sample: Daily Go Test Parallelizer, Deep Report, Refactoring Cadence, and Copilot Session Insights.

The highest-cost offender is Daily Go Test Parallelizer, which accumulated 1,030,663 rebuild-excess tokens while never materializing the required state.json file. Deep Report is a separate class of problem: it enables cache-memory but never uses it in the prompt body, so the workflow pays setup overhead without any possible reuse.

No consistently healthy cache-memory workflow was confirmed in this run. Daily SPDD Spec Planner is the only workflow with a visible cache-specific directory in persistent storage, but no durable hit signal was available to classify it as healthy.

---

Findings

Severity	Workflow	Miss Streak	Miss Rate (14d)	Root Cause	Issue
🟠	Daily Go Test Parallelizer	2 days	100%	Required cache state is never persisted	#56715
🟠	Deep Report	2 days	100%	Declares cache-memory but never uses it	#56717
🟠	Refactoring Cadence	2 days	100%	Required baseline file is never persisted	#56718
🟠	Copilot Session Insights	2 days	100%	Session-analysis history never materializes	#56719
🟡	The Daily Repository Chronicle	1 day	50%	Declares cache-memory but never uses it	n/a
🟡	Daily Documentation Updater	1 day	50%	Declares cache-memory but never uses it	n/a
🟡	Daily News	1 day	50%	Declares cache-memory but never uses it	n/a

🟠 High Priority

Workflow	Evidence
Daily Go Test Parallelizer	Prompt requires reading and always writing /tmp/gh-aw/cache-memory/go-test-parallelizer/state.json, but the file is absent after 9 runs across 2026-08-27 and 2026-08-28.
Deep Report	7 observed runs still execute cache-memory setup/update steps even though the prompt body never references cache-memory outside the shared system block.
Refactoring Cadence	Prompt requires creating /tmp/gh-aw/cache-memory/refactoring-cadence/baseline.json, but the file is absent after the observed runs.
Copilot Session Insights	Prompt requires initializing /tmp/gh-aw/cache-memory/session-analysis/history.json, but no session-analysis/ directory exists in persistent cache memory.

🟡 Medium Priority

Workflow	Evidence
The Daily Repository Chronicle	Single observed run had 720,297 rebuild-excess tokens and no workflow-specific cache-memory instructions.
Daily Documentation Updater	Single observed run had 48,927 rebuild-excess tokens and no workflow-specific cache-memory instructions.
Daily News	Single observed run had 28,589 rebuild-excess tokens and no workflow-specific cache-memory instructions.

---

Healthy Workflows

No workflow met the bar for a confirmed cache hit with durable state visible in persistent cache memory during this analysis window.

---

Issues Created Today

• #56715 [cache-strategy] Fix cache miss in Daily Go Test Parallelizer
• #56717 [cache-strategy] Fix cache miss in Deep Report
• #56718 [cache-strategy] Fix cache miss in Refactoring Cadence
• #56719 [cache-strategy] Fix cache miss in Copilot Session Insights

💾 Cache Memory Summary

• Total workflows tracked: 72
• Runs recorded (last 30d): 162
• Cache memory location: /tmp/gh-aw/cache-memory/cache-strategy/
• Next pruning date: 2026-09-27
• Dedupe note: GitHub read authentication failed in this runner, so duplicate suppression relied on known-issues.json, which was empty at startup.

---

Report generated by the Daily Cache Strategy Analyzer

Generated by 📊 Daily Cache Strategy Analyzer · codex · gpt54 · 164.1 AIC · ⌖ 7.9 AIC · ⊞ 13.2K · ◷

• expires on Aug 29, 2026, 1:56 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Daily Cache Strategy Analyzer.

A newer discussion is available at Discussion #56950.