project-gapslisted

# Gaps An audit of the Open items section for exactly two problems: nobody owns it, or it has sat past the staleness threshold. Nothing else is a gap. In particular, an unowned **decision** is normal (per `ledger-format.md`) and is never reported here. ## 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, § Step D and § Notices, shared wording -- the shared resolve-and-parse mechanism Steps 1 and 2 below follow, the staleness- threshold resolution Step 1 also needs, and 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: Open items, § Body markers, § Relationships between entries, § A decision imposed from outside, § Section: Decisions and § Reading rules for skills -- the checkbox/`@unassigned`/resolution grammar, the one-hop blocker chase, and why an unowned imposed decision is excluded. - `${CLAUDE_PLUGIN_ROOT}/docs/config-schema.md` § Field notes -- what `stale_after_days` measures. - `${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 only § Entries are named topic-first, ID in parentheses, but the contract's own scope s