docs: update README and CONFIGURATION for ctx_search, ctx_reduce_enabled, and dreamer timer

- README: five tools (was four), ctx_memory is now write/delete only,
  added ctx_search section, updated cross-session memory search ref,
  added message_history_fts/index to storage table
- CONFIGURATION.md: added ctx_reduce_enabled option to Core table,
  updated dreamer scheduling to reflect independent 15-minute timer

Author: ualtinok

CONFIGURATION.md

@@ -38,6 +38,7 @@ Higher-tier models with longer cache windows benefit from a longer TTL. Setting
 | Option | Type | Default | Description |
 |--------|------|---------|-------------|
 | `enabled` | `boolean` | `false` | Master toggle. |
+| `ctx_reduce_enabled` | `boolean` | `true` | When `false`, hides `ctx_reduce` tool, disables all nudges/reminders, and strips reduction guidance from prompts. Heuristic cleanup, compartments, memory, and search still work. Useful for testing whether automatic cleanup alone is sufficient. |
 | `cache_ttl` | `string` or `object` | `"5m"` | Time after a response before applying pending ops. String or per-model map. |
 | `protected_tags` | `number` (1–20) | `20` | Last N active tags immune from immediate dropping. |
 | `nudge_interval_tokens` | `number` | `10000` | Minimum token growth between rolling nudges. |
@@ -141,7 +142,7 @@ Configures the dreamer agent — both the model it uses and the maintenance task
 
 ### How scheduling works
 
-The schedule check piggybacks on `message.updated` events with an hourly debounce. When the current time falls inside the configured window:
+An independent 15-minute timer checks the schedule regardless of user activity, so overnight dreaming triggers even when the user isn't chatting. When the current time falls inside the configured window:
 
 1. The scheduler scans the memory store for projects with activity since the last dream.
 2. Eligible projects are enqueued into a SQLite-backed dream queue.

README.md

@@ -81,7 +81,7 @@ And overnight, a **dreamer** agent consolidates, verifies, and improves memories
 
 ## What Your Agent Gets
 
-Magic Context injects structured context automatically and gives the agent four tools.
+Magic Context injects structured context automatically and gives the agent five tools.
 
 ### `ctx_reduce` — Shed weight
 
@@ -120,10 +120,19 @@ Architecture decisions, naming conventions, user preferences — anything that s
 
 ```
 ctx_memory(action="write", category="ARCHITECTURE_DECISIONS", content="Event sourcing for orders.")
-ctx_memory(action="search", query="authentication approach")
 ctx_memory(action="delete", id=42)
 ```
 
+### `ctx_search` — Unified search
+
+Search across all data layers with a single query — project memories, session facts, and raw conversation history. Results are ranked by source (memories first, then facts, then message hits).
+
+```
+ctx_search(query="authentication approach")
+```
+
+Message results include ordinal numbers the agent can pass to `ctx_expand` to retrieve the surrounding conversation context.
+
 ### Automatic context injection
 
 Every turn, Magic Context injects a `<session-history>` block containing:
@@ -170,7 +179,7 @@ As context usage grows, Magic Context sends rolling reminders suggesting the age
 
 After each historian run, qualifying facts are promoted to the persistent memory store. On every subsequent turn, active memories are injected in `<session-history>`. New sessions inherit all project memories from previous sessions.
 
-Memories are searchable via `ctx_memory(action="search", ...)` using semantic embeddings (local by default) with full-text search as fallback.
+Memories are searchable via `ctx_search` alongside session facts and raw conversation history, using semantic embeddings (local by default) with full-text search as fallback.
 
 ### Dreamer
 
@@ -230,6 +239,8 @@ All durable states live in a local SQLite database. If the database can't be ope
 | `memory_embeddings` | Embedding vectors for semantic search |
 | `dream_state` | Dreamer lease locking and task progress |
 | `dream_queue` | Queued projects awaiting dream processing |
+| `message_history_fts` | FTS5 index of user/assistant message text for `ctx_search` |
+| `message_history_index` | Tracks last indexed ordinal per session for incremental FTS population |
 | `recomp_compartments` | Staging for `/ctx-recomp` partial progress |
 | `recomp_facts` | Staging for `/ctx-recomp` partial progress |