[cache-strategy] Fix cache miss in Q

[github-actions]

Cache Strategy Problem: Q

Severity: High

Workflow: Q
Analysis Date: 2026-04-25
Issue Type: Cache miss / missing persisted state

Problem Description

Q declared and ran cache-memory handling, but the analyzed runs show repeated cache restore misses with no observed cache hit. The latest run also did not leave a cache artifact or saved cache signal, so the next run is likely to start cold again and repeat log analysis work.

Evidence

• Miss streak: 1 day with repeated misses in the analyzed window
• Miss rate (14d): 100%
• Runs observed: 3
• Last cache hit: never observed
• Latest run: §24929839999
• Log signals: Cache not found for input keys: memory-none-9f0b69b3-q-24929839999, memory-none-9f0b69b3-q-

View Observed Q Runs

Run	Cache Hit	Cache Miss	Signals
§24920151268	false	true	cache_miss, run_id_in_cache_key, no_cache_artifact
§24928863169	false	true	cache_miss, run_id_in_cache_key, no_cache_artifact
§24929839999	false	true	cache_miss, run_id_in_cache_key, no_cache_artifact

Recommended Fix

1. Persist meaningful state — Ensure Q writes structured data to /tmp/gh-aw/cache-memory/q/ or another workflow-specific path before the cache update job runs.
2. Verify cache save path — Confirm the cache-memory update job sees non-empty content and saves it under the expected memory-none-...-q-* key namespace.
3. Add a restore check — At startup, log whether prior cache state was restored and how many records were loaded so future runs can distinguish first-run behavior from a broken cache.

Expected Impact

If fixed, Q should avoid re-scanning the same recent workflow logs on future runs and can reuse historical findings to reduce agent time and token usage.

References

• §24929839999
• §24928863169
• §24920151268

Warning

Firewall blocked 4 domains

The following domains were blocked by the firewall during workflow execution:

• ab.chatgpt.com
• api.github.com
• chatgpt.com
• github.com

💡 Tip: api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "ab.chatgpt.com"
    - "api.github.com"
    - "chatgpt.com"
    - "github.com"

See Network Configuration for more information.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #17243 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Daily Cache Strategy Analyzer · ◷

• expires on May 2, 2026, 1:22 PM UTC