Add glossary hover presentation

README.md

@@ -67,7 +67,7 @@ Major modules:
 
 - `module-registry.js`, `base-module.js`, `loader.js`: module lifecycle, dependency graph, progress overlay, state reporting.
 - `text-processor-module.js`, `paragraph-layout-module.js`, `layout-renderer-module.js`: SmartyPants, language-aware hyphenation, Knuth-Plass line breaking, DOM rendering.
-- `markup-parser-module.js`: story markup fallback for chapters, sections, Markdown emphasis, images, SFX, and music.
+- `markup-parser-module.js`: story markup fallback for chapters, sections, Markdown emphasis, right-page glossary notes, images, SFX, and music.
 - `sentence-queue-module.js`, `playback-coordinator-module.js`, `animation-queue-module.js`: sentence preparation, synchronized playback, timing, fast-forward.
 - `tts-factory-module.js` plus provider modules: TTS provider selection, voice settings, speed mapping, caching, and playback.
 - `audio-manager-module.js`: master, speech, music, and sound effect volume, music playback, sound effects, and music ducking.
@@ -88,6 +88,15 @@ Inline Markdown emphasis:
 ***bold italic*** or ___bold italic___
 ```
 
+Right-page glossary notes:
+
+```text
+The train stops at Eibenreith.
+#gloss[Eibenreith](A fictional alpine town in the Kaiserpunk setting.)
+```
+
+Glossary markup is a normal story tag scoped to the paragraph/block it is attached to. The UI finds every matching visible instance of the term in that right-page block and adds a hover/focus note. The tag itself is not displayed, is not sent to TTS, and is ignored by choices and command history. Avoid raw Ink control characters in the explanation; `|`, `{`, and `}` must be escaped in Ink as `\|`, `\{`, and `\}` if they are needed literally.
+
 Canonical block/media/control tags use Ink-style `#` syntax. In Ink these are real Ink tags. In YAML and Zork narrative output, leading `#...` lines are parsed by the server into the same structured `StoryTag` objects before reaching the client. The browser only consumes structured `TurnResult` objects.
 
 Tag format:
@@ -180,7 +189,7 @@ The renderer is designed to behave like a scaled static book page. The page keep
 Text processing order:
 
 1. Parse story markup and remove non-display media markers.
-2. Apply Markdown emphasis spans.
+2. Apply Markdown emphasis spans and right-page glossary annotations.
 3. Run SmartyPants for typographic punctuation.
 4. Apply Hyphenopoly for the selected language.
 5. Calculate line breaks with the Knuth-Plass algorithm.