Cross-vendor companion to the per-vendor augmentation recipes folded into the `recued-core.hubspot` + `recued-core.salesforce` vendor packs (the standalone `sales-augmentation-*` packs were retired in D-182 Slice 4). Ships *alerts only* — no producers. Producers stay vendor-specific in each per-vendor pack and write rows under `connection.api.<vendor>.<entity>.<id>.<topic>` paths; this pack reads them through the `core.data.enrichment.list` op, vendor-agnostic by construction (the dynamic `scope` arg resolves to `{{context.event.payload.platform}}` at read time). The three CRM-entity alerts subscribe via the canonical `on: <crm_alias>.changed` sugar (`deal.changed` / `contact.changed`), which fans one subscription per installed vendor carrying that alias — HubSpot + Salesforce today, any future CRM automatically; the new-inquiry alert subscribes to inbound mail (`data.mail.**.created`) instead. Install AT LEAST one vendor-specific pack alongside this one to get producers populating the topics. Variants share `variant_group` with the per-vendor recipes and carry `variant_kind: 'cross_vendor'` discriminator so the marketplace UI can collapse the card with vendor switch. Per spec § A.8.2 the install dialog SHOULD warn about overlap when both this pack and a vendor-specific pack covering the same alerts are installed (non-blocking — multi-CRM tuners may want both for vendor-specific tuning + cross-vendor catch-all).