| 1 | # Plugin Discovery DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own contextual plugin discovery cards and welcome-screen promotions. |
| 6 | |
| 7 | ## Ownership |
| 8 | |
| 9 | - `plugin.yaml` owns metadata and always-enabled status. |
| 10 | - `extensions/` owns backend or WebUI discovery contributions. |
| 11 | - `webui/discovery-store.js` owns discovery UI state and actions. |
| 12 | |
| 13 | ## Local Contracts |
| 14 | |
| 15 | - Discovery cards must be accurate, dismissible where appropriate, and avoid advertising already-complete setup. |
| 16 | - CTA actions must match supported welcome-screen action contracts. |
| 17 | - Keep card IDs unique and plugin-prefixed. |
| 18 | - The Welcome screen `welcome-actions-end` surface renders feature channel cards plus the compact OAuth account-provider card; other hero discovery cards stay out of the lower welcome grid. |
| 19 | - Do not hide discovery cards solely because model setup is incomplete; model setup gating belongs to the chat thread. |
| 20 | |
| 21 | ## Work Guidance |
| 22 | |
| 23 | - Prefer backend status checks before surfacing setup or integration prompts. |
| 24 | |
| 25 | ## Verification |
| 26 | |
| 27 | - Smoke-test welcome-screen discovery cards, ordering, dismissal, and CTA behavior after changes. |
| 28 | |
| 29 | ## Child DOX Index |
| 30 | |
| 31 | No child DOX files. |