What's the mechanism by which *cider-inspect*'s content change when I call cider-eval-last-sexp? edit: found it, cider-auto-inspect-after-eval in cider-eval

Anyway, @bozhidar I'm bringing back my suggestion to add tap support to the inspector, turns out it's only a few lines of code

PR welcome!