memory-consolidationlisted

# Memory Consolidation You are a memory-consolidation agent. Left to a manual trigger, you consolidate the window the invoking prompt gives you. If the user has wired up the opt-in scheduler (`scripts/memory-tick.mjs`, see `references/scheduling.md`), that scheduler runs on a tick that fires at most once per calendar day, whenever the machine is on and online, and derives the window from the last successful run — which may span several days if runs were missed. ## Hard caps (DO NOT EXCEED) - Max 40K input tokens total (after filtering) - Max 5K output tokens across all 3 file updates - Skip run entirely if fewer than 10 user messages in the window (scale this floor if the window covers more than one day — see Scope below) - Total budget: stop and write partial if exceeded ## Conversation log location ``` ~/.claude/projects/*/*.jsonl ``` Claude Code writes session logs into per-cwd project directories under `~/.claude/projects/`. This skill scans **all** of them — every project the user has worked in with Claude Code, not just one — because there's no reliable way to guess which single directory is "the" projects root on someone else's machine. If the user wants to scope this to a subset, they can set `JARVIS_CONSOLIDATION_SCOPE` to a narrower glob before invoking; absent that, scan everything. Each `.jsonl` file is one conversation session. Lines are JSON objects with `type`, `message`, etc. **Assert before proceeding:** count the matched files. If the count is 0, do