[Mattral]

Version bump for 0.3.2, a bug-fix release for the acceptance-rate fix merged in #58. There is no new measurement: the
decoding path and its speed are unchanged, so the README tables stay on the 0.3.0 release run (3c43e08).

Changes

• pyproject.toml, flashspec/__init__.py, CITATION.cff (version and date-released): 0.3.2.
• CHANGELOG: [0.3.2] — 2026-10-29 — Per-call acceptance rate, with highlights, upgrade notes and known issues above
  the Fixed entries from fix: acceptance_rate per generate() call; acceptance figures from step counts #58. [Unreleased] is empty.
• The container image tag 0.3.1 → 0.3.2 in the README, docs/install.md, deploy/Dockerfile (comment),
  deploy/docker-compose.yml and deploy/k8s/flashspec-deployment.yaml. The README test checks that these tags equal
  __version__.

This PR touches deploy/Dockerfile, so the container check runs. It builds and smoke-tests the newest release already on
PyPI (0.3.1) and pushes nothing.

Gate

Local, on this branch:

• make lint (ruff, format, import-linter: 2 contracts kept), mypy --strict flashspec: clean
• pytest tests/unit tests/integration -m "not gpu": 574 passed, 5 skipped (coverage 88.94%); pytest tests/chaos: 5 passed
• python scripts/readme_api.py --check: current
• python -m build: flashspec-0.3.2.tar.gz, flashspec-0.3.2-py3-none-any.whl
• twine check --strict dist/*: wheel PASSED, sdist PASSED
• readme_renderer on the wheel's long description, with warnings as errors: rendered; 6 tables, 11 code blocks,
  7 images, no relative link or image; image tag 0.3.2; the acceptance note is present

After merge (in this session, with the maintainer's go-ahead)

Tag v0.3.2 on the merge commit, push it, run Publish on the tag, approve the pypi environment, and wait for PyPI to show
0.3.2. Then create the GitHub release as a draft, check it, and publish it as Latest. That triggers the container workflow
for ghcr.io/mattral/flashspec:0.3.2 and :latest.