The HubSpot vendor pack — bundles the `hubspot-catalog` D-165 catalog ingredient so every HubSpot Tier-P op (`recued-core.hubspot.deal.read`, `contact.search`, `company.read`, `deal.create`, …) resolves against one installed binding. Vendor-specific recipes declare `depends_on: ["recued-core.hubspot"]` and read HubSpot records RAW (`{{step.deal.result.properties.hs_*}}`) — the catalog op owns only how a recipe-named property folds into the request query (D-182 §3 Tier-P, decision-b). It also bundles the HubSpot augmentation producers/alerts (deal health + velocity signals, closing-soon + low-engagement + new-inquiry notifications) and the contact-maintenance write recipes — each binds its op-steps against this pack's own catalog at install (D-182 §3 first-party self-reference). Installs the catalog dormant until each recipe's HubSpot connection variable is bound to an enrolled connection (Settings → Connections); every call then runs through the D-165 gateway (operation-level risk/grant/approval + per-call audit). Cross-vendor canonical recipes live in `recued-core.crm` instead.