Publish to PyPI as conflens on release

[picaultj]

Summary

Sets up automatic PyPI publishing (integrated into the existing release automation), makes the pip-installed CLI pick up a local .env, and documents installation + configuration.

Packaging verified: uv build → wheel + sdist with every conflens submodule; installed into a clean Python 3.13 venv, conflens/conference-analyzer scripts work, imports resolve from site-packages, and the installed conflens boots the app (HTTP 200).

Publishing

• pyproject.toml — distribution renamed to conflens (both names were free on PyPI). Import name + CLI unchanged; pip install conflens. uv.lock re-locked.
• .github/workflows/release.yml — after the existing bump + tag, the same job runs uv build then uvx twine upload --skip-existing dist/* (__token__ / secrets.PYPI_API_TOKEN), gated on a released output so it only runs when a new version is cut. Publishing lives inside the release job because GITHUB_TOKEN-pushed tags don't trigger a separate tag-based workflow.

Environment variables (installed CLI)

conflens takes config three ways, in precedence order:

1. Real environment variables (export ANTHROPIC_API_KEY=…) — always work.
2. A .env in the directory you launch conflens from — loaded automatically.
3. The in-app "API key" field — at runtime.

Fix: the old _load_env() called load_dotenv(), which searches from the installed package location, so a pip-installed conflens never picked up a .env in the user's working directory (only real env vars worked). Now it uses find_dotenv(usecwd=True) to search the working directory. Real env vars still take precedence over .env. OpenReview creds (OPENREVIEW_TOKEN, or OPENREVIEW_USERNAME + OPENREVIEW_PASSWORD) work the same way or via the in-GUI fields.

Docs

• README — pip install conflens quick start; a Configuration section explaining env var / .env-in-run-dir / in-app field (+ OpenReview); the PYPI_API_TOKEN secret under Releasing.
• Badges — switched to PyPI stats (pypi version, pepy.tech downloads, pypi pyversions) in place of the GitHub release/downloads/static-python badges, mirroring BERTrend. (These render as "not found" until the first PyPI release populates them.)

Testing

• Clean-installed the renamed wheel → conflens 0.1.13, conflens --help works.
• New tests/test_cli.py: .env-from-cwd is loaded, no-.env is a no-op, real env var overrides .env.
• release.yml valid YAML; steps: Bump → Build → Publish.
• ruff clean · pytest 76 passed.

⚠️ One-time setup you must do

1. Create a PyPI API token (account-scoped for the first upload since the project doesn't exist yet; narrow to conflens afterward).
2. Add it as repo secret PYPI_API_TOKEN (Settings → Secrets and variables → Actions).

Then the next merged PR bumps the version and publishes conflens to PyPI automatically. (Happy to add a TestPyPI workflow_dispatch dry-run if you want to validate the token before the first real release.)