Adom TTS: Text to Speech

@@ -137,6 +137,9 @@ threads) and gets confused about WHO said WHAT. Two mechanisms, keep both:      ease; it does not blink per heartbeat).   4. The header shows the human WHO (thread) + WHAT (desc) — never a raw mp3      filename except in a tooltip.+  5. NO EMOJIS in READMEs or skills, ever (user rule: they read as childish).+     Plain typographic marks are fine; the only pictograph-adjacent characters+     allowed are inside verbatim quotes of actual CLI output. - Don't churn the player while the user is listening. Diagnose from logs; the   system self-heals. Manual mid-playback intervention has itself caused   user-audible chaos.

@@ -12,7 +12,6 @@     "audio",     "demo",     "accessibility",-    "cli",     "open-source",     "mit"   ],@@ -65,17 +64,5 @@   ],   "install": {     "binary_name": "adom-tts"-  },-  "description": "Adom's shared text-to-speech CLI + Playground. Reads your AI answers back to you while driving, and renders perfectly-timed voiceover tracks for demo videos.",-  "dependencies": {},-  "scripts": {-    "install": "./install.sh",-    "uninstall": "./uninstall.sh"-  },-  "needs_sudo": false,-  "org": "adom",-  "author": {-    "name": "John Lauer",-    "email": "[email protected]"   } }\ No newline at end of file

@@ -70,7 +70,8 @@ description: >-    adom-desktop --target <laptop> browser_screenshot '{"sessionId":"wiki-check"}'   # read the PNG it saves    ```    Check: version, hero renders, Skills tab shows User + Dev + Publish tiers,-   README intact, Install command correct.+   README intact, Install command correct, and NO EMOJIS anywhere in the README+   or skills (user rule — plain typographic marks only).  7. **Prove playback end-to-end** (the release isn't done until a human can    hear it):