Here ya go, @chromalchemy. Thanks for the suggestion, this could be useful to adoption. I extended the static HTML to have a second DIV, then added a "Debug" button that injects a second matrix's DOM into that DIV. It is really a toggle, click it again and it clears the DIV and shuts down the second matrix. The debug matrix reactively follows the whole structure of the "MX Multi" exercise, and when I click on the :spelling tag its onclick handler reactively mutates that DIV's style so it turns yellow. Toggling the debug panel on and off goes well, which is significant because that requires clean quiescence of the matrix as well as resurrection.
Btw, I might have said that the app exercise itself is a simple one that simply demonstrates reactive change of the DOM, with a "spelling" widget having one span for each letter in the inout word. The "debug" panel just renders the resulting DOM hierarchy as a DOM tree of its own.
Wow, nice! Looking forward to try it out.
Ha-ha, it occurred to me that I had removed any hard-coding by the time I was done, so the "debugger" works on any of the exercises. If I change exercises with the debugger open, that works, too. The one thing semi-hardcode was the one widget turning yellow when clicked in the debugger. I would have to make the DOM style attribute manipulation a bit fancier, but for now I feel good about multiple MXs per app page as well as injection into arbitrary vanilla HTML DOM.