Function revoke_order 

pub async fn revoke_order(
    id: &str,
    reason: Option<u32>,
    actor: Actor,
    client: ClientContext,
    revocations: Revocations<'_>,
) -> Result<RevokeOutcome, RevokeError>

Revokes an order’s issued certificate at the signer backend and records it on the order.

actor/client say who asked and from where. Both front ends supply their own: Actor::cli with an empty ClientContext from the command line, Actor::admin with the operator’s address from the web admin. Passed in rather than derived here because this layer is deliberately front-end agnostic — it is the same reason the destructive operations come in a bare and a confirm_* form.

revocations carries the database, the auditor, the order’s profile’s dispatcher and the revoker. The revoker is what withdraws the trust — for every front end, Revoker::for_route: a local CA’s ledger, or the queue a worker drains. Neither front end holds a backend.

The operation itself is acme_proxy_protocol::acme::revoke::Revocations::revoke_order, the same tail POST /revokeCert runs; this wrapper only sorts its answers into the outcomes an operator front end reports.