pr-descriptionlisted

# PR description Two audiences share one body. The bullets are for a human deciding whether to review this; the dropdown is for the agent that has to understand it. Keep them apart. ## Format ```markdown [AI-generated] ### Summary (for humans) #### Problem - Cache key omits the region, so us-east reads hit eu-west entries - Stale entries survive deploys because the TTL is never refreshed #### Fix - Add region to the cache key - Reset the TTL on every write ### Extra context (for clankers) <details> <summary>Details</summary> Everything you would normally put in a PR description: reasoning, alternatives rejected, file-by-file notes, test evidence, migration steps, risk. </details> ``` ## Several changes in one PR When the PR carries more than one distinct change, give each its own `#### Issue N: <title>` heading inside the summary, with Problem and Fix as bold labels underneath it. One `### Extra context (for clankers)` at the end still covers the whole PR. ```markdown [AI-generated] ### Summary (for humans) #### Issue 1: Cache key ignores the region **Problem** - us-east reads hit eu-west entries **Fix** - Add region to the cache key #### Issue 2: Stale entries survive deploys **Problem** - The TTL is never refreshed **Fix** - Reset the TTL on every write ### Extra context (for clankers) <details> <summary>Details</summary> ... </details> ``` Titles are short noun phrases, not sentences. Only split when the changes stand on their own — steps tow