Overlay runtime cache configuration on documented defaults #23

Priority

P1 — High — completed.

Resolution

Completed by #68 (71f26a278cf390d864da15ae017ab41e3afba5c2) and released in https://github.com/lan17/DialCache/releases/tag/v0.7.0.

Shipped contract

• defaultConfig is the baseline; a non-null runtime provider result overlays it field by field.
• Provider null, defensive undefined, or an empty config applies no overrides.
• Missing runtime leaves inherit; explicit requestLocal: false and per-layer ramp: 0 disable inherited policy.
• An omitted baseline remains fully disabled; a configured TTL with omitted ramp defaults to 100%.
• Provider exceptions and malformed dynamic policy fail open uncached rather than silently re-enabling defaults.
• Static/default policy is validated and snapshotted when cached() registers a definition or getOrLoad() starts its invocation.
• DialCacheKeyConfig.disabled() is the explicit all-layer kill switch.
• missing_config was replaced by the bounded policy_disabled reason.
• The unused deprecated MissingKeyConfigError export was removed before release.

Compatibility delivered

• Partial runtime configs now inherit unspecified defaults instead of disabling them.
• Runtime kill switches must be explicit.
• Dashboards migrated from reason="missing_config" to reason="policy_disabled".
• Cache keys, Redis frames/Lua, invalidation identity, serializers, and client ownership were unchanged.

The current implementation and documentation are in main@84341f221da625af0df147e54c0eff7b1d8bb3eb / dialcache@0.10.0.