docs: record chile no-free-phones run

2026-05-10 19:53:18 +08:00
parent 25a34794a1
commit 1567fd0a28
4 changed files with 446 additions and 1 deletions
@@ -0,0 +1,97 @@
+# Chile +56 phone verification attempt (2026-05-10)
+
+## Request
+
+BOSS asked to continue testing with Chile numbers:
+
+```text
+Chile / 智利 +56, 5 attempts
+```
+
+## Account/session recovery
+
+The previous account `chickliu.wnjmwncq@claw.163.com` could not be recovered to `add-phone`:
+
+- password login showed `Incorrect email address or password`
+- one-time-code login repeatedly hit `invalid_state`
+
+To avoid burning 5sim numbers before the identity gate, a fresh ClawEmail sub-mailbox was created:
+
+```text
+chickliu.apwkwesb@claw.163.com
+```
+
+The mailbox external receive gate was set and verified:
+
+```json
+{"commLevel":2,"extReceiveType":1,"extSendType":0}
+```
+
+OpenAI registration with this mailbox reached email verification. The OpenAI mail arrived in the ClawEmail sub-mailbox and the code was submitted. The flow reached:
+
+```text
+https://auth.openai.com/add-phone
+```
+
+## Chile runner
+
+Runner:
+
+```text
+/tmp/phone_verify_chile5_latest.py
+```
+
+Log:
+
+```text
+/tmp/phone_verify_chile5_latest.log
+```
+
+Effective country order was hardcoded and verified:
+
+```python
+ORDER = ['chile']
+```
+
+Mapping:
+
+```text
+5sim country: chile
+OpenAI ISO: CL
+Visible selector: 智利 (+56)
+Dial prefix: 56
+```
+
+## Result
+
+All 5 attempts passed the OpenAI country gate before buying:
+
+```json
+{"ok":true,"country":"智利 (+56)","selectValue":"CL","expected":"智利 (+56)","iso":"CL"}
+```
+
+However, each attempt failed at the 5sim buy step before any phone number was obtained:
+
+```json
+{"phase":"buy_failed","country":"chile","error":"Expecting value: line 1 column 1 (char 0)"}
+```
+
+Direct 5sim probe explained the parse error:
+
+```json
+{"status":200,"content_type":"text/plain; charset=utf-8","body_preview":"no free phones"}
+```
+
+## Conclusion
+
+Chile did not fail due to OpenAI rejection or SMS non-delivery. It failed because 5sim currently has no available `openai` activation numbers for Chile:
+
+```text
+https://5sim.net/v1/user/buy/activation/chile/any/openai -> no free phones
+```
+
+No Chile activation IDs were created, no phone number was submitted, and no 5sim order needed cancellation.
+
+## Workflow improvement
+
+5sim buy responses may be HTTP 200 `text/plain` with bodies like `no free phones`, not JSON. The runner should classify this as `buy_no_free_phones` instead of a generic JSON parse error, and should not count it as an OpenAI phone-verification attempt.
@@ -0,0 +1,78 @@
+# OpenAI login recovery gate before phone/SMS runs (2026-05-10)
+
+## Trigger
+
+Use this note before any new country-specific OpenAI phone-verification run, especially when BOSS asks to test a new 5sim country such as Chile.
+
+## Incident
+
+BOSS requested testing Chile numbers 5 times.
+
+Intended mapping:
+
+```text
+5sim country: chile
+OpenAI ISO: CL
+Visible selector: 智利 (+56)
+Dial prefix: 56
+Total attempts: 5
+```
+
+Two blockers appeared before any 5sim number was bought:
+
+1. The generated Chile runner still read `FIVE_SIM_COUNTRY_ORDER` from env, so it started with the old Europe list (`italy,poland,spain,england`) instead of `chile`.
+2. OpenAI account recovery could not return to `add-phone`:
+   - Password login showed `Incorrect email address or password`.
+   - Clicking `使用一次性验证码登录` returned `invalid_state`.
+   - Fresh Codex2API OAuth URLs plus stale-tab cleanup still landed on the password page/error state.
+
+Because the runner failed before `add-phone`, no Chile 5sim activation was bought and no number was submitted.
+
+## Rule
+
+Before buying any 5sim activation for a new country, enforce a hard pre-buy gate:
+
+```text
+current URL must be https://auth.openai.com/add-phone
+OpenAI account must already be usable / email-verified
+country selector can be set and read back for the target country
+```
+
+If the page is any of the following, stop before buying numbers:
+
+```text
+/auth.openai.com/log-in/password
+Incorrect email address or password
+invalid_state
+account_deactivated
+email-verification stale state
+```
+
+## Runner implementation guard
+
+Country-specific test runners must not accidentally read a stale env country order.
+
+For one-off country tests, explicitly set:
+
+```python
+ORDER = ['chile']  # or requested country only
+LIMIT = 5          # requested total/per-country budget
+```
+
+Also emit the effective order at startup and verify it matches the request before attempting OAuth recovery:
+
+```json
+{"phase":"phone_strict_start","countries":["chile"],"max_total_attempts":5}
+```
+
+If startup emits a different country list than requested, abort immediately rather than buying or submitting any number.
+
+## Recovery recommendation
+
+When login recovery fails with password mismatch plus `invalid_state`, do not keep generating OAuth URLs in a loop. The next step should be one of:
+
+1. create a fresh ClawEmail sub-mailbox and restart the OpenAI account flow;
+2. manually verify/reset the account password;
+3. manually test visible browser `使用一次性验证码登录` once to confirm whether `invalid_state` persists.
+
+Only resume 5sim phone attempts after `add-phone` is restored.