One-install Salesloft v2 front door over four bounded domain packs and seven revenue-engagement workflows. The suite admits all 198 current v2 method/path operations published through Salesloft's content-hashed OpenAPI reference fragments: the 16-operation compatibility root preserves every prior ID and effective route while dependencies add 182 operations. Salesloft does not publish the monolithic build-time OpenAPI file, so no false openapi_source pin is declared; the generated audit fixture records each official page and hashed fragment instead. The upgrade repairs cadence-enrollment query transport, note association fields, array-valued filters, origin/path composition, and recipe bindings. Operations that publish the page/per_page contract walk bounded pagination until metadata.next_page is null. Every mutation requires approval, sensitive new reads are marked sensitive-read, reads are uncached, JSON request fields follow Salesloft's recommended format, and unsafe response integers remain exact strings.