fix(workflow): add explicit guidance to avoid chapter-specific mentions

- AVOID: Specific chapter names, topic names, section titles
- GOOD: Generic terms like 'Enhanced visualizations', 'Improved explanations'
- BAD: 'Deep Learning Primer', 'Data Engineering chapter', 'Chapter 3 updates'
- Chapter-level details belong in changelog, not release notes
- Provides clear examples of what to avoid vs what to include

.github/workflows/publish-live.yml

@@ -1180,7 +1180,9 @@ jobs:
                 echo "- Infrastructure: 3-5 most significant reliability/performance improvements users notice"
                 echo "- Use straightforward, academic language (no marketing terms)"
                 echo "- Be factual and direct - state what improved, not how amazing it is"
-                echo "- Avoid specific chapter numbers or technical implementation details"
+                echo "- AVOID: Specific chapter names, topic names, or section titles (use generic terms)"
+                echo "- GOOD: 'Enhanced visualizations', 'Improved explanations', 'Updated examples'"
+                echo "- BAD: 'Deep Learning Primer', 'Data Engineering chapter', 'Chapter 3 updates'"
                 echo "- Write like a scholarly publication announcement, not marketing material"
               } > ai_prompt.txt