Cache stable investigation case context with versioned deterministic aliases

docs/llm-context-caching.md

@@ -6,7 +6,7 @@ No cache handle, credential or provider conversation ID becomes required case
 state. `docs/architecture.md` and the investigation full-history policy are
 unchanged. All evidence remains in every investigation input.
 
-## First implementation
+## Transport and complete case context
 
 The existing `openai_compatible` adapter now reads
 `usage.prompt_tokens_details.cached_tokens` and
@@ -21,9 +21,10 @@ the live user JSON; no case facts, identifiers, evidence or assessments are
 removed. The archived request is not changed. This is deterministic transport
 preparation, not another LLM summary.
 
-By default on the native Gemini adapter, this instruction/schema prefix is stored as a
-Gemini `cachedContents` resource. Case-specific input and all research history
-are still sent in full. The prefix is independent of the currently selected
+By default on the native Gemini adapter, instructions, schema and the stable
+case context are stored as a Gemini `cachedContents` resource. Hypothesis state,
+budget, questions and all research history are still sent in full as live input.
+See [stable case cache](stable-case-cache-v1.md) for the partition and proof contract. The prefix is independent of the currently selected
 hypothesis. Reuse requires an exact match of endpoint, provider ID, model,
 credential fingerprint, prefix and TTL. The adapter retains at most eight
 entries (including short-lived failed-creation entries), in process memory only.