chore: prepare package for PyPI publication as "useprimer"

[ccf]

Summary

The PyPI name primer is already taken by a 2015 prime-numbers library, so this PR preps the package to publish as useprimer — matching the domain. The Python module stays primer (same pattern as PyYAML → yaml), so import primer and the primer CLI entry point are unchanged.

Once published, the PyPI project page surfaces the six [project.urls] entries as inbound links from pypi.org — a very high-trust domain. That's the SEO signal we need to help accelerate Google indexing of useprimer.dev (on top of the developer-distribution benefit).

pyproject.toml

• Rename [project] name → "useprimer"
• Add readme, license, authors, maintainers, keywords, classifiers
• Add [project.urls] → Homepage, Documentation, Repository, Issues, Changelog, Live Demo
• Add [tool.hatch.build.targets.wheel] packages = ["src/primer"] so hatch finds the module under the new project name
• Add [tool.hatch.build.targets.sdist] include = [...] for a proper sdist

README.md

• Update install command: pip install primer → pip install useprimer (with note that the Python module is still primer)

PUBLISHING.md (new)

• Token setup (PyPI + TestPyPI)
• Release workflow (build → twine check → TestPyPI rehearsal → PyPI upload → tag/push)
• Verification steps

Test plan

• python -m build produces useprimer-0.2.0-py3-none-any.whl
• Wheel contents include primer/ module + primer/_alembic/ migrations
• METADATA file contains all 6 Project-URL entries
• python -c "import primer; print(primer.__name__)" → primer
• pytest tests/test_hook_installer.py tests/test_hook_session_end.py → 43 passed

Follow-up (not in this PR)

Actually publishing requires a PyPI account + API token (documented in PUBLISHING.md). The first upload from a clean account will also need to go through TestPyPI first to verify the rendered project page looks right before committing the public name.

🤖 Generated with Claude Code

---

Note

Low Risk
Mostly packaging/metadata changes for PyPI plus docs; runtime behavior should be unchanged, with the main risk being a misconfigured build that omits modules/migrations or breaks version reporting.

Overview
Prepares the project for PyPI publication under the new distribution name useprimer while keeping the import/CLI name primer.

Updates pyproject.toml with the new project name, richer package metadata and project.urls, and Hatch build config to explicitly include src/primer plus sdist contents. The CLI’s --version lookup is switched to package_name="useprimer", and the README/install docs are updated accordingly, with a new PUBLISHING.md documenting the release workflow.

^{Reviewed by Cursor Bugbot for commit 9ce8da9. Bugbot is set up for automated code reviews on this repo. Configure here.}