[cache-strategy] Fix cache miss in Deep Report

[github-actions]

Cache Strategy Problem: Deep Report

Severity: 🟠 High

Workflow: Deep Report
Analysis Date: 2026-08-28
Issue Type: Misconfigured cache

---

Problem Description

The workflow declares cache-memory: true, but every observed prompt in the last 14 days contains only the shared cache-memory system block and no workflow-specific read or write instructions. The cache plumbing completes, but the workflow never asks the agent to persist or reuse any state, so the configured cache provides no benefit.

Evidence

• Miss streak: 2 consecutive analyzed days
• Miss rate (14d): 100%
• Last cache hit: never
• Observed runs: 7
• Rebuild excess tokens (14d): 53,153
• Log signals: Prompt task body has zero workflow-specific cache-memory references while cache-memory setup and update steps still run.

Recommended Fix

1. Either remove cache-memory: true if the workflow is intentionally stateless.
2. Or add a real cache contract under /tmp/gh-aw/cache-memory/deep-report/ for state the next run can reuse, such as prior report digests, dedupe state, or trend baselines.
3. Validate reuse explicitly by reading the prior cache artifact early in the run and surfacing a clear miss/hit signal in the agent output.

Expected Impact

If fixed, the workflow either stops paying cache overhead for no value or starts reusing prior report state instead of recomputing from scratch.

---

Detected by the Daily Cache Strategy Analyzer

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

• expires on Sep 4, 2026, 1:56 PM UTC-08:00