01
Confirm the runtime
Load the production property with its real hostname, then select Check installation in the Pact developer handoff. Pact records a successful signal only when tenant and hostname match.
02
Inspect the network
- pact.js is served from the intended first-party path
- No optional request starts before the bootstrap decision
- Quiet regions make no initial pact.js request
- Stored rejection and GPC survive reload
- Withdrawal stops purpose-bound behavior
03
Keep the performance contract
≤400 BInline≤8 KBCore Brotli0.00Consent CLSNeverLCP candidate
04
Definition of done
- Bootstrap precedes every optional tag
- GPC and stored rejection block before execution
- Quiet path makes zero initial core requests
- Purpose gates react to approval and withdrawal
- Runtime hostname and version match
- CLS remains 0.00 and Pact is never LCP