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` § Step A0, § Step A, § Step B, § Step C and § Notices, shared wording -- the shared resolve-and-parse mechanism Steps 1 and 2 below follow, plus the exact notice text they reuse without restating it (a config marked absent or a project left unregistered has no literal wording inline in Step A -- only in § Notices, shared wording). - `${CLAUDE_PLUGIN_ROOT}/docs/ledger-format.md` § IDs, § Body markers, § Section: Decisions, § Section: Open items, § Section: Context links, § Section: Sources, § Section: Changelog, § Compacting a long summary and § Reading rules for skills -- ID range expansion, the markers this skill carries through unchanged, each section's own grammar for looking up a changed ID's current text, and the delta-reporting rules. - `${CLAUDE_PLUGIN_ROOT}/docs/config-schema.md` § Field notes -- `last_checkpoint`'s format. - `${CLAUDE_PLUGIN_ROOT}/docs/config-writers.md` -- who writes what. This doc has no subsections to narrow to -- the whole file is that one topic. - `${CLAUDE_PLUGIN_ROOT}/docs/response-format.md` -- how the reply to the user is shaped. Read in full and not narrowed to a section: Step 4 explicitly