[BUG] PoP status alignment between Polkadot App and CLI (needs verification)

[ottovlotto]

Severity: P0 if real — needs verification
Reported by: Francisco
OS / device: OS not captured
Source: Testathon Session 02 (2026-05-20), bug B29.

Symptom

Francisco passed PoP via the Polkadot App's onboarding (the game-based PoUD flow) but the CLI's dot deploy rejected him as not having PoP. Suggests the CLI reads PoP status from a different source than where the Polkadot App writes it — or there's a propagation delay between the two.

Francisco: "It said I didn't have personhood. I do have personhood in the app because I played the games. I guess that's not hooked up yet?"

Reproduction

1. Complete PoP onboarding in the Polkadot mobile app (play the games to earn PoUD/PoP status)
2. Attempt dot deploy on a PoP-gated domain (e.g. 9-char baseName + 1 trailing digit, which requires Lite PoP)
3. Observe rejection despite Polkadot App showing PoP status

Recommended fix

Verify that dotns.getUserPopStatus(userH160) in CLI's availability.ts reads from the same chain state that Polkadot App writes to. If they're separate sources, sync them. If propagation delay, add a retry loop with a friendly message:

"Verifying your personhood status — this can take a few seconds."

Note: could be the root cause of multiple B1 reports.

[ottovlotto]

Automated comment: related to #259 from the DevEx Audit (External, 3 June 2026). Audit hit the same NoStatus rejection — useful additional repro for the PoP-status alignment investigation.