A second Verify says a check is already running, not "something went wrong" (SP98 T26, final review M-1)

Shipped

October 5, 2026 at 4:43 PM UTC

Author

Kamo

Commit

e64496a

AIService answers a Verify while the provider's check lease is held with 409 verify_in_progress, and one whose lease cannot be taken with 503 verify_unavailable (SP98-T1, master §11). registryErrors did not know either code, so the toast read the generic "Something went wrong. Try again.", which invites the click that 409s again. Both codes now have their own words (dictionary 943db8a7); the model capability Verify shares the mapping.