cataloglisted

# The tooling catalog One job: keep `WSS.record.tooling.catalog` — a human-readable index of every skill and agent, what each is for, and the diagram of who invokes whom — true of the tree the run ends with. **The cross-skill contract with `--wss-tidy`.** `wss-tools-inventory.sh` is the discovery step neither skill skips. Before this skill renders or edits anything, run `bash wss/scripts/wss-tools-inventory.sh` (no `--root` flag) to regenerate `.claude/WSS.TOOLS.json` — `WSS.record.tooling.inventory` — so the catalog describes what is actually on disk rather than what the last run left behind. `--wss-tidy` runs the same script and then invokes this skill after any edit that restructures a file, for the same reason from the other side: a row or an arrow written before a Job 3, 4 or 5 edit lands describes a tree that no longer exists. **Every skill, agent, script and hook entry in `.claude/WSS.TOOLS.json` needs a matching row here, and every catalog row of those four kinds needs a matching entry there.** `wss-doctor.sh` verifies that pairing on every run (not `--check`, which is `wss-tools-inventory.sh`'s flag, not this script's) — keep it true rather than letting either side drift. A contract, reference or writer entry has no comparable catalog row to check by design; see the doctor's own "Catalog rows vs tools inventory" section for exactly which kinds are covered and why the rest are out of its reach. **It does not fire on a file belonging to this suite** — including the