[armagon]

The browser debugger is still helpful, but it isn't able to link together the cause and effects (because the code in the system was designed that way -- it doesn't matter who fires off an action, it will (eventually) make certain code happen to respond to it. But, when you see the response code go off, it can be hard to figure out what action caused it -- moreso if your codebase abstracts things like the names of strings representing actions so you can't just grep for them.)

I think some sort of higher-level debugger ought to be possible, but don't know what it would look like.