fix: stabilize private zone CI auth

[brendanjryan]

Summary

• Add a private-zone e2e helper that retries authorization until the next enabled action appears.
• Use the helper across private-zone tests that depend on Zone A read authorization.
• Prevent handled zone authorization status failures from leaking as unhandled page errors.

Motivation

Private-zone CI could time out after clicking Zone A authorization when testnet auth briefly bounced back to the authorize action instead of advancing to the funding or top-up action.

Key design considerations

• Keep retry behavior inside the e2e helper so individual tests stay focused on the user flow.
• Preserve existing test timeouts and action selection behavior.
• Keep the app-side timeout wrapper scoped to clearing timers without changing authorization semantics.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tempo-docs	Ready	Preview, Comment	Jun 17, 2026 2:27pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 389a85a1cc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Reset the retry deadline after the initial button wait

When the authorize button is slow to become enabled in CI, this deadline is consumed by the preceding toBeVisible/toBeEnabled waits, so callers using the default 120s budget can have only a few seconds—or none—to click and wait for the fund/top-up/deposit action. The previous flow waited for the authorize button, clicked it, and then gave waitForEnabledAction its own 120s window, so this change can reintroduce timeouts exactly in the slow auth path it is meant to stabilize.

Useful? React with 👍 / 👎.