Currently, the dropDatabase command returns a bare { ok: 1 } reply regardless of whether the database actually existed, for idempotency purposes.

This means callers have no way to distinguish between "the database was dropped" and "the database never existed in the first place."

We could investigate enriching the reply with an additional field, e.g.: { ok: 1, dropped: true/false }