chore: align launch pack with package rename

Author: ayhammouda

.github/INTEGRATION-TEST.md

@@ -13,9 +13,9 @@ Release-specific sign-off still lives in [`.github/RELEASE.md`](RELEASE.md).
   - `uv run pyright src/`
   - `uv run pytest --tb=short -q`
 - Local index build completed:
-  - `uv run mcp-server-python-docs build-index --versions 3.10,3.11,3.12,3.13,3.14`
+  - `uv run python-docs-mcp-server build-index --versions 3.10,3.11,3.12,3.13,3.14`
 - Doctor passes:
-  - `uv run mcp-server-python-docs doctor`
+  - `uv run python-docs-mcp-server doctor`
 - Slow E2E workflow passes when preparing a release:
   - GitHub Actions: `Slow E2E`
   - Expected: Python 3.13 and 3.14 jobs both complete `build-index`, `doctor`,
@@ -29,7 +29,7 @@ Use Inspector for fast local iteration before checking real clients.
 ### Start Inspector
 
 ```bash
-npx @modelcontextprotocol/inspector uv --directory . run mcp-server-python-docs
+npx @modelcontextprotocol/inspector uv --directory . run python-docs-mcp-server
 ```
 
 ### Verify
@@ -62,7 +62,7 @@ npx @modelcontextprotocol/inspector uv --directory . run mcp-server-python-docs
   "mcpServers": {
     "python-docs": {
       "command": "uvx",
-      "args": ["mcp-server-python-docs"]
+      "args": ["python-docs-mcp-server"]
     }
   }
 }
@@ -90,7 +90,7 @@ npx @modelcontextprotocol/inspector uv --directory . run mcp-server-python-docs
 2. Add a server:
    - Name: `python-docs`
    - Command: `uvx`
-   - Args: `mcp-server-python-docs`
+   - Args: `python-docs-mcp-server`
 3. Confirm the server shows as connected
 
 ### Checks
@@ -111,11 +111,11 @@ locked.
 
 ### Checks
 
-- [ ] `uvx mcp-server-python-docs --version`
+- [ ] `uvx python-docs-mcp-server --version`
   - Expected: prints the current package version
-- [ ] `uvx mcp-server-python-docs build-index --versions 3.10,3.11,3.12,3.13,3.14`
+- [ ] `uvx python-docs-mcp-server build-index --versions 3.10,3.11,3.12,3.13,3.14`
   - Expected: index build completes successfully
-- [ ] `uvx mcp-server-python-docs doctor`
+- [ ] `uvx python-docs-mcp-server doctor`
   - Expected: all required checks pass
 - [ ] Follow the README from scratch
   - Expected: a new user can get to a working client configuration without using `.planning/`
@@ -130,7 +130,7 @@ or supported Python versions.
 - [ ] Start the `Slow E2E` workflow from GitHub Actions
   - Expected: both Python 3.13 and Python 3.14 jobs start
 - [ ] Confirm each job installs the built wheel into a clean virtual environment
-  - Expected: the command path is the installed `mcp-server-python-docs`, not editable source
+  - Expected: the command path is the installed `python-docs-mcp-server`, not editable source
 - [ ] Confirm `build-index --versions 3.10,3.11,3.12,3.13,3.14` passes
   - Expected: all five versions produce content, not symbol-only fallback
 - [ ] Confirm `doctor` and `validate-corpus` pass

.github/RELEASE.md

@@ -6,7 +6,7 @@ Before the first release, configure PyPI Trusted Publishing:
 
 1. Go to https://pypi.org/manage/account/publishing/
 2. Add a new pending publisher:
-   - **PyPI project name**: `mcp-server-python-docs`
+   - **PyPI project name**: `python-docs-mcp-server`
    - **Owner**: your GitHub username or org
    - **Repository**: `python-docs-mcp-server`
    - **Workflow name**: `release.yml`
@@ -54,19 +54,19 @@ versions 3.10 through 3.14.
    https://github.com/<owner>/python-docs-mcp-server/actions/workflows/release.yml
 
 5. Verify the package on PyPI:
-   https://pypi.org/project/mcp-server-python-docs/0.1.1/
+   https://pypi.org/project/python-docs-mcp-server/0.1.1/
 
 ## Post-Release Verification
 
 After the package is published:
 
 ```bash
 # In a fresh environment:
-uvx mcp-server-python-docs --version
+uvx python-docs-mcp-server --version
 # Should print: 0.1.1
 
 # Or via pipx:
-pipx run mcp-server-python-docs --version
+pipx run python-docs-mcp-server --version
 # Should print: 0.1.1
 ```
 
