Pending identity verification can resume after an app restart, per a SQLite fixture

A hosted identity onboarding flow can lose track of a pending verification session if a deploy, crash or reschedule occurs before the provider's callback arrives. The article presents a synthetic SQLite-backed fixture in which a second process reopening the same database file sees the existing pending session, its deadline and grant count, with no duplicate session created. Duplicate callbacks are deduplicated by event ID, and a timeout recovery path handles sessions where no callback arrives. The example is local and synthetic only, does not verify real signatures or grant real permissions, and does not change live permissions. The author frames the key question as whether durable storage, not process memory, owns pending state and is read before the restarted process acts.