project-catchuplisted

# Catchup Reports what changed since the user's last checkpoint, then moves the checkpoint. The one read skill that writes anything, and it writes exactly one config key, never the ledger. ## Step 0: read the contracts Read these before doing anything. Do not work from memory of them. - `${CLAUDE_PLUGIN_ROOT}/docs/reading.md` -- the shared resolve-and-parse mechanism every read skill follows. - `${CLAUDE_PLUGIN_ROOT}/docs/ledger-format.md` -- entry grammar, Changelog grammar. - `${CLAUDE_PLUGIN_ROOT}/docs/config-contract.md` -- `last_checkpoint`'s format and who writes what. - `${CLAUDE_PLUGIN_ROOT}/docs/response-format.md` -- how the reply to the user is shaped. The report in Step 4 follows it. ## Step 1: resolve config, project and ledger Follow `reading.md` § Step A and § Step B. **No project match, or the project matches but carries no `last_checkpoint`.** This is a first run. There is no baseline to diff against, so the "delta" is the whole current ledger. Say so plainly: ``` No checkpoint on file for this project. Showing everything currently in the ledger. Once you approve, I will set a checkpoint so next time is a real delta. ``` Proceed to Step 3 with an empty changelog cutoff (every line counts as new). ## Step 2: read the ledger Follow `reading.md` § Step C. Read the whole file, not just the Changelog -- the Changelog gives you *which* IDs changed, but the current text of each entry only lives in its section. ## Step 3: compute the delta Collec