The information one gets when running a test using Debugger.withDebugger is much too hard to understand, and even then lacks sufficient detail to really see what is happening.
First, this is not a debugger, it's a trace facility, so we should call it Debugger.withTrace at least.
We need to improve this by adding in the ability to watch delimiter scanning actions as they succeed and fail as part of what the debugger/trace displays.
We also need indentation or some other means to determine nesting level. (Putting a level/depth number along the left edge may be enough.)
We also need ways to get finer granularity control rather than running it over the entire execution of the parser. This could be done by putting daf:trace properties of some sort on the parts of the schema of interest, or by supplying paths to schema components of interest for tracing. The trace facility would then turn on when that component was entered, and off when it was exited.
There are other options as well: turn on/off one of text or hex dumps. If data is all text, you probably never want to see the hex, and binary data, you may not want to bother with the text.