cache: scope response entries by operation version

This commit is contained in:
a.tolmachev
2026-05-04 07:45:04 +00:00
parent 50b1e5ea13
commit 6cec445b4f
6 changed files with 34 additions and 4 deletions
+1
View File
@@ -62,6 +62,7 @@ Progress:
- `ExecutionConfig.response_cache` is now part of the public operation model, and `admin-api` validates the safe Community baseline: only explicit `REST GET` operations without `auth_profile_ref`
- cache boundary and namespace rules are now documented for `platform / coordination cache` versus `response cache`
- runtime executor now performs actual response cache reads/writes for eligible `REST GET` operations with keys isolated by `workspace + agent + operation + request fingerprint`
- response cache keys now also include `operation version`, so a new published version does not reuse stale cached payloads from the previous one
- mcp-server published tool catalog now uses shared coordination snapshots across instances, while preserving the same `workspace + agent` isolation model
- pending:
- preserve the same isolation model while extending response cache beyond the first `REST GET` hot path