prompts/07-commit-and-pr: clarify 14-day cache-memory window is target/best-effort, not guaranteed

Agent-Logs-Url: https://github.com/Hack23/riksdagsmonitor/sessions/e399eab7-ffab-4114-9420-e9640c6eee11

Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>

Author: Copilot

.github/prompts/07-commit-and-pr.md

@@ -54,7 +54,7 @@ Translations for the remaining twelve languages are produced by the dedicated **
 
 ## Cache-memory recovery (resilience for failed PRs)
 
-Every news workflow declares `tools.cache-memory:` keyed by `news-${{ github.workflow }}-${{ inputs.article_date || 'today' }}` with 14-day retention (see `02-mcp-access.md` §Servers & tool naming). gh-aw automatically restores the cache from the **last successfully persisted run** on each invocation. Analysis artifacts under `/tmp/gh-aw/cache-memory/` can therefore be reused on the next attempt when a previous run reached the cache-update stage, but newly generated cache-memory content from an agent job that **fails or times out** is **not** guaranteed to persist for the next retry.
+Every news workflow declares `tools.cache-memory:` keyed by `news-${{ github.workflow }}-${{ inputs.article_date || 'today' }}` with a configured 14-day **target** window (see `02-mcp-access.md` §Servers & tool naming). Treat 14 days as an *intended recovery horizon*, **not** as a strict guarantee that cache-memory will remain available for 14 days: actual availability depends on GitHub Actions cache persistence and eviction policy (best-effort, repo-policy driven), and the 14-day setting primarily affects retained artifacts/related workflow data rather than guaranteeing cache retention. gh-aw automatically attempts to restore cache-memory from the **last successfully persisted run** on each invocation. Analysis artifacts under `/tmp/gh-aw/cache-memory/` can therefore often be reused on the next attempt when a previous run reached the cache-update stage, but newly generated cache-memory content from an agent job that **fails or times out** is **not** guaranteed to persist for the next retry.
 
 **On every run, immediately after MCP pre-warm:**