@@ -88,13 +88,13 @@ Complete these steps in order. Each step has a checkbox -- do not skip ahead.
 - [ ] Integration tests from `.github/INTEGRATION-TEST.md` are complete and signed off
 - [ ] Doctor subcommand passes:
   ```bash
-  mcp-server-python-docs doctor
+  uv run python-docs-mcp-server doctor
   ```
 
 ### PyPI Trusted Publishing Setup (one-time)
 
 - [ ] PyPI pending publisher configured at https://pypi.org/manage/account/publishing/:
-  - PyPI project name: `mcp-server-python-docs`
+  - PyPI project name: `python-docs-mcp-server`
   - Owner: `<your-github-username>`
   - Repository: `python-docs-mcp-server`
   - Workflow name: `release.yml`
@@ -107,12 +107,12 @@ Complete these steps in order. Each step has a checkbox -- do not skip ahead.
   ```bash
   git tag -a v0.1.1 -m "Release v0.1.1
 
-  First public release of mcp-server-python-docs.
+  First public release of python-docs-mcp-server.
 
   A read-only, version-aware MCP retrieval server over Python
   standard library documentation (3.10 through 3.14).
 
-  Installable via: uvx mcp-server-python-docs"
+  Installable via: uvx python-docs-mcp-server"
   ```
 - [ ] Push the tag to trigger the release workflow:
   ```bash
@@ -123,29 +123,29 @@ Complete these steps in order. Each step has a checkbox -- do not skip ahead.
 
 ### Post-Release Verification (SHIP-06)
 
-- [ ] Package visible on PyPI: https://pypi.org/project/mcp-server-python-docs/0.1.1/
+- [ ] Package visible on PyPI: https://pypi.org/project/python-docs-mcp-server/0.1.1/
 - [ ] Attestation visible on PyPI package page (look for "Provenance" badge)
 - [ ] Fresh install test:
   ```bash
   # Clear any cached version
-  uv cache clean mcp-server-python-docs 2>/dev/null || true
+  uv cache clean python-docs-mcp-server 2>/dev/null || true
 
   # Install and verify version
-  uvx mcp-server-python-docs --version
+  uvx python-docs-mcp-server --version
   # Expected output: 0.1.1
   ```
 - [ ] Full README flow test (from a clean environment):
   ```bash
   # Step 1: Install
-  uvx mcp-server-python-docs --version
+  uvx python-docs-mcp-server --version
   # Should print 0.1.1
 
   # Step 2: Build index
-  uvx mcp-server-python-docs build-index --versions 3.10,3.11,3.12,3.13,3.14
+  uvx python-docs-mcp-server build-index --versions 3.10,3.11,3.12,3.13,3.14
   # Should complete successfully
 
   # Step 3: Doctor check
