| 1 | # Banner Extensions DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own backend banner and discovery-card contributions. |
| 6 | |
| 7 | ## Ownership |
| 8 | |
| 9 | - Ordered Python files append alert banners or discovery cards to the mutable `banners` list. |
| 10 | |
| 11 | ## Local Contracts |
| 12 | |
| 13 | - Banner IDs must be unique and stable. |
| 14 | - Use supported banner/card fields and types only. |
| 15 | - Banner HTML links that trigger WebUI behavior should use supported structured actions, such as `data-banner-action`, instead of inline JavaScript handlers. |
| 16 | - Do not expose secrets, local paths, or raw system diagnostics in banner text. |
| 17 | |
| 18 | ## Work Guidance |
| 19 | |
| 20 | - Gate setup or warning banners on current configuration/status where possible. |
| 21 | |
| 22 | ## Verification |
| 23 | |
| 24 | - Smoke-test welcome-screen banner rendering, ordering, dismissal, and CTA behavior after changes. |
| 25 | |
| 26 | ## Child DOX Index |
| 27 | |
| 28 | No child DOX files. |