[nedtwigg]

The repo has no PyPI publish workflow. This adds one that needs no stored token, and prepares 1.0.1.

Changes

• python-deploy.yml runs manually. It checks the version, builds both packages without publish permissions, publishes through the pypi environment (selfie-lib first, since pytest-selfie depends on it), then creates the python/<version> tag and a GitHub Release.
• The GitHub Release uses --latest=false, so the latest JVM release stays as Latest.
• Both packages are now 1.0.1 with Homepage, Source, and Changelog links, which PyPI doesn't show today.

Since 1.0.0, the package changes are the leading-whitespace fix, the new URLs, and exporting EscapeLeadingWhitespace from selfie_lib.

Tested locally

• uv build --no-sources builds both, twine check passes, and wheel sizes are close to 1.0.0.
• In a clean venv, the two wheels install together, pytest loads selfie-1.0.1, and a real expect_selfie test passes.
• pytest, ruff, and pyright pass in all three projects, actionlint reports nothing on the workflow, and the version checks and release notes extraction behave as expected when run by hand.

Not tested
The workflow itself can't run from a PR, and the PyPI upload only happens in a real release.

To release after merging

1. On PyPI, add a trusted publisher to both selfie-lib and pytest-selfie: owner diffplug, repository selfie-lib, workflow python-deploy.yml, environment pypi.
2. Fast-forward release to main.
3. Run python-deploy from release and approve it.

🤖 Generated with Claude Code