refactor(memory): simplify Dream config naming and rename gitstore module

docs/MEMORY.md

@@ -149,10 +149,10 @@ Dream is configured under `agents.defaults.dream`:
   "agents": {
     "defaults": {
       "dream": {
-        "cron": "0 */2 * * *",
-        "model": null,
-        "max_batch_size": 20,
-        "max_iterations": 10
+        "intervalH": 2,
+        "modelOverride": null,
+        "maxBatchSize": 20,
+        "maxIterations": 10
       }
     }
   }
@@ -161,10 +161,22 @@ Dream is configured under `agents.defaults.dream`:
 
 | Field | Meaning |
 |-------|---------|
-| `cron` | How often Dream runs |
-| `model` | Optional model override for Dream |
-| `max_batch_size` | How many history entries Dream processes per run |
-| `max_iterations` | The tool budget for Dream's editing phase |
+| `intervalH` | How often Dream runs, in hours |
+| `modelOverride` | Optional Dream-specific model override |
+| `maxBatchSize` | How many history entries Dream processes per run |
+| `maxIterations` | The tool budget for Dream's editing phase |
+
+In practical terms:
+
+- `modelOverride: null` means Dream uses the same model as the main agent. Set it only if you want Dream to run on a different model.
+- `maxBatchSize` controls how many new `history.jsonl` entries Dream consumes in one run. Larger batches catch up faster; smaller batches are lighter and steadier.
+- `maxIterations` limits how many read/edit steps Dream can take while updating `SOUL.md`, `USER.md`, and `MEMORY.md`. It is a safety budget, not a quality score.
+- `intervalH` is the normal way to configure Dream. Internally it runs as an `every` schedule, not as a cron expression.
+
+Legacy note:
+
+- Older source-based configs may still contain `dream.cron`. nanobot continues to honor it for backward compatibility, but new configs should use `intervalH`.
+- Older source-based configs may still contain `dream.model`. nanobot continues to honor it for backward compatibility, but new configs should use `modelOverride`.
 
 ## In Practice