[Copilot]

The fresh-wallet test’s 40-second wait exceeded its 30-second test timeout. Local traces also exposed a response-order race that prevents timeout alignment alone from stabilizing the test.

• Test-only changes

  • Set a 60-second test budget; retain the 40-second state assertion.
  • Replace text polling with diagnostic retrying assertions requiring “Whitelisting Required” and a visible Verify button.
  • Document RPC dependencies and refresh screenshot evidence.

• Product blocker

  • An obsolete address-less refresh can overwrite not_whitelisted with not_connected despite successful Celo identity reads.
  • Product behavior remains unchanged; separate authorization is needed to address the race.

• Acceptance

  • Repeated live Chromium passes: 0/3, blocked by the race.
  • Citizen Claim regressions: 5 passed without retries.
  • Dependencies documented: Celo Forno, Fuse RPC, and Ankr XDC. Historical CI logs were inaccessible; findings use local traces.

Live-RPC blocker screenshot

• Fixes [Patch] Stabilize Citizen Claim live-RPC Playwright test #268

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

[L03TJ3]

@copilot Please follow up with the minimal widget fix here.

Locally reproduced on bb05d89: the fixture auto-connects correctly and the identity read returns not_whitelisted. About 0.7 seconds later, an older addressless refresh finishes its auxiliary RPC reads and overwrites that state with not_connected. The test is valid; adding a Connect click or more timeout is not the fix.

In packages/citizen-claim-widget/src/adapter.ts, remove await auxiliaryReads from the if (!address) branch so the disconnected state is applied immediately, not after a stale async wait. This one-line proof fix passed the target test 5/5 with one worker and no retries, the full Citizen Claim states.spec.ts 5/5, scoped build and lint. A temporary 15-second observation also confirmed Verify remained visible.

Please apply this small fix and add one focused regression proving a late addressless refresh cannot overwrite the connected result. Keep this scoped; no broad refactor or unrelated edge-case work. Rerun the focused tests and report the results.

[Copilot]

@copilot Please follow up with the minimal widget fix here.

Locally reproduced on bb05d89: the fixture auto-connects correctly and the identity read returns not_whitelisted. About 0.7 seconds lat...

Addressed in 99c6572: removed the addressless branch’s await auxiliaryReads and added a deterministic regression that releases held auxiliary responses after Verify appears. It fails before the fix and passes 5/5 afterward.

With one worker and no retries: live Chromium 5/5; full Citizen Claim suite 7/7 (six state tests plus version). Scoped build/lint and spec lint pass. Verify remained visible during a 15-second live observation. Screenshots refreshed; secret scan clean; CodeQL: zero alerts. No Connect click, added timeout, or broader refactor.