lov-cc-mv

# lov-cc-mv Two modes in one tool: **Directory-level** (default) — four things in one shot: 1. `mv FROM TO` on disk (fs.renameSync — instant, preserves everything) 2. Rewrites `~/.claude/projects/<slug>/*.jsonl` session store — including every sub-directory slug 3. Rewrites `~/.claude/history.jsonl` (prompt up-arrow recall) 4. Rewrites `~/.claude/sessions/*.json` (running-session records) **Session-level** (opt-in, via `--session`/`--grep`/`--pick`) — migrate a subset of chats: 1. Copies only the selected `.jsonl` files from FROM's slug dir into TO's 2. Rewrites each file's `cwd` from FROM → TO 3. Rewrites only the matching running-session records 4. Does **not** touch `history.jsonl` or `fs mv` (project itself isn't being moved) 5. Sub-dir slugs are ignored (root only by design) Old slug dirs and source sessions are left intact unless `--delete-source` is passed. ## When to Trigger **YES — directory-level** when: - User wants to move/rename a project folder (prospective move — we do the mv) - User already moved the folder externally and CC lost history (post-move recovery — use `--no-mv` or the `cc-migrate-session` alias) - Sub-dir sessions under FROM should come along (handled automatically) **YES — session-level** when: - User wants to migrate only *some* sessions from FROM to TO — identified by id, topic/content, or to be picked interactively - User said "只搬这几个" / "those chats about X" / "not all of them" - User needs to split one project's chat history across tw...