From 0415d07cd0d1ce824657a89e9787fcf0361f459d Mon Sep 17 00:00:00 2001 From: carlotestor Date: Sat, 19 Sep 2026 10:50:37 +0000 Subject: [PATCH] docs: invalidate_models_cache is the only delete_disk entry point, not the only snapshot-dropping path --- docs/architecture/models-cache-invalidation.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/architecture/models-cache-invalidation.md b/docs/architecture/models-cache-invalidation.md index 21f4f2bd..ce96c968 100644 --- a/docs/architecture/models-cache-invalidation.md +++ b/docs/architecture/models-cache-invalidation.md @@ -69,7 +69,13 @@ the fingerprint captured at publish time. ## Invalidation modes (`invalidate_models_cache`) `invalidate_models_cache(*, delete_disk=True)` is the only entry point that -drops the published snapshot. It has two modes: +offers the `delete_disk` choice. It is **not** the only path that drops the +published in-memory snapshot: `invalidate_provider_models_cache()`, +`_get_fresh_memory_models_cache()` (on a fingerprint mismatch or an invalid +cached shape) and the config-reload branch inside +`get_available_models()` also reset `_available_models_cache` and call +`_sync_models_cache_provenance()`. None of those paths take a `delete_disk` +argument; they only clear memory. `invalidate_models_cache` has two modes: | Mode | What is dropped | When to use | | --- | --- | --- |