Notifications stays attached to real site ownership surfaces
These named 52H discovery routes exist so integrations, automations, notifications, multilingual, migrations, and exports/backups remain public, sellable, and traceable to signed-in site outputs instead of hiding behind generic capability-family copy.
The route keeps the add-on family visible across packs instead of burying it in generic platform language or later dashboard assumptions.
Each route points toward the signed-in site outputs that must actually operate the family so public discovery does not over-promise.
Public discovery stays browse-only and hands state changes off through /pricing and protected flows rather than mutating anything while logged out.