One-install Datadog US1 front door over 17 stable management and observability packs plus four existing workflows. The complete generated suite admits 1,035 callable operations: 1,033 of 1,038 stable nondeprecated operations in Datadog's immutable official v1/v2 schemas plus the two still-official per-monitor mute and unmute compatibility routes documented outside the generated v1 schema. Five explicit transport exclusions are three multipart-only IdP/stegadography requests and two POST operations whose binary ZIP success responses cannot use the GET-only file_ref capture transport. Four dedicated-host event intake, log intake, On-Call paging, and product-analytics intake packs are separately installable so ordinary API access never requests ingestion or alternate-host credentials. The compatibility root keeps all 10 prior operation IDs and routes while the dependency and optional packs add 1,025 operations. The root intentionally omits a misleading partial OpenAPI pin because its compatibility surface spans two official schemas and two official documentation pages; every single-schema leaf carries its exact immutable pin and the reverse-audit fixture records all authorities. Reads are uncached, sensitive reads are marked sensitive-read, and every mutation is grant-off and approval-gated. JSON responses and generated leaf int64 inputs remain exact decimal strings; legacy root numeric inputs stay unchanged for workflow compatibility. Forty-one of 51 provider-declared pagination contracts are followed through their original route. The ten POST-search cursors nested inside JSON request bodies remain explicit because the current paginator cannot replay them without changing the documented wire shape, so automatic completeness is not claimed for those operations.