Put one account back together as a labeling physician, in a single call.

The repair is four writes across three screens — role, tier, verification, real-data approval — and an account filed under an operator role is on NONE of those screens, so the sequence could not be started from the console at all. Every step here is reachable through its own route; what this adds is that they can be done in one action on an account the UI cannot reach, and that the response says what each one did.

Nothing is implicit. approve_verification is a credentialing decision and is off by default; when set, it is recorded as a human decision by the calling admin (verified_by), exactly as the queue would. Real-data approval is never set directly — it is left to the same APPROVED + LABELING policy that governs everyone else, so this endpoint cannot become a side door around it.