tooling-catalog-synclisted

# Keeping the tooling files honest Two jobs, both about the files that describe and drive the tooling: 1. **The catalog** — `record.tooling.catalog` is a human-readable index of every skill and agent: what exists and what it is for, so the user can see it at a glance without opening every file. 2. **The claims inside those files** — `record.tooling.sources`. A skill or agent file that states something false about the project is worse than one that states nothing, and nothing else in the workflow owns them. **Project facts come from `.claude/workflow.json`**: `record.tooling.catalog` and `record.tooling.sources`. Without a manifest, fall back to `.claude/TOOLING.md`, `.claude/skills/*/SKILL.md` and `.claude/agents/*.md`, and say so. Who owns what else is [`~/.claude/workflow/ownership.md`](../../workflow/ownership.md). ## When it triggers - A skill or agent is created, removed, or has its `description` or purpose edited in a way that changes what it does or when it's used. - **A stale claim is found inside a skill or agent file** — by you, or dispatched here by `--check`. Not needed for internal changes that don't alter purpose, like rewording a section. **It does not fire on a global skill from another project's session.** A defect in a file under `~/.claude` — including the very skill being executed — is appended to `~/.claude/bug-reports.md` and left there. The edit belongs to a session in `~/.claude`; the inbox is what stops the finding dying with t