docs: address CodeRabbit review feedback (3 findings)

- README.md: wrap the Windows MSIX Claude Desktop config in PRE-PYPI
  markers so pre-PyPI readers get the --from git+... form alongside the
  post-PyPI survivor (mirrors the lines 157-188 pattern).
- docs/launch/show-hn.md: add a concrete "Demo query" line to both the
  pre-PyPI feedback draft and the post-PyPI Show HN draft, using
  asyncio.TaskGroup on Python 3.13 as the example.
- docs/launch/reddit-posts.md: add an r/ClaudeAI launch variant
  alongside r/Python and r/LocalLLaMA, leaning on the Claude Desktop /
  Claude Code MCP integration angle as the audience-specific hook.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ayhammouda

README.md

@@ -439,6 +439,25 @@ uv cache clean python-docs-mcp-server
 The MSIX-packaged version of Claude Desktop on Windows may have restricted PATH
 access. If `uvx` is not found, specify the full path in your config:
 
+<!-- PRE-PYPI: remove the GitHub-source config and the "After PyPI publishing, use:" lead-in after the first PyPI publish; the post-PyPI config fence below survives -->
+```json
+{
+  "mcpServers": {
+    "python-docs": {
+      "command": "C:\\Users\\YOU\\.local\\bin\\uvx.exe",
+      "args": [
+        "--from",
+        "git+https://github.com/ayhammouda/python-docs-mcp-server.git",
+        "python-docs-mcp-server"
+      ]
+    }
+  }
+}
+```
+
+After PyPI publishing, use:
+<!-- /PRE-PYPI -->
+
 ```json
 {
   "mcpServers": {

docs/launch/reddit-posts.md

@@ -72,3 +72,39 @@ uvx --from git+https://github.com/ayhammouda/python-docs-mcp-server.git python-d
 
 I'd appreciate practical feedback from people wiring MCP into local coding
 workflows.
+
+## r/ClaudeAI
+
+> Reminder: do not post until the package is published on PyPI and the release
+> smoke test passes (see top-of-file gate).
+
+Title: Local MCP server that gives Claude precise Python stdlib docs
+
+I built `python-docs-mcp-server`, a small read-only MCP server that drops into
+Claude Desktop or Claude Code and gives Claude exact access to the official
+Python standard library documentation.
+
+It runs on Python 3.12+ and indexes docs for Python 3.10 through 3.14.
+
+Why I built it:
+
+- Claude is strong on Python but answers can drift between stdlib versions
+- generic docs MCP servers pull in noise from broad web sources
+- I wanted Claude to retrieve one official stdlib section, not a whole page
+- the MCP tools are read-only, so the operational story is boring
+
+How I use it: I ask Claude things like "in Python 3.13, what does
+`asyncio.TaskGroup` change vs older asyncio patterns?" and it retrieves the
+exact section from the official 3.13 docs instead of guessing from generic
+web results.
+
+Repo: https://github.com/ayhammouda/python-docs-mcp-server
+
+PyPI publishing is still being finalized. For now, test from source:
+
+```bash
+uvx --from git+https://github.com/ayhammouda/python-docs-mcp-server.git python-docs-mcp-server --version
+```
+
+Feedback welcome on Claude Desktop / Claude Code MCP config, retrieval
+quality, and which stdlib lookups feel clunky in real use.

docs/launch/show-hn.md

@@ -28,6 +28,10 @@ What it does:
 - supports version-aware lookup across Python 3.10 through 3.14
 - runs locally, read-only, with no API keys
 
+Demo query:
+
+- "In Python 3.13, what does `asyncio.TaskGroup` change compared to older asyncio patterns?"
+
 It is intentionally narrow. Use Context7 or generic retrieval for broad
 third-party docs and web research. Use this when you want official stdlib docs
 with less token waste.
@@ -68,6 +72,10 @@ What it does:
 - supports version-aware lookup across Python 3.10 through 3.14
 - runs locally, read-only, with no API keys
 
+Demo query:
+
+- "In Python 3.13, what does `asyncio.TaskGroup` change compared to older asyncio patterns?"
+
 Repo: https://github.com/ayhammouda/python-docs-mcp-server
 
 First run after the PyPI release: