Need structured offline backing of console log (and more)

[erights]

Right now when marshal serializes an error, it emits that error onto the console so that, once #2045 is in better shape, a sufficiently motivated user could track down a distributed error back to its origin. This situation has two problems. The serialization of the error, that often no one wanted to see anyway, is unnecessary noise on the console. With text as the only representation of these clues, either the user has too much work to bother with, or, if automated tools were written to help, they'd be unreliable scrapers.

Instead these errors should be sent somewhere out of vat in a structure preserving way. Causeway-like. Given adequate permissions, automatic tools should be able to stitch these clues together reliably into a pleasant developer experience. Ideally, the developer experience of distributed programming should be as fun and productive as familiar local programming.

[erights]

Hi @FUDCo I added to the assignees as I suspect the solution may involve the slogulator.

[erights]

See endojs/endo#529