memtrace-session-continuity

## Overview Session continuity for agents. Store a timestamp from your last session and call `get_changes_since` to see exactly what happened since then — then drill into details with `get_evolution` if needed. **Core principle:** Persist a `since` timestamp (or the `until` from your last catch-up call). Never invent a `days` parameter. ## Steps ### 1. Find or bootstrap the session anchor Look for a stored anchor from your last session: ```json { "repo_id": "memdb", "since": "2026-04-13T10:43:00Z" } ``` If you have no anchor yet (first run), call `list_indexed_repositories`. Use `last_episode_time` from the repo entry as a bootstrap `since` value, or ask the user how far back to look. ### 2. Call `get_changes_since` ```json { "repo_id": "memdb", "since": "2026-04-13T10:43:00Z" } ``` Optional: pass `until` to cap the upper bound (defaults to now). **Required param is `since`** — not `last_episode_id`, not `days`. Same time formats as `get_evolution.from` (`"7d ago"`, ISO-8601, etc.). Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root). ### 3. Interpret the response Response shape: see [Output](#output) below. Act on `totals.episode_count`: | `totals.episode_count` | Action | |---|---| | `0` | Nothing changed — safe to proceed | | `1–20` | Review each episode's `touched_files` and change counts | | Many episodes | Scan `touched_files` for overlap with your task; drill down with `get_evol...