What problem does it solve? Developers extending the newsletter crawler risk editing the wrong config file, breaking conventions, or silently no-oping commands because the project has two sources.json files, strict module placement rules, and a specific CLI wiring pattern. ## Core Features & Use Cases - Source management: Add or replace newsletter sources via the add command or UI wizard, understanding that NC_HOME/sources.json is live while config/sources.json is only the install seed, with AI-detected source types (index vs listing). - Subset crawling: Crawl specific sources with --sources/--source/--only flags using the filterSeedSources helper with explicit precedence and warnings. - Extension recipes: Step-by-step conventions for adding src/ modules, CLI commands (commands.js + index.js dispatch + npm script + UI screen), publications, and fetch/extract strategies behind fetchSmart/clean.js. - Use Case: You want to add a new weekly newsletter to the crawler. Follow the procedure to run npm run add, let detectSourceType classify it, then run a bounded crawl with --since to confirm links are found and a selector is cached. ## Quick Start Ask the assistant to add a new newsletter source to the crawler and verify it with a bounded crawl using --since and --max-articles.