How hard a revocation key like in #gpg, but for schnorr?

It's been discussed for years, both key rotation and revocation. There are problems with race conditions.

The real problem isn't killing a leaked key — it's that Nostr has no concept of key revocation with temporal scope. Right now you can: 1. Post a replacement event (kind 0) — but clients may cache the old one 2. Burn the key (publish a signed "compromised" statement) — but nothing enforces it ...