t2-p3-01draft4–7h
Caching with explicit invalidation
Spec
Redis caching on the task list endpoint with explicit invalidation on writes - not TTL-only - and a test proving invalidation actually fires on task update.
Why this matters
TTL-only caching is how you ship a system that serves stale data for exactly as long as the TTL and nobody can reproduce it. Explicit invalidation is harder and correct.
Verify
No result yet. Run `learn verify t2-p3-01` locally, or push to trigger CI.
contract
unrun