-  uvx mcp-server-python-docs doctor
+  uvx python-docs-mcp-server doctor
   # All checks should PASS
   ```
 - [ ] Slow E2E workflow passes:
@@ -154,15 +154,44 @@ Complete these steps in order. Each step has a checkbox -- do not skip ahead.
   - Confirm each job installs the built wheel, runs
     `build-index --versions 3.10,3.11,3.12,3.13,3.14`, `doctor`, and
     `validate-corpus`
+
+### Post-PyPI Launch Pack Cleanup
+
+- [ ] Remove every temporary PyPI pre-release block from `README.md`:
+  - Delete each `<!-- PRE-PYPI: ... -->` through `<!-- /PRE-PYPI -->` region,
+    including the marker comments and GitHub-source replacement commands
+  - Remove or rewrite stale "Before PyPI publishing" headings, "Until the first
+    PyPI release is published" text, and "After PyPI publishing" qualifiers
+  - Make the published package commands (`uvx python-docs-mcp-server ...`) the
+    primary install, build-index, MCP client, `doctor`, and `validate-corpus`
+    examples
+- [ ] Verify `README.md` has no temporary pre-release install artifacts:
+  ```bash
+  rg -n 'PRE[-]PYPI|Before PyPI publishing|Until the first PyPI|After PyPI publishing|git\\+https://github.com/.*/python-docs-mcp-server' README.md
+  ```
+  The command should return no output.
+- [ ] Review `docs/launch/` so no public launch copy still asks users to install
+  from GitHub source after the PyPI package is available. Intentional historical
+  pre-release drafts may remain, but they must stay clearly labeled as
+  pre-PyPI-only.
+- [ ] Submit `server.json` to https://registry.modelcontextprotocol.io/ via the
+  `mcp-publisher` CLI after the PyPI smoke test passes; verify the registry
+  listing appears and points at version 0.1.1
+- [ ] Use the post-PyPI draft in `docs/launch/show-hn.md` for the HN submission
+- [ ] Use `docs/launch/reddit-posts.md` for the r/Python and r/LocalLLaMA
+  submissions after the PyPI release smoke test passes
+- [ ] Commit and push the README cleanup before public launch posts go out
+
 - [ ] Claude Desktop test with published package:
-  Configure `mcpServers` with `uvx mcp-server-python-docs` and verify
+  Configure `mcpServers` with `uvx python-docs-mcp-server` and verify
   "what is asyncio.TaskGroup" returns a correct hit
 
 ### Release Complete
 
 - [ ] GitHub Release exists with attached artifacts
 - [ ] PyPI page shows 0.1.1 with attestation
 - [ ] README install instructions verified end-to-end
+- [ ] README no longer contains temporary pre-PyPI GitHub-source install blocks
 - [ ] Slow E2E workflow passed for the release candidate
 - [ ] Tag v0.1.1 exists in git
 

.github/workflows/e2e.yml

@@ -33,18 +33,18 @@ jobs:
           uv run --python ${{ matrix.python-version }} python -m venv .e2e-venv
           .e2e-venv/bin/python -m pip install --upgrade pip
           .e2e-venv/bin/python -m pip install dist/*.whl
-          .e2e-venv/bin/mcp-server-python-docs --version
+          .e2e-venv/bin/python-docs-mcp-server --version
 
       - name: Build and validate full docs index
         env:
           HOME: ${{ runner.temp }}/mcp-python-docs-home
           XDG_CACHE_HOME: ${{ runner.temp }}/mcp-python-docs-cache
         run: |
           set -o pipefail
-          .e2e-venv/bin/mcp-server-python-docs build-index --versions 3.10,3.11,3.12,3.13,3.14 \
+          .e2e-venv/bin/python-docs-mcp-server build-index --versions 3.10,3.11,3.12,3.13,3.14 \
             2>&1 | tee "${RUNNER_TEMP}/build-index-${{ matrix.python-version }}.log"
-          .e2e-venv/bin/mcp-server-python-docs doctor
-          .e2e-venv/bin/mcp-server-python-docs validate-corpus
+          .e2e-venv/bin/python-docs-mcp-server doctor
+          .e2e-venv/bin/python-docs-mcp-server validate-corpus
 
       - name: Upload E2E logs and cache artifacts
         if: always()

AGENTS.md

@@ -2,7 +2,7 @@
 
 ## Project
 
-`mcp-server-python-docs` is a read-only MCP server for the official Python
+`python-docs-mcp-server` is a read-only MCP server for the official Python
 standard library documentation. It is built for end users who want precise,
 version-aware stdlib answers inside MCP clients such as Claude, Cursor, and
 Codex without relying on an external hosted docs API at query time.
@@ -39,9 +39,9 @@ uv run pytest --tb=short -q
 Build and inspect a local docs index:
 
 ```bash
-uv run mcp-server-python-docs build-index --versions 3.12,3.13
-uv run mcp-server-python-docs doctor
-uv run mcp-server-python-docs validate-corpus
+uv run python-docs-mcp-server build-index --versions 3.12,3.13
+uv run python-docs-mcp-server doctor
+uv run python-docs-mcp-server validate-corpus
 ```
 
 Package smoke check:

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to mcp-server-python-docs
+# Contributing to python-docs-mcp-server
 
 Start here for current contributor workflow. You should not need `.planning/`
 to set up, test, or validate the repo.
@@ -42,9 +42,9 @@ uv run pytest tests/test_retrieval_regression.py -q
 The server needs a local SQLite index before runtime validation:
 
 ```bash
-uv run mcp-server-python-docs build-index --versions 3.10,3.11,3.12,3.13,3.14
-uv run mcp-server-python-docs doctor
-uv run mcp-server-python-docs validate-corpus
+uv run python-docs-mcp-server build-index --versions 3.10,3.11,3.12,3.13,3.14
+uv run python-docs-mcp-server doctor
+uv run python-docs-mcp-server validate-corpus
 ```
 
 `build-index` downloads the symbol inventories, clones CPython docs sources,