Ecosystem follow-up work

[pboothe]

The package builds and its CI is green, but it is not on PyPI (the name triplepat-syntheticalert is unclaimed as of 2026-09-04) and nothing is tagged. This issue collects the work that puts it into the Python ecosystem. All publishing waits for go-syntheticalert to prove out in production.

Publishing

• Claim triplepat-syntheticalert on PyPI (and TestPyPI for a dry run).
• Set up PyPI trusted publishing (OIDC from GitHub Actions) for this repo, so no long-lived token exists.
• Add a release workflow triggered by a v* tag: uv build, uv publish, GitHub Release with notes drafted for founder review first. Notes describe the module for a first-time reader.
• First tag only after the API settles; bump Development Status from Alpha at that point.
• Verify the published wheel installs into a clean venv on 3.10 through 3.14 and that py.typed is honoured by mypy in a consumer project.
• Add the PyPI version badge to the README.

Deployment recipes

• Run the README's gunicorn recipe in a real gunicorn deployment (not the local demo) and confirm the master-driven livemostrecent gauge survives worker restarts and a HUP reload.
• Decide whether uWSGI deserves a recipe or a sentence saying to use a sidecar.
• Consider a tiny example repo or gist for the gunicorn wiring that people can clone.

Discoverability

• Submit to the OpenTelemetry Registry as an instrumentation library.
• Ask for a listing on the Prometheus "Exporters and integrations" page, or decide it does not fit.

Housekeeping

• Dependabot or Renovate for the dev dependency group and GitHub Actions versions.
• Re-check the CI matrix when Python 3.15 ships.