I had success revoking a certificate by signing the request with the account private key.
In addition, when I try to revoke the same certificate twice, I get an error, as expected.
“urn:ietf:params:acme:error:alreadyRevoked”: Certificate has already been revoked.
This “revoke twice” seems good enough for testing. I agree that implementing OCSP in Pebble might not be worth the effort.
It is making sense to move on to testing a new ACME client with Boulder (or the staging server) to be able to revoke and then check certificate status through OCSP.