Writing into being.
Debug80 regenerated its debug maps on every session start even when the underlying source had not changed. I added content-hash based caching to skip redundant work then tackled two quality-of-life improvements: auto-opening source files plus consolidating the memory panel.
When debugging user programs on the TEC-1 I kept hitting a wall at ROM boundaries. The debugger could step through my code but the moment execution jumped into the monitor ROM the source view went dark. I fixed that by teaching Debug80 to load external listings then build source maps from assembly files at session start.
I built a TEC-1 memory panel so the debugger could show live memory state without guesswork. This entry explains the snapshot request and the windowing rules, then shows how the panel grew into a multi-view dashboard with symbol context.
Debug80 treats assembler listings as primary data and uses them to build explicit mappings between source code and runtime execution.
Debug80 integrates a JavaScript Z80 assembler with VS Code’s debugging infrastructure to create a coherent environment for building and observing Z80 programs.