AuthOtpController::verify() accepted a constant '0000' in the mode every instance
shipped with, and minted a Sanctum token with ability 'mobile:*' for whichever
active user matched the submitted phone number — staff included. The routes were
deleted in 883391c7, so the tokens reach nothing today, but a credential that was
issuable without authentication should not sit in the table waiting for the next
surface that accepts Sanctum.

Every client gets this, so it is a migration rather than an SSH per instance.
Two such rows exist on the one instance that used the API; the others have none,
and the table guard covers instances that never ran Sanctum's migration.

Deleting rows in up() is a deliberate exception to "destructive operations live
in down() only" — that rule protects schema and client data, and this is neither.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>