[cache-strategy] Fix cache miss in Linter Miner #52134

Cache Strategy Problem: Linter Miner

Severity: 🟡 Medium

Workflow: Linter Miner
Analysis Date: 2026-08-11
Issue Type: Cache miss

Problem Description

Linter Miner reads prior state from /tmp/gh-aw/cache-memory at startup, but it only appends the new proposed-linters entry after the full mining, implementation, and PR steps finish. The 2026-08-11 run 31518785706 failed after 12 turns and 89,698 tokens, so none of that mined state was checkpointed.

That means the next run will redo the expensive discussion mining and code-pattern scanning from scratch instead of resuming from the partial results it already paid for.

Evidence

• Miss streak: 1 run observed in the last 24h
• Miss rate (14d): 100% of observed cache-memory runs for this workflow today
• Last cache hit: never observed in the available history
• Log signals: Create cache-memory directory / Restore cache-memory file share data / Commit cache-memory changes were present, but the run still ended in failure before any durable proposed-linters checkpoint was created

Recommended Fix

1. Checkpoint the mined candidates before implementation - Persist the merged candidate list or selected linter name immediately after Step 3, not only after Step 6. That preserves the expensive discovery work even if code generation or PR creation fails.
2. Split draft and final state - Store draft candidates separately from the final proposed-linters append so a failed PR does not force a full re-scan next run.
3. Make writes incremental - Append state after each expensive phase instead of waiting for the workflow to finish cleanly.

Expected Impact

If fixed, this workflow should avoid repeating the same expensive mining work after a failure, reducing token spend and making subsequent runs resume from the last completed stage instead of starting over.

Detected by the Daily Cache Strategy Analyzer

Generated by 📊 Daily Cache Strategy Analyzer · gpt54mini · 43 AIC · ⌖ 1.45 AIC · ⊞ 12.2K · ◷

• expires on Aug 18, 2026, 10:58 AM UTC-08:00