fix(content): detect explicitly-rendered Turnstile managed challenge (TPS /InternalCaptcha)

[DustinVK]

What

detectChallenge() now returns true when the Cloudflare Turnstile API script (challenges.cloudflare.com/turnstile) is present in the top document, closing a gap where the TruePeopleSearch /InternalCaptcha managed challenge slipped past every existing heuristic and the sidebar showed verdict buttons over a live bot-gate.

Why it was missed

The gate renders Turnstile via turnstile.render(...) — so there is no .cf-turnstile container, and the widget iframes are about:blank (content injected cross-frame). The only reliable top-document signal is the Turnstile API <script>. Every prior selector (.cf-turnstile, iframe[src*="challenges.cloudflare.com"], the interstitial ids) keys off elements this shape doesn't expose.

Pre-existing gap, not a PR #6 regression — src/content/classify.ts is untouched by the tab-registry PR. Found during manual QA of that branch.

The fix (one line)

if (!turnstile && document.querySelector('script[src*="challenges.cloudflare.com/turnstile"]')) {
  return true;
}

Two non-obvious details, both locked by tests:

• Host-specific match, not a substring. The same page hosts a cf.clym-widget.net iframe (a Clym consent widget, not Cloudflare — the cf. prefix is coincidental). A bare cf/cloudflare match would false-positive on it.
• The !turnstile guard is load-bearing. Real solved Turnstile pages also carry the api.js script; without the guard, every solved container-Turnstile would falsely re-detect. The guard routes the container case to the existing solved/unsolved logic.

QA evidence (Firefox 140+)

• Clean /results pages return null for this selector → no false-positive challenge over a real listing.
• Solving /InternalCaptcha navigates away to the person page → the fresh load reports CHALLENGE_RESOLVED; no in-page solved-state detection needed.
• Manual pass green: /InternalCaptcha → challenge view (Skip only) → solve → back to results, challenge key cleared, verdict view returns.

Scope — deliberately minimal

The human-in-the-loop plus Skip (no-wedge rule) is the backstop, so hardening for shapes no shipping broker exhibits is deferred:

• Deferred: the unsolved-refinement (cf-turnstile-response check — inert on the callback-rendered TPS interstitial), the observer attributeFilter hardening (load-time detection already catches TPS), and the option-2 per-broker challenge.urlIncludes hint (schema + signed-dataset + CI cost, not yet needed).
• Carried forward: an M9 per-broker challenge-resolve gate (plan/expurge-progress.md) — detection is generic and manifest-bounded, but resolve-via-navigation is proven n=1 (TPS). A future broker that resolves its gate inline needs a resolve signal before onboarding, or it would strand the challenge view over real results.

Tests

• test(content): reproducing fixture (managed challenge → true) + two regression locks (solved-container-with-script → false for the guard; Clym-only → false for the host-specific selector).
• Full suite green: 190 passed, tsc --noEmit clean, npm run build clean.

🤖 Generated with Claude Code