project-sourceslisted

# Sources Answers the question `project-catchup` cannot: not "what did Daikenja write since I looked" but "what moved in the documents this project is tracked from". For a project that consists largely of tracking documents other people own, this is the difference between one check and re-reading everything. The check is cheap by design: a source stores the last-modified value its own system reported when it was last read, and this skill compares that against what the system reports now. Different means moved. No content is diffed, no date arithmetic is done, and nothing is re-read until the user asks. ## 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` § Section: Sources -- the head line, the fields, the baseline rule, and the Changelog verbs. - `${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 follows § The answer comes first, § Entries are named topic-first, ID in parentheses and § A clean res