[Ardem2025]

Summary

Excludes the transient substring "verify your account to continue" from ACCOUNT_DEACTIVATED_SIGNALS in open-sse/services/accountFallback.ts and aligns security documentation in docs/security/BAN_DETECTION.md.

Problem & Root Cause

When Antigravity / Google Cloud Code issues a 403 response requiring intermittent account verification or browser challenge (such as "verify your account to continue"), OmniRoute previously matched this substring under ACCOUNT_DEACTIVATED_SIGNALS.

This resulted in:

1. Classifying the error as a fatal, permanent account deactivation (testStatus: "banned").
2. Applying an immediate 365-day cooldown penalty (Date.now() + 365 * 24 * 60 * 60 * 1000).
3. Disabling all accounts experiencing transient challenges and causing cascading fallback failures across multi-provider combos.

Verification prompts from Cloud Code / Antigravity are transient security checkpoints or challenge prompts that should route through normal rate-limiting / retry or account cooldown, rather than permanent 1-year deactivations.

Changes Made

1. open-sse/services/accountFallback.ts:
   • Removed "verify your account to continue" from ACCOUNT_DEACTIVATED_SIGNALS.
2. docs/security/BAN_DETECTION.md:
   • Updated built-in keywords count from 8 to 7.
   • Removed "verify your account to continue" from the active deactivation keywords table.
3. tests/unit/account-fallback-service.test.ts:
   • Added regression test: isAccountDeactivated does NOT treat transient 'verify your account to continue' as permanent deactivation.

Verification & Testing

• Unit test suite passed cleanly via Node.js test runner:

  node --import tsx/esm --test tests/unit/account-fallback-service.test.ts

• Verified that "verify your account to continue" returns false under isAccountDeactivated(), preventing false-positive 1-year bans while genuine deactivation signals ("this service has been disabled in this account") continue to be caught as expected.

[diegosouzapw]

Thank you @Ardem2025! Excluding the transient "verify your account to continue" challenge from the permanent-ban list landed on release/v3.8.51 via #14848 (open-sse/services/accountFallback.ts, see the note above ACCOUNT_DEACTIVATED_SIGNALS). Closing as covered — thanks for flagging it.