[urbit] Debugging tool: event blocks tracing

[Anton Dyudin]

Tractability status: pipe dream

---

Something I frequently find myself doing is staring at a %dy-no-prompt
console, and wondering what it's waiting for behind the scenes. Now, arvo
knows what's going on behind the scenes: every vane has some combination of
data structures that map ducts to various data, and possibly opaque
identifiers(gall bones, eyre sessions) back to ducts. If one were to go
through all ducts in vanes' possession, pull out any that were caused by a
specific source(an http request, or a freshly-created console), and sort
the results lexicographically, you'd get a fairly thorough idea of what
could cause responses to the given source event.

Bonus points for exposing metadata, such as "this duct was found in a jug
of listeners to notify if this clay path updates". Bonus bonus point for
dealing with indirection, e.g. "this duct maps to a bone, let's add
anything associated with that bone to the trace."