docs: document local-first backend, gemma4 gotchas, and contract tests

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/claude-integration.md

@@ -3,7 +3,7 @@
 ## Overview
 
 Tatlock uses a bidirectional Claude architecture:
-- **Scenario A**: Tatlock powered by Claude backend (with Ollama fallback) — **COMPLETE**
+- **Scenario A**: Tatlock powered by Claude backend (with Ollama fallback) — **COMPLETE**, then **rolled back to local-first**: Ollama/gemma4 is primary, Claude is retained as fallback (`PREFER_CLOUD_BACKEND=false`)
 - **Scenario B**: Tatlock exposed as MCP server for external Claude instances — **OPEN**
 - **Scenario C**: Offline operation via Ollama — **COMPLETE**
 

docs/roadmap.md

@@ -12,7 +12,7 @@ This document tracks open/planned work. Completed phases have been removed.
 - Household staff: Tatlock (Butler), Steward, Librarian, Biographer
 - Core tools: Calculator, Date/Time, Web search (SearXNG)
 - Memory system: Qdrant (vector), Redis (session cache), multi-tenancy via ContextVar
-- Dual backend: Claude (preferred) + Ollama (fallback)
+- Dual backend: Ollama/gemma4 (primary) + Claude (fallback)
 - 439 tests with good coverage
 
 ---