Skip to content

The agent that grows with you

docs(unbroker): one captcha instruction; state machine names the defunct close-out

kshitijk4poor932b5104dbab
diff --git a/optional-skills/security/unbroker/SKILL.md b/optional-skills/security/unbroker/SKILL.md
index 3ecccb61433..a8fdcbc07a2 100644
--- a/optional-skills/security/unbroker/SKILL.md
+++ b/optional-skills/security/unbroker/SKILL.md
@@ -330,7 +330,8 @@ is where lead buyers get it. The same engine, entered from the number:
actually gone; note paid-tier retention in the report.
- **Soft CAPTCHAs clear by default; don't fight the hard ones.** The default cloud browser passes
managed/soft challenges as normal operation (those brokers stay T1). For a hard interactive one it
- genuinely can't pass, record `blocked` and let the stealth/operator-browser pass take it - never a
+ genuinely can't pass, record `human_task_queued --reason "..."` so the operator gets it once in
+ the digest (a `blocked` case re-scans, re-finds the listing and re-queues the opt-out) - never a
third-party solver service or fingerprint spoofing.
- **Broker pages change.** If a flow breaks, `$PDD record ... blocked` and flag the broker file in
`references/brokers/` for re-verification instead of guessing.
diff --git a/optional-skills/security/unbroker/references/methods.md b/optional-skills/security/unbroker/references/methods.md
index 6aa5253efc4..fdc4fc324c1 100644
--- a/optional-skills/security/unbroker/references/methods.md
+++ b/optional-skills/security/unbroker/references/methods.md
@@ -253,16 +253,16 @@ reCAPTCHA checkbox - as normal operation, so those brokers stay T1 and you just
**not** CAPTCHA solving: no solver service, no fingerprint spoofing.
Only a **hard** challenge the browser genuinely can't pass (interactive image grids, behavioral
-scoring that flags the session) becomes a fallback: `record ... blocked` and requeue it for the
-stealth/operator-browser pass (`methods.md` → scan ladder 3b - the operator's own residential
-browser is the reliable unblock). Without a cloud browser configured, soft-CAPTCHA brokers drop to
-T2 and become human tasks. **Never use a third-party CAPTCHA-defeating service.**
+scoring that flags the session) becomes a fallback: `record ... human_task_queued --reason "..."`
+so it reaches the operator once in the digest (the operator's own residential browser is the
+reliable unblock; a `blocked` case would re-scan, re-find the listing and re-queue the opt-out).
+Without a cloud browser configured, soft-CAPTCHA brokers drop to T2 and become human tasks. **Never use a third-party CAPTCHA-defeating service.**
### CAPTCHA policy, clarified (on a consenting first-party opt-out)
- **Do NOT defeat** behavioral / token challenges: a Cloudflare Turnstile that will not auto-clear,
**DataDome**, and **"slide-to-verify" gesture-entropy sliders** (the InfoPay lane). These are hard
- stops -> take the email lane (rule above) or record `blocked`.
+ stops -> take the email lane (rule above) or record `human_task_queued` with the reason.
- **A visible Google reCAPTCHA v2 / Enterprise checkbox is in this class** (verified live 2026-10-26 across two sites): synthetic CDP clicks on a debug-profile Chrome do NOT toggle it -
no token, no challenge appears, no error surfaces, `grecaptcha.getResponse()` stays empty -
so it is a silent hard stop for the automation browser. By contrast a managed Cloudflare
diff --git a/optional-skills/security/unbroker/references/state-machine.md b/optional-skills/security/unbroker/references/state-machine.md
index 4952c999da0..d2f467bf834 100644
--- a/optional-skills/security/unbroker/references/state-machine.md
+++ b/optional-skills/security/unbroker/references/state-machine.md
@@ -43,9 +43,14 @@ blocked -> searching | found | not_found | indirect_exposure | acti
A transition to the same state is always allowed (idempotent field updates).
+**Defunct-broker close-out:** when the broker record carries `defunct` (domain seized / NXDOMAIN),
+`action_selected | submitted | verification_pending | awaiting_processing | human_task_queued ->
+not_found` is also allowed (`ledger.DEFUNCT_CLOSEOUT_FROM`; `record` checks the broker record). A
+dead site cannot hold the listing. For a live broker these moves stay illegal.
+
## Notes / gotchas learned in the field
-- **`submitted -> not_found` is ILLEGAL.** A lodged request that then finds no matching profile is a
+- **`submitted -> not_found` is ILLEGAL** for a live broker. A lodged request that then finds no matching profile is a
no-op that resolves as `awaiting_processing`, never a walk back to `not_found`. (This is why a guided
opt-out whose matcher says "no results" after you have already submitted is recorded
`awaiting_processing`, not `not_found`.)
diff --git a/website/docs/user-guide/skills/optional/security/security-unbroker.md b/website/docs/user-guide/skills/optional/security/security-unbroker.md
index 42198d5d9b9..dc9f04a3125 100644
--- a/website/docs/user-guide/skills/optional/security/security-unbroker.md
+++ b/website/docs/user-guide/skills/optional/security/security-unbroker.md
@@ -344,7 +344,8 @@ is where lead buyers get it. The same engine, entered from the number:
actually gone; note paid-tier retention in the report.
- **Soft CAPTCHAs clear by default; don't fight the hard ones.** The default cloud browser passes
managed/soft challenges as normal operation (those brokers stay T1). For a hard interactive one it
- genuinely can't pass, record `blocked` and let the stealth/operator-browser pass take it - never a
+ genuinely can't pass, record `human_task_queued --reason "..."` so the operator gets it once in
+ the digest (a `blocked` case re-scans, re-finds the listing and re-queues the opt-out) - never a
third-party solver service or fingerprint spoofing.
- **Broker pages change.** If a flow breaks, `$PDD record ... blocked` and flag the broker file in
`references/brokers/` for re-verification instead of guessing.