Apply the stop-ID registry in obehy build

[Sap1k]

Summary

This implements PROGRESS §2, using the registry design from the JrUtil and geodata PRs rather than the earlier stop-registry/jdf-stops.csv + --stop-registry-out sketch:

• When jrunify-ext-geodata/registry/stops.csv exists, obehy build passes --stop-registry to merge-jdf, jdf-to-bundle and regional-gtfs-overlay, with --stop-registry-candidates paths.
• The national-JDF run manifest records the registry's file hashes (stop_registry).
• The candidate CSVs are kept in releases/<run>/stop-registry/, because the national-JDF work directory is deleted after publish:
  • stop-candidates.csv;
  • post-candidates.csv;
  • place-candidates.csv.
• PROGRESS.md: §2 status, the known limitation, and a recent-log entry.

The converters/jrutil submodule pointer is not touched.

Related:

• Sap1k/jrutil: --stop-registry support (must land first)
• Sap1k/jrunify-ext-geodata: registry files and registry.py

Testing

• uv run pytest tests/unit -q: 75 passed.
• uv run ruff check src tests, uv run ruff format --check src tests and uv run pyright: all clean.
• Not run: a full or bounded live obehy build.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NaGwhzZNSpEZZQCoVPn9Fj

---

Generated by Claude Code