V2 one-install PayPal front door over 13 immutable source-pinned feature packs. The visible compatibility root grows from 21 to 70 operations while preserving every established operation ID, route, argument, entity, risk, approval, result-path, and cache contract; compatibility hardening adds recursively closed requests, explicit required empty JSON bodies, and lossless unsafe-integer responses. The installed family publishes 109 catalog operations covering 105 of 115 unique official routes, including 4 useful complete-page-walk aliases; 10 multipart, inbound-callback, internal-scope, or provider-prose-deprecated routes fail closed. Root additions are action-only so the established read surface does not silently widen default grants; remaining reads and one reserved action per source stay in the dependency leaves. Every new mutation requires approval, reads are uncached and not approval-gated, money movement and irreversible financial decisions are destructive, and supported POST retries require caller-owned PayPal-Request-Id values. Bearer authorization and merchant/partner identity headers remain connection-owned, Prefer is binding-owned, JSON Patch arrays use bounded verbatim JSON, projected JSON is recursively closed, and unsafe response integers stay exact. This root intentionally omits a misleading single openapi_source because PayPal publishes thirteen independent contracts; each dependency leaf carries its exact hash pin and the generated audit fixture reconciles every root route. No workflow or work-entity Source is claimed over financial or control-plane records.