# 2925 + Luban continuation notes (2026-05-11)

## 2925 Webmail false-negative lesson

BOSS manually checked 2925 accounts and found OpenAI verification mail that automation had reported missing. Treat automation `candidateCount=0` / `no code` as suspect until checked against visible/manual UI.

Correct 2925 scraping rules:

1. Do not navigate by `#/mailList?type=收件箱` and trust the resulting list; it can show an empty/stale view.
2. Click the left `收件箱` navigation item and then click the visible toolbar `刷新`.
3. Read rows from `table.maillist-table tr`, not generic `div/li` selectors.
4. Inspect hidden tooltip/title/textContent; current alias may only appear in OpenAI bounce sender text such as `...-<aliasLocal>=2925.com@tm1.openai.com`.
5. Open the newest matching row and extract the 6-digit code from the body near `输入此临时验证码以继续：`.
6. If OpenAI says `代码不正确`, request a new email and select the newest row by timestamp; do not reuse older code candidates.

The 2031 run (`chickliu2031...`) passed OpenAI email verification after this correction and reached `https://auth.openai.com/add-phone`.

## Luban UK first phone attempt

For the 2031 add-phone page, Luban resolved OpenAI service:

```text
country: United Kingdom/England
service_id: 537935
cost: 0.05
```

OpenAI country gate passed with `countryValue=GB`, visible `英国`. The first Luban UK number was bought and submitted successfully; OpenAI moved to `phone-verification` and did not immediately reject the number. SMS polling returned `msg=wait` for 90s. Immediate reject/cancel returned a supplier timing message requiring a later stop (`停用失败,该供应商需要在两分钟后停止`). Future runners should schedule delayed cancellation/re-check rather than assuming the activation is released.