[yodablocks]

PyPI only has 0.0.1 to 0.0.4, which were 2 KB placeholders, and v0.1.0 was tagged but never uploaded. This sets up releases from tags and prepares 0.2.0 (133 commits after v0.1.0).

• One version number: pyproject.toml reads it from quarq/__init__.py (hatch dynamic version); the FastAPI app now reports it too instead of a hard-coded 0.1.0
• sdist: limited to quarq/, tests/ and top-level docs (was going to include experiments/); 122 KB
• README: absolute image URLs so the screenshots render on PyPI
• CHANGELOG: 0.2.0 entry (eval command and gold set, cross-encoder re-ranking, quarq_rag_v2 + rag migrate, fixes)
• .github/workflows/release.yml: on a v* tag: check tag == package version and a CHANGELOG entry exists, run tests, build, publish to PyPI with trusted publishing (no token), create a GitHub Release from the CHANGELOG section

Checked locally: 247 tests pass, uv build produces quarq-0.2.0 wheel and sdist with the expected contents, no CLAUDE files packaged, the workflow's shell steps run on the real files.

PyPI trusted publisher is already configured (yodablocks/quarq, release.yml, environment pypi).

After merging: push the tag to publish:

git checkout master && git pull && git tag v0.2.0 && git push origin v0.2.0