Add exact KV memory with persona overlays and param priority.

Canonical defaults live in exact.json (UI fills empties without an LLM call); chat session overrides beat file defaults until clear/persona change.

Co-authored-by: Cursor <cursoragent@cursor.com>

Config/_base/skills/memory.json

@@ -1,6 +1,6 @@
 {
   "id": "memory",
-  "title": "Vector memory",
+  "title": "Exact + vector memory",
   "default": true,
   "prompt_file": "memory.md"
 }

Config/_base/skills/memory.md

@@ -1,8 +1,15 @@
 # Skill: memory
 
-You have a persistent vector memory (`memory_hits` in live context).
+You have two memory layers:
 
-## When to write
+1. **Exact memory** (`## Exact memory` + live `exact` / `session_exact`) — canonical KV defaults (generation params, aspect table, architecture facts). Always prefer Exact over RAG for numbers and defaults.
+2. **Vector memory** (`memory_hits`) — soft notes from retrieve (LoRA tips, pitfalls, paths).
+
+## Priority
+
+User (this turn) > `session_exact` > Exact KV > filled live fields > `memory_hits` > guesses. Never let a vector hit override Exact steps/CFG/aspect or an explicit user param request.
+
+## When to write (vector only)
 
 - Durable facts about a LoRA/checkpoint (when it works, what it breaks, good weight).
 - Bad paths / pitfalls you discovered this session.
@@ -10,6 +17,7 @@ You have a persistent vector memory (`memory_hits` in live context).
 
 ## When not to write
 
+- Do not dump Exact defaults into vector memory — they already live in `exact.json`.
 - Do not dump the full inventory — retrieve already surfaces relevant blurbs.
 - Do not store the user's taste profile (that is `taste_profile` / taste.json).
 - Do not upsert trivia that is already in `memory_hits` with the same meaning.