Revokes a session. The bearer's own session is the only path accepted on this endpoint at the v3 layer; deleting other sessions requires admin tooling. Revocation propagates to all servers within about 60 seconds.
Replay semantics: after a successful revoke, the bearer can no longer authenticate, so a retried DELETE returns 401 — clients MUST treat 401 on a retried DELETE as logout success. A 204 on replay can occur briefly while the revocation propagates. Idempotency-Key is NOT required because the post-condition ("the session is gone") is itself the idempotency anchor.