cataloglisted

# /catalog — build the topic catalog Writes `catalog/topics.md`: the topic hierarchy that later serves as the selection menu for `/cards`. **The ordering is the whole point.** When `goal.md` exists, the tree comes from the *goal* first and the references are attached to it afterwards. Build it the other way round and the catalog is a summary of whatever was ingested, which is how a deck ends up full of research-methodology cards nobody wanted. ## Steps 1. `knowledge/` empty → point at `/ingest`, done. 2. Read `goal.md` if it exists. **It decides the shape of the tree.** 3. If a catalog already exists: only work in the documents that are newer than the catalog (mtime) or do not appear there as a reference yet — keep the existing topics instead of re-rolling them. 4. With a lot of material (> ~15 documents or > ~200k words): fan out one reading agent per source that returns topics + subtopics + one-sentence descriptions + references, then merge and deduplicate. Otherwise read directly. 5. Write the catalog (format below) — including a `Term:` line on every subtopic whose heading names a concept — show the tree with the counts, and point at the next step. ## With a goal — the normal case 1. **Build the skeleton from `goal.md` before reading anything.** Each `###` area becomes its own top-level topic (`##`); the topics listed under it become its subtopics. Never merge two areas and never place a subtopic under an area it does not belong to — ar