[cache-strategy] Fix cache miss in Refactoring Cadence

[github-actions]

Cache Strategy Problem: Refactoring Cadence

Severity: 🟠 High

Workflow: Refactoring Cadence
Analysis Date: 2026-08-28
Issue Type: Cache miss

---

Problem Description

The prompt requires the workflow to read and then recreate /tmp/gh-aw/cache-memory/refactoring-cadence/baseline.json, but the baseline file is still absent after the observed runs on 2026-08-27 and 2026-08-28. That prevents the workflow from carrying its baseline forward and turns the cache into a recurring miss.

Evidence

• Miss streak: 2 consecutive analyzed days
• Miss rate (14d): 100%
• Last cache hit: never
• Observed runs: 2
• Rebuild excess tokens (14d): 392,792
• Log signals: Prompt includes cat /tmp/gh-aw/cache-memory/refactoring-cadence/baseline.json and later mkdir -p /tmp/gh-aw/cache-memory/refactoring-cadence/ followed by writing baseline.json, but the file is missing in persistent cache memory after the runs.

Recommended Fix

1. Make baseline persistence mandatory by failing the run when baseline.json was supposed to be written but is absent before cache upload.
2. Write the baseline through an atomic temp-file move so partial failures do not silently leave the cache empty.
3. Emit a clear cache status line indicating whether the baseline was restored or newly initialized.

Expected Impact

If fixed, the workflow can compare against a real prior baseline instead of rebuilding its starting point from scratch on every run.

---

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