What problem does it solve? Adding a new router model to OpenRouter touches many disconnected parts of the monorepo — the RouterModel enum, a new router plugin, plugin registration, production model rows, seed CSV verification, settings UI, and tests — and missing any step causes subtle routing failures. ## Core Features & Use Cases - Step-by-step checklist: Covers RouterModel enum entry, plugin scaffolding with required patterns (guard clause, placeholder endpoint, resolveEndpoints, routerRequest threading, metadata logging), and init-plugins registration. - Production and seed workflow: Explains creating the model row in prod Mission Control, verifying it lands in postgres/seeds/models_rows.csv, and local DB fallback insertion. - UI, docs, and testing guidance: Details plugin settings UI wiring, PostHog events, docs updates, unit/pipeline tests, and local e2e verification with curl. - Use Case: When adding a router like openrouter/pareto-code, follow the checklist to implement the plugin, register it, seed the model, and verify routing end to end. ## Quick Start Ask the AI to add a new router model with a given slug, enum key, plugin directory, and plugin class name, and have it follow this checklist.
