Bump to 0.0.4

[benjipeng]

First release since 0.0.3, and not a documentation-only one.

What is in it

Added

• EoMT-DINOv3 small-640 COCO panoptic family — config, DINOv3 LayerScale path, query insertion, mask and class heads, learned upscaling, processor
• viz.py — Result.draw() for boxes, masks, points, keypoints, tracks, and depth
• Changes to the Depth Anything V3, RF-DETR, and SAM 3.1 paths
• The project landing page and its share card

Removed — breaking

• mlx_cv.parity is gone from the wheel. That tooling now lives in tools/, where it belongs: it exists to compare against upstream reference checkouts, which is not something a runtime dependency should carry. Any caller importing mlx_cv.parity breaks on upgrade. Acceptable at 0.0.x, but it should be stated rather than discovered.

Two version literals stop being literals

tests/test_version.py asserted __version__ == "0.0.3". That only ever proved someone had edited that file — it could not catch the failure that actually happens, which is bumping pyproject.toml and forgetting __init__.py, or the reverse. It now compares __version__ against the installed distribution metadata.

convert_locateanything_checkpoint.py defaulted --converter-version to a hard-coded mlx-cv-0.0.3. That string is stamped into checkpoint provenance metadata, so every conversion run after a release quietly mislabelled itself. It reads __version__ now.

Caveats worth stating

• The Hugging Face model cards move their pinned install to 0.0.4, but those cards only reach the Hub through tools/huggingface_release.py upload, which is manual and needs the weights present. The published cards stay on 0.0.3 until someone runs it.
• The 0.0.3 strings under .agent/work/ are historical release records and stay as written.
• The version still lives in two files. [tool.hatch.version] could make pyproject.toml read it from __init__.py and leave one source of truth, but that changes build-backend behaviour and does not belong in the commit that cuts a release. The new test guards the gap in the meantime.

Verification

In a clean venv, outside the repo:

• distribution metadata and __version__ both report 0.0.4 and agree
• test_version.py passes
• the converter stamps mlx-cv-0.0.4

Publishing runs on the newly pinned workflow.yml (#30), whose YAML was parsed locally — it never runs on a pull request, so no CI check covers it.