cache: wire rest get response caching
This commit is contained in:
@@ -61,9 +61,9 @@ Progress:
|
||||
- admin-api and mcp-server ingress rate limiting now use shared external cache state when `CRANK_CACHE_BACKEND` is `valkey` or `redis`
|
||||
- `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`
|
||||
- pending:
|
||||
- preserve strict cache isolation between workspace/agent/operation scopes while wiring concrete cache-key builders into runtime hot paths
|
||||
- wire actual response cache reads/writes into concrete runtime execution paths
|
||||
- preserve the same isolation model while extending response cache beyond the first `REST GET` hot path
|
||||
- wire replay guard / coordination state into additional concrete runtime and transport paths
|
||||
|
||||
## Planned
|
||||
|
||||
Reference in New Issue
Block a user