moradin-capturelisted

# moradin:capture Capture an external source as a reference. **Capture EVERYTHING notable, not just what fits the current project.** Project-specific filtering happens later at distillation time. ## When invoked `/moradin:capture <url>` (or `/moradin:capture <description>` if not URL) The operator saw something interesting and wants to record it permanently. ## What you do 1. **WebFetch the URL** (or read source if local). Read README + key sections. 2. **List ALL notable concepts** in your reply. Don't pre-filter for current project relevance. Show the operator a full inventory of what's in the source: - Concept A: [one paragraph] - Concept B: [one paragraph] - Concept C: [one paragraph] - ... 3. **For each concept, propose tags:** - `topics`: from the 8-tag taxonomy (harness, memory, eval, llm, agent, arch, workflow, tooling) - `applies_to`: which projects might use it (universal, godtech, trading, future) 4. **Ask the operator to confirm or edit the tags.** Don't auto-write — get a green light. 5. **Note what you deliberately skipped** — tactical setup details, deeply specific code, or items fundamentally irrelevant. 6. **Write the reference file** at `memory/references/<source_name>.md` using `templates/reference.template.md` as scaffold. Include: - Frontmatter: name, description, topics, applies_to, type=reference, url, captured (date), last_verified (date) - Body: "What it is" + "Notable concepts" (full inventory) + "What I deliberatel