docs(25): create phase plan for catalog enrichment and agent tools

.planning/ROADMAP.md

@@ -102,7 +102,11 @@ Plans:
   3. A single API call with an array of items imports them all, upserting on (brand, model) conflict
   4. An MCP agent can call `upsert_catalog_item` with attribution fields and the item appears in the catalog
   5. An MCP agent can call `bulk_upsert_catalog` with a batch of items and all are persisted with attribution
-**Plans**: TBD
+**Plans**: 2 plans
+
+Plans:
+- [ ] 25-01-PLAN.md — Schema migration (attribution columns + unique constraint) and upsert service layer
+- [ ] 25-02-PLAN.md — HTTP upsert routes, MCP catalog tools, and client attribution display
 
 ### Phase 26: Discovery Landing Page
 **Goal**: The app opens to a public discovery feed with prominent catalog search, not a personal dashboard
@@ -145,7 +149,7 @@ Plans:
 | 22. Add-from-Catalog & Thread Integration | v2.0 | 2/2 | Complete | 2026-04-06 |
 | 23. Manual Entry Fallback | v2.0 | 1/1 | Complete | 2026-04-06 |
 | 24. Public Access & Infrastructure | v2.1 | 2/2 | Complete    | 2026-04-10 |
-| 25. Catalog Enrichment & Agent Tools | v2.1 | 0/TBD | Not started | - |
+| 25. Catalog Enrichment & Agent Tools | v2.1 | 0/2 | Not started | - |
 | 26. Discovery Landing Page | v2.1 | 0/TBD | Not started | - |
 
 ## Backlog