Resolve unified cache configuration and legacy migration

This commit is contained in:
2026-11-20 18:59:02 +00:00
parent 254401e5f6
commit 058703abe5
2 changed files with 124 additions and 31 deletions

View File

@@ -56,7 +56,7 @@ The sections below keep broader extensions deferred.
deterministic safety rules. Define any additional configuration and domain
compatibility checks from that workflow; do not recreate asset registration,
prompt fingerprints, or checkpoint dependency tracking.
- Reuse the selected [accepted-artifact cache policy](promptkit.md#accepted-artifact-cache)
- Reuse the selected [accepted-artifact cache policy](promptkit.md#accepted-artifact-cache-u8-resolved)
when evaluating policy changes and the need for explicit refresh.
### Broader Reconciliation Inputs And Module Selection
@@ -121,7 +121,7 @@ Define compatibility and migration policy before generated-reference chains
must span multiple schema versions or long-lived historical artifacts. The
policy should address stable identifier semantics, when an older artifact may
be decoded or adapted, and when consumers need regenerated artifacts. For cached
artifacts, use the [selected reuse policy](promptkit.md#accepted-artifact-cache)
artifacts, use the [selected reuse policy](promptkit.md#accepted-artifact-cache-u8-resolved)
and explicit refresh where needed. Do not add a general migration framework
until an actual contract change requires one.