French Polynesia Proxies

Treat the route as the only planned variable. Alternate reference and proxied observations, preserve their order, and compare status, redirect destination, response marker, and observed exit country instead of relying on a single screenshot. Create one PYF row per planned attempt: source permission, client version, network, protocol, redacted selector, observed exit, UTC time, response class, and decision. Keep the sample finite, preserve missing values, and stop on the declared control signal. Use only an endpoint permitted for the French Polynesia test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Identify whether the client, gateway, upstream connection, TLS layer, or destination produced the earliest signal. Rotation must not be used to conceal a quota, block, access-control response, or other explicit stop signal. New Caledonia at 11,212 and Papua New Guinea at 7,904 are the neighbouring historical records used to place French Polynesia in Oceania. They provide no basis for claiming present stock, equivalent targeting, or destination acceptance. Keep PYF comparator rows labelled and diagnose the requested French Polynesia route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Treat the route as suitable for redirect work only when the intended country is observed and the chain can be reproduced from a clean baseline. Reject conclusions based on a cached terminal URL or an undocumented client setting. For PYF, separate mandatory requirements from preferences. Mark country observation, client compatibility, session behavior, response validity, usage measurement, and retry handling as pass or fail, then buy only if the written French Polynesia threshold survives a repeat run. Reject any French Polynesia conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat PYF verification after a material configuration change.