An aside was planned as a dedicated tool, an awkward seam that stopped the DM mid-story to commit secret canon. The DM now writes an aside as a fenced code block tagged aside inside its narration, the way it writes a map or a letter. The markdown renderer recognizes the tag structurally, drains the block and renders nothing, and the prose before and after keeps printing with no spurious blank row. The transcript still records the raw narration verbatim, so the secret stays timestamped and provable. Because an aside is now narration it rides the bus, so the scanner catches its wikilinks for free and replay routes it to the DM without extra plumbing; a later map or item fence uses the same seam. A base-system section teaches the form, and the roadmap notes that a growing entity can be promoted to a directory so extracted maps get files of their own. The plan marks the form and renderer steps